WCAG checker

Enter the address of a web page. You get a report that explains every problem found: what is wrong? Which rule is affected? How do you fix it?

For example www.example.org. Only this one page is checked.

Next: test by hand

Automated tools find only about a third of all barriers. A report without problems therefore does not mean the page is accessible. Anyone can do these six checks:

  1. Use the keyboard only. Can you reach everything with Tab? Can you always see where focus is? Can you get out of everything again?
  2. Zoom to 400%. Does everything stay readable and usable without scrolling sideways?
  3. Listen with a screen reader. Do headings, links and forms make sense when read aloud? Are text alternatives helpful – not just present?
  4. Check video and audio. Are there captions and transcripts? Does nothing start by itself?
  5. Submit forms with mistakes. Does the error message say which field is affected and how to get it right?
  6. Read the text. Is the language simple and clear? Are technical terms and abbreviations explained?

How the checker works

  • The checker opens the page in a browser on our server and tests it with the open-source tool axe-core.
  • It tests WCAG Levels A and AA plus established best practices.
  • We store neither the address nor the result. The “Done” ticks stay in your browser only.
  • You can run 6 checks per minute. The checker cannot test pages behind a login.

There is an open API for developers and AI agents: API description (OpenAPI).