Skip to content

Free tools for SEO, AI search, Google Ads and local businesses. No sign-up. See all tools

DigitalSnot

Article Accessibility Checker: check your content against WCAG 2.2

Check an article for missing alt text, unclear links, heading gaps and unmarked Hindi, by WCAG 2.2.

  • Free to use
  • Runs in your browser
  • No sign-up

How to use the Article Accessibility Checker

Read what the guide says

This is the Article Accessibility Checker.

Check an article for missing alt text, unclear links, heading gaps and unmarked Hindi, by WCAG 2.2.

Copy the article's HTML from your editor's HTML or code view,

or the whole page from view-source, and paste it. Or open the file.

Or press Try an example to fill in sample details.

Read the checks, the most important first. Each one names its WCAG criterion,

or says "our check" when the rule is ours.

Fix the article in your editor, paste it again to check,

and copy the report for your team.

It runs in your browser, so nothing you type is uploaded.

Try it free on this page.

Runs in your browser. Your article is not uploaded, and no link, image or video is opened.

Copy it from the editor's HTML view (in WordPress, Options › Code editor), or the whole page from view-source to check the page language too. Pasting from the visual editor also works, and so does Markdown.

Used to find passages in the other language. A lang attribute on the page's <html> tag wins.

What it checks

The WCAG 2.2 criteria a writer controls: alt text, headings, lists and tables, link text, the language of the page and of Hindi passages, instructions that rely on colour or position, and video captions. It covers the content only, not your site's code, colours or menus, so it is not a full audit.

Paste your article to check it

You get a score (our checklist), the fixes to make first, and every check with its WCAG 2.2 criterion and how to fix it. Or press Try an example.

Share this free tool

Embed this tool on your websiteFree. Paste one code; it runs in your visitors' browsers.

Copy this code into a page of your site. The tool sets no cookies and sends nothing your visitors type to us. Change height="760" if it needs more room.

Preview the embed

How to embed a free tool on your website

Read what the video says

Want one of our free tools on your own website?

Here's how to embed it, in about a minute.

Open any of our browser tools, such as the GST Calculator.

Below the tool, find Embed this tool on your website, and open it.

Press Copy code.

The code is a frame with the tool in it, plus a short credit line that links to the tool's page.

In your website's editor, add an HTML block where you want the tool, and paste the code.

In WordPress, that's the Custom HTML block.

If the tool needs more room, change the height in the code.

Publish the page, and the tool works on your site.

Here, it's on a sample page for a made-up sweet shop.

Visitors use it right there. It sets no cookies, and sends nothing they type to us.

The credit line under it links to the tool on DigitalSnot.

You can embed as many of our free browser tools as you like.

About the Article Accessibility Checker

Paste your article's HTML from the editor's HTML or code view. The tool checks the parts of accessibility a writer controls, each against its WCAG 2.2 success criterion: images without text alternatives, headings and structure, lists and tables, link text, the page language and Hindi passages inside an English page, instructions that rely only on colour or position, and videos without captions or a transcript. You get a score (our checklist), what to fix first and how. It runs in your browser and covers the content only, not your site's code, colours or menus.

How it works

  1. 01

    Copy the article's HTML from your editor's HTML or code view, or the whole page from view-source, and paste it. Or open the file.

  2. 02

    Read the checks, the most important first. Each one names its WCAG criterion, or says "our check" when the rule is ours.

  3. 03

    Fix the article in your editor, paste it again to check, and copy the report for your team.

Built on WCAG 2.2

The Web Content Accessibility Guidelines (WCAG) 2.2 are the W3C's standard for accessible web content, a W3C Recommendation since October 2023. This tool picks the success criteria a writer controls: text alternatives for images (1.1.1), structure in the markup (1.3.1), instructions that do not rely only on shape or position (1.3.3) or on colour (1.4.1), captions and a text alternative for video (1.2.2, 1.2.3), link purpose (2.4.4), descriptive headings (2.4.6), and the language of the page and of passages in another language (3.1.1, 3.1.2).

Hindi and English in one article

WCAG 3.1.2 asks that the language of each passage or phrase in another language can be read by software, so a screen reader can pronounce it correctly. If an English article quotes a line in Hindi, mark it with lang="hi", for example <span lang="hi">…</span>. Proper names, technical terms and words that have become part of the surrounding language are exceptions. The tool finds Devanagari text that is not marked; it cannot tell Hinglish written in English letters from English.

What this tool cannot do

It checks the content you paste, not your site's theme, menus, forms, colour contrast or keyboard use, so it is not a full accessibility audit and cannot say that a page meets WCAG. Some checks need a person, such as whether a video has captions or an image is really decorative; those are marked "check". The score, the paragraph length and the capitals and emoji checks are our own.

Frequently asked questions

What is WCAG 2.2?

The Web Content Accessibility Guidelines, version 2.2, published by the W3C as a Recommendation on 5 October 2023; the current version is dated 12 December 2024. Each success criterion has a number and a level, A, AA or AAA. This tool covers criteria at levels A and AA that depend on what a writer puts in an article.

Does a high score mean my page is accessible?

No. The score is our checklist for the content you pasted. Many WCAG criteria depend on the site's design and code, such as colour contrast, keyboard use and forms, and need a full audit by a person with testing tools.

Why does the tool flag "click here" links?

WCAG 2.4.4 asks that the purpose of each link can be worked out from its text, or from the text with its sentence or paragraph. The W3C writing tips say to avoid vague link text such as "click here" and "read more". Link the words that name the page instead, such as "monsoon diet tips".

How do I mark Hindi text in an English article?

Wrap it in an element with lang="hi": <span lang="hi">धन्यवाद</span> for a phrase, or <p lang="hi"> for a whole paragraph. In WordPress you can add it in the block's Edit as HTML view. WCAG 3.1.2 does not ask you to mark proper names or technical terms.

Does the tool check colour contrast?

No. It reads the article's HTML and text, not your theme's colours or fonts. It does flag sentences that point to things only by colour or position, such as "tap the green button on the right" (WCAG 1.4.1 and 1.3.3), so you can add the button's name.

Sources and checks

Rules last checked

The Article Accessibility Checker follows these official pages:

The score, the paragraph length and the capitals and emoji checks are our own.

Scores, limits and suggestions marked "our checklist", "our measure" or "our suggestion" are ours, not Google's or the platform's. How our tools work

Related reading

Want help with your content?

Tell us about your site and what your articles and pages should bring in. We reply within one business day.

Talk to us Our service: Content and blog SEO

More content writing tools

All content writing tools

Want us to fix what the tool found?

Tell us about your business and what you want to grow. We reply within one business day with next steps, not a sales script.

  • A reply within one business day
  • A quick look at your site and search visibility before we talk
  • Your details are only used to answer your enquiry

Prefer email or a call?

[email protected]

+91 70079 75411

Popular