My Journey to Accessibility Testing and What I Learned from It
summary
Journey describes starting from no experience and adopting WCAG 2.1 as the standard then collapsing ~100 checklist items into four principles perceivable operable understandable robust and focusing on core flows: register deposit play withdraw. Testing uses three screen readers cover 80% across Chrome Firefox Edge and IE11, finds keyboard-only popup traps and browser-specific failures, produces a WCAG-mapped gap analysis, developer guidelines, automated Lighthouse/GitHub/Microsoft checks and regression tests, and shows legal and market pressure (≈10%+ users affected).
AI-written summary · about
chapters (20)
- 0:00My accessibility journey
- 1:04Why accessibility testing matters
- 2:33Redefining accessibility testing
- 5:03WCAG 2.1 guidelines levels
- 7:10Starting accessibility testing project
- 9:00Research challenges in testing
- 11:15Narrowing testing methodologies
- 13:26Screen readers and keyboard testing
- 16:24Fixing inaccessible UI elements
- 18:34Cross-browser testing
- 20:27Accessibility flows in user lifecycle
- 22:34Myths about blind testing
- 24:19Documenting findings and gaps
- 26:10Convincing stakeholders
- 27:57Legal risks and business benefits
- 31:31Automating accessibility in CI/CD
- 32:55Developer accessibility guidelines
- 34:21Modern testing principles
- 36:33Recommended tools and resources
- 37:18Q&A
related talks
26mThe Ultimate Practical Guide to Accessibility Testing
01h 05mAccessibility Testing 101
25mBeyond Compliance: Testing for a more Accessible Web
56mAccessibility Testing 101
45mTips from the Trenches: Accessibility Testing
56mQuick Start for Evaluating and Testing Web Accessibility
08m"Introduction to Accessibility Testing"
35mBuilding an accessibility testing habit