Automation meets UX: Perfect Partners for Accessibility
summary
Automation scans the HTML, runs WCAG rule checks, highlights offending elements, captures screenshots and generates per‑link reports; it’s fast and cheap but cannot yet test native mobile apps. A BVG mover evaluation finds 6 major, 12 serious, 13 cosmetic issues discovered by 8 one‑hour interviews — automated scans looked almost clean while real users fail the lengthy QR→landing→download setup, proving the service is unusable in emergency scenarios.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 2:31Why accessibility testing matters
- 4:15Automated accessibility testing explained
- 7:54Pros and cons of automation
- 11:04Why user testing is essential
- 13:57Strengths and weaknesses of UX testing
- 17:14Case study: BVG Mover app
- 22:54Automated test results example
- 24:25User testing findings vs automation
- 27:14Combining both methods for best results
- 28:41Q&A session
related talks
38mAutomated vs. Manual Accessibility Testing: Finding the Right Balance
35mAutomated Accessibility Testing
33mAutomated Accessibility Testing
56mAccessibility Testing 101
59mAccessibility in UX: A panel discussion
21mTesting A11y: Validating Web App Accessibility
44mCan Accessibility Testing Be Automated?
52mAccessibility Testing 101