I would like webpages to be accessible (in the #a11y sense).
In the past I've been on teams where we did automated webpage regression testing (using https://www.selenium.dev back then). API's for those always felt cumbersome and 'technical'.
This got me wondering: wouldn't it make sense to express UI tests in terms of how someone using assistive technology would experience the site? Then if a feature is hard to describe that way, that indicates it might need some more work/thought anyway.
Are there tools that do this? I saw https://github.com/AmadeusITGroup/Assistive-Webdriver but that appears to still make you quite 'explicitly' test whether #a11y has been "successfully bolted on as an afterthought", rather than asking "how would this site work when primarily seen through the lens of assistive technology?".
Of course this won't be perfect: it will still miss real problems both for users using assistive technologies and for ones that don't - but that is inherent in frontend tests.
Curious about experiences!
@raboof I built voiceover.js to make it easy to express actions for assistive tech. the example test shows how to use it with playwright. https://github.com/AccessLint/voiceover.js/blob/main/README.md
@raboof im thinking about a DSL that could work for either mouse or screen readers. like `activate` instead of `click` etc
Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them.