Check your website's accessibility for free

What this free accessibility checker tests

Each website accessibility test below maps to a WCAG 2.2 success criterion or a common best practice. Results are ranked so the issues with the most impact come first.

• Images without alt text, including image links and image buttons (WCAG 1.1.1)
• Form fields without labels (1.3.1, 4.1.2)
• Links with no accessible text (2.4.4, 4.1.2)
• Buttons with no accessible text (4.1.2)
• Missing page language (3.1.1)
• Missing or empty page title (2.4.2)
• No h1 and skipped heading levels (1.3.1, best practice)
• Zoom blocked on mobile (1.4.4)
• No skip link or main landmark (2.4.1)
• Frames without titles (4.1.2)
• Media that autoplays with sound (1.4.2)
• Positive tabindex (2.4.3)
• Duplicate ids (4.1.1 in WCAG 2.0 and 2.1)

What an automated website accessibility test can't tell you

This checker reads the HTML the server sends for the one page you enter. It doesn't crawl other pages or run the page's JavaScript, and it doesn't test color contrast (WCAG 1.4.3). No automated test can tell you whether you can reach and use everything with a keyboard, whether focus order makes sense, how a screen reader announces your forms, whether alt text actually describes the image, or whether videos have accurate captions. That takes a person. Read our guide to manual accessibility testing.

How to test web accessibility yourself in 15 minutes

1. Keyboard pass. Put the mouse aside and press Tab through the page. Can you see where you are at every step, and reach and use every link, menu, and form field?
2. Zoom to 200%. Zoom the browser to 200%. Is all the text still readable, without overlapping or being cut off?
3. Contrast. Check that body text stands out clearly from its background. WCAG asks for a contrast ratio of at least 4.5:1 for normal text.

For a fuller walkthrough, see how to do an accessibility audit.

Checker vs. a full accessibility audit

See all accessibility audit services from Tabstop Audits.

We don't use overlay widgets

We don't use or sell overlay widgets. We fix the underlying pages instead; read our take on accessibility overlays.

Frequently asked questions

Is this website accessibility checker really free?

Yes. You can check as many single pages as you like, with no signup. To keep it free and fair, each visitor can run up to 12 checks an hour.

Can a free checker tell me whether my site meets the ADA?

No. No automated tool can. It finds a share of common WCAG issues. Whether a site meets the law depends on things only a person can judge, and we don't give legal advice.

What standard does it check against?

Automated rules that map to WCAG 2.2 Level A and AA success criteria, plus two widely used best practices for headings. One rule, duplicate ids, comes from WCAG 2.0 and 2.1 and was removed in 2.2; we still flag it because it can break labels.

How much of WCAG can an automated test catch?

Only part of it. In a 2017 GOV.UK test of 10 automated tools on a page with 143 known barriers, the best single tool caught 37 to 41 percent of them, and 29 percent were missed by every tool. Manual keyboard and screen reader testing covers the rest. This free check runs fewer rules than those full tools.

Do you store the pages I scan?

No, we don't store the page's content. For each check we store the page address, the time, how many issues of each type we found, your country, and a one-way hash of your IP address for rate limiting. If you choose to leave your email, we also store it with that page's full results.

What should I do after the scan?

Fix the listed items, then test with a keyboard and a screen reader, or have Tabstop Audits do it in a $299 Snapshot Audit of three pages.

Does it work on WordPress, Shopify, Squarespace, or Wix?

Yes. It checks the public page, whatever built it. Pages that build most of their content with JavaScript may show fewer results, because this checker reads the HTML the server sends.

Source for the 2017 figures: GOV.UK Accessibility blog, What we found when we tested tools on the world's least-accessible webpage (February 24, 2017).