Accessibility Testing Techniques, Issues and Tricks
summary
Projects for a large financial institution reveal concrete outcomes: automated and manual runs using NVDA plus a Chrome plugin uncover 40+ issues per site, most fixed by adding keyboard focus, ARIA labels and contrast tweaks. The team builds an accessibility test plan early, wires checks into user stories and sprints, measures screen‑reader and keyboard paths, and reduces regressions. Configuration cost for screen readers is high, so lightweight plugins and color‑contrast checkers become practical tradeoffs.
AI-written summary · about
chapters (11)
- 0:00Accessibility testing intro
- 3:15What accessibility testing means
- 10:56Starting accessibility testing
- 14:29Keyboard navigation & screen readers
- 17:19Color contrast & visual access
- 20:55Browser plugins for checks
- 23:27Screen readers on platforms
- 27:52Form accessibility mistakes
- 30:00Design choices affecting access
- 33:34Language in accessibility
- 36:30Q&A
related talks
56mAccessibility Testing 101
35mBuilding an accessibility testing habit
01h 05mAccessibility Testing 101
26mThe Ultimate Practical Guide to Accessibility Testing
52mAccessibility Testing 101
26mHow (Not) to Fail at Accessibility
31mDecoding web accessibility through testing
21mTesting A11y: Validating Web App Accessibility
