Automated screen reader testing with Claude Code, VoiceOver and Gherkin

> Screen reader testing is notoriously difficult, and can be slow. It’s usually because it needs to be done manually, and although developers and testers often know how to write automated acceptance tests, like the tests I wrote in the TetraLogical Accessible Components Library, this type of automation is not usually easy to apply to assistive technologies. > > But, what many people don’t know, is that VoiceOver on macOS has an AppleScript dictionary, and we can drive it from the terminal. This means we can boot up VoiceOver, move the virtual focus around, and capture what VoiceOver says, all fully automated. The functionality has been there for years, but hardly anyone uses it. Because, presumably, writing AppleScript isn’t most people’s idea of a fun afternoon!