This is a collection of (mostly automated) accessibility checkers that we recommend and/or have found useful, in collaboration with human oversight.

Documents (Word, PowerPoint, Google Docs and Slides, PDF)

As part of the Accessible Communication competency, you are expected to make documents accessible, including the running project doc and poster.

We do not recommend using PDFs or teach how to make them accessible in this class.

Websites and apps

As part of the Accessible Implementation competency and the accessibility audit, you will need to make your website/app accessible.

  • Beginners’ guide to accessibility testing appt.org walks through testing without tools, text resizing, contrast, and screen readers.
  • WCAG A good entry point is the WCAG beginners’ guide. You will need to use the full guidelines as a reference
  • axe DevTools: a browser extension that runs automated testing on a page (you can also run it in a testing script)
  • WAVE: WebAIM is a web interface to an accessibility checker.
  • HTML validator: the W3C Markup Validator catches invalid markup.
  • Keyboard only: unplug or ignore the mouse, then try to reach and use everything with Tab, Shift+Tab, Enter, Space, and the arrow keys. No tool replaces this.

Screen readers

You will need to test your project with a screen reader (the audit assignment has the full instructions).

Color and contrast

Mobile apps

Something missing?

Suggest things on the [Class discussion]https://edstem.org/us/courses/107577/discussion/) and we’ll add them!


Back to top

The University of Washington acknowledges the Coast Salish peoples of this land, the land which touches the shared waters of all tribes and bands within the Suquamish, Tulalip and Muckleshoot nations. This site is maintained by J. Mankoff.