30 Minutes or Less: The Magic of Automated Accessibility Testing
summary
Demo shows automated audits catching missing labels and focus bugs before deploy and a protractor plugin that runs Chrome accessibility checks during end to end tests against a real browser rather than headless phantom. Command line audits use a11y CLI, unit tests assert ARIA and tabIndex behavior for custom controls, and the protractor plugin can call the Tenon API key or the Chrome accessibility devtools. Example app fixes make tests pass but the promised pizza never arrives.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:20Accessibility basics
- 2:58Manual audit techniques
- 5:53Automated testing strategy
- 7:04Live demo and keyboard
- 10:27Browser tools and trees
- 14:26Command line automation
- 16:52Protractor testing plugin
- 24:17Unit testing accessibility
- 27:58Conclusion and Q&A
related talks
33mAutomated Accessibility Testing
56mAccessibility Testing 101
30mTesting Web Accessibility
35mAutomated Accessibility Testing
43mLucky Nkosi: A11y Beyond the Theory: Integrating Accessibility Testing into Your Workflow
49mAutomated & Manual Testing + AI: A Holistic Approach to Accessibility
44mTesting Web Accessibility
25mHow to do good without doing anything