Developers can catch 90% of critical blocker accessibility issues with just a few quick checks. If each developer agrees to test their work for accessibility issues before committing to the branch or marking an issue as “Done,” they can prevent major accessibility problems from advancing through the development pipeline. We will walk through two tests for a total of 6 checkpoints you can do in a web browser that should uncover critical blockers that will prevent some people from using a webpage.

Comments

Please login to leave a comment

Anna Filina at 14:00 on 16 Oct 2026

Nice examples. The pace was good. There was a lot of good information. I like that it didn't try to cover too much, therefore it could go into details that I don't see often in other talks on the topic.

Chris Holland at 14:11 on 16 Oct 2026

Very informative and a practical set of quick checks we can go through

Very thorough & well-metered overview that every developer regardless of language should see.

Thanks for the talk. I liked the information, and it was super helpful. My only suggestion is to "show" more, because I got a little confused by some of the examples where a picture might have helped. The tabbing and zoom examples were great because I could see them but others were a little more challenging.

Great avenue for baseline accessibility. I like the emphasis on keyboard users, which is often overlooked.
Rachele presented the information in a way that was clear and easy to understand.

Only thing missing was be a live demo rather than screenshots.