How Do You Make Accessibility Testing as Efficient as Possible
summary
Designs scan in Figma with axe for Designers and return 24 issues immediately; VS Code linting flags missing alt text and enforces custom-component mappings; the browser axe DevTools scan finds 18 issues, eight color-contrast “needs review” that an AI review resolves as passing, IGTs reach 57% progress and the table IGT finds seven missing header semantics in minutes; keyboard automation finds 15 tab stops and 20 keyboard issues; issues export into axe Auditor and the recorded user‑flow beta captures multi‑state scans for consolidated reporting.
AI-written summary · about
chapters (10)
- 0:00Introduction and agenda
- 2:34Design accessibility in Figma
- 5:36Design annotations and review
- 13:56Code linting for accessibility
- 23:13Browser extension testing
- 28:43Intelligent guided testing
- 34:31Keyboard and manual testing
- 39:20Importing to Axe Auditor
- 40:43Upcoming userflow analysis
- 42:30Q&A and closing
