There is a common misconception that accessibility testing can only fall into two groups:

Some limited amount of static analysis performed by something like Axe

Manual testing for everything else, either by yourself, your tester, your AI agent(?), your resident accessibility expert, or hopefully real assistive technology users

If you've gone a step further, you might even have some coverage in your functional test suite of choice for keyboard interactions (most cool!), but have you ever considered that you could also be testing with some popular screen reader technologies as well?

Instead of querying the DOM to find a button, or checking its accessible name from the browser's internal accessibility tree, you could be navigating using a real screen reader and assert against what it actually announces.

In this post we'll walk you through how to set it up with Guidepup running against the BBC Homepage - spoiler alert, it's two extra CLI commands and then whatever tests you fancy writing!

Getting…