Accessibility Checker

Enter a page, a list of URLs or your whole website to find accessibility problems that can be spotted in the HTML: images without alt text, form fields without labels, links and buttons with no name, missing page language, blocked zoom and more. Each finding shows the element, the WCAG 2.2 success criterion where one applies, and how to fix it.

How to check your website’s accessibility

1. Choose One page, Page list (up to 100 URLs) or Whole site (a crawl from your homepage).
2. Click Check accessibility. Each problem shows the element, the WCAG 2.2 criterion where one applies, and how to fix it.
3. For a site crawl, use the Pages table to see which templates have the most problems, then tap a page for its full list.
4. Download the CSV to share with your developer.

What to fix first

• Form fields without labels on contact, booking and checkout forms. These stop people from contacting or paying you.
• Links and buttons with no name, usually icon-only buttons like menu, search and social links. Add an aria-label.
• Images without alt text. Describe meaningful images and use alt="" for decoration.
• Blocked zoom and missing page language. Both are one-line fixes in your theme’s header.
• Heading structure and vague link text on your key pages.

Test what tools can’t

• Keyboard: press Tab through the page. Can you reach every link, button and field, see where you are, and open the menu?
• Zoom: zoom the browser to 200%. Text should still fit without overlapping or cutting off.
• Screen reader: try VoiceOver (iPhone or Mac) or TalkBack (Android) on your homepage and contact form for a few minutes.
• Contrast: run Lighthouse in Chrome DevTools or the axe DevTools extension to check colour contrast on the rendered page.

Also check your images with the image SEO audit, and find broken links and other technical issues with the website SEO crawler.

Frequently asked questions

What does this accessibility checker test?

It reads each page’s HTML and checks for images without alt text, form fields, buttons and links without an accessible name, a missing or invalid page language, a missing page title, zoom being blocked, timed refreshes, autoplaying media, positive tabindex, focusable elements hidden with aria-hidden, ARIA references to missing IDs, iframe titles, heading structure, data tables without headers and a missing main landmark.

Does a clean result mean my site is WCAG compliant?

No. Automated checks can only find part of the problems. Colour contrast, keyboard use, focus visibility, captions and whether alt text and labels make sense all need a rendered page or a person to judge. Use this tool to catch the common issues fast, then test by hand and with Lighthouse or axe DevTools in your browser.

Why are some findings notices instead of errors?

Errors are clear failures of a WCAG success criterion, such as an image with no alt attribute. Warnings are likely problems that depend on context. Notices are best practices, such as skipped heading levels or vague link text like “read more”, which can still pass if the surrounding text makes the purpose clear.

Is this the same as an ADA or EAA compliance check?

Laws such as the ADA in the US and the European Accessibility Act generally point to WCAG as the technical standard. This tool checks some WCAG criteria automatically, but it is not a legal audit or a certificate. For legal questions, talk to a specialist.

Can I check my whole website?

Yes. Choose Whole site to crawl up to 500 pages while you wait, or 750 to 1,000 pages as an email report that we run on our server and send to you as a link. Page list checks up to 100 URLs you paste.

Why might a result differ from what I see in the browser?

The checker reads the HTML your server sends. Elements added or changed later by JavaScript, such as chat widgets or cookie banners, are not checked. Email reports store a slimmed copy of each page, so icon-only links that use SVG titles are skipped there rather than reported.

More free tools

See all free marketing tools