New May 5, 2026

A11y Advent Day 21: Testing Accessibility

More Front-end Bloggers All from Kitty Giraudel View A11y Advent Day 21: Testing Accessibility on kittygiraudel.com

On day 2, we talked about evaluating accessibility with the Web Content Accessibility Guidelines. It is time to see how to test it. But first of all, a disclaimer: if I hope to have shown anything with this calendar is that accessibility is a broad topic impacting many different kinds of people and a lot of the work is done beyond sheer compliance with the WCAG.

Therefore, it is important to acknowledge that not everything can be automated. In fact, only a few things can be automated in the grand scheme of things. Basically, the HTML (and to some extent the CSS) can be audited to see if there are any sort immediately appearing markup issues.

Testing the HTML can be done with a variety of tools:

For copy-writing and content, I can recommend:

Low hanging-fruits which can be performed to test things:

For more all-around testing, there are pretty handy checklists:

For professional audits conducted by accessibility experts, I can recommend:

I am definitely forgetting a lot of tools here, this is just the tip of the iceberg. At the end of the day, ensuring proper accessibility and inclusivity in our products has to be done by combining various tools, methogolodies and manual work. There won’t be a one-size-fit-all testing solution. Feel free to share your favorite tools on Twitter with the #A11yAdvent hashtag!

Scroll to top