Outside tools for accessibility and testing

Free tools from other makers that check contrast, find accessibility problems, and let you use a page the way many people do.

Every link on this page goes to another site. Each tool is free. Most of them are already part of your computer or phone.

Check colour contrast

Text needs a contrast of 4.5:1 against its background, and control borders and the focus ring need 3:1. tools/contrast.py checks the tokens; these tools check any two colours.

Run automatic checks

These go through a page and list problems such as missing labels, missing alt text and headings out of order. They find only some problems, so always test with people too.

  • axe DevTools: a browser extension; the free version checks the whole page.
  • WAVE: marks each problem on the page itself, which helps when you are learning.
  • Lighthouse: part of Chrome and Edge, in the developer tools.
  • Accessibility Insights: automatic checks, plus a guided check of what a tool cannot test.
  • Playwright with axe-core: runs the same checks in your automated tests, so a problem stops a release. axe-core is the engine.

Snaglist has a check of its own, 'Check this page for accessibility problems', that people can run on any page. Read Feedback in the product with Snaglist.

Use a screen reader

A screen reader reads the page aloud, or shows it on a braille display. Use one to check that every control has a name, headings are in order and changes are announced.

  • NVDA: for Windows.
  • VoiceOver: part of every Mac, iPhone and iPad.
  • TalkBack: part of Android phones.
  • Orca: for Linux desktops.

Use a magnifier

A magnifier enlarges part of the page, so only a small part is in view at once. Check that messages appear near the thing they belong to, and that nothing needs a wide view to make sense. Also try the gallery's Display slide-out at 175% text.

Use voice control

People who use voice control say the name of the control they want, for example "Save changes". It works only when the words on a control match its name in the code, which is one more reason to name controls by their visible label.

Read the standard