Adding accessibility into Unit Tests
summary
Automated checks catch about 25% of accessibility issues so the team integrates Deque’s Axe into Jest/React unit tests, mapping WCAG/Section 508 rules, disabling non‑blocking checks and enabling rules like tabindex meaningful sequence and title-only inputs. Tests produce Axe reports with DOM snippets and Deque help URLs, immediately flagging missing alt text and input labels; setup works but doubles test time, misses off‑DOM dialogs, and needs manual code review and future keyboard‑interaction custom rules.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:48Who are we
- 1:14What is accessibility
- 2:34Laws
- 5:43Manual Testing
- 11:38Automated Unit Testing
- 14:52Generate AX Report
- 15:36Act Standard to Run
- 16:03Other Rules
- 19:50Running a test
- 20:07Checking the rules
- 20:51DQ site
- 21:57DOM output
- 23:57Viewing the tests
- 27:13Whats next
- 30:05Summary
- 31:32Conclusion
- 32:12Disclaimer
related talks
28mAutomated Accessibility Testing
33mAutomated Accessibility Testing
35mAutomated Accessibility Testing
21mTesting A11y: Validating Web App Accessibility
53mAutomating Accessibility Assurance
29mBuilding Accessibility Testing into Your Workflow
01h 05mAccessibility + TDD == easy && !impossible
07mHow to Catch a11y Defects During Unit and E2E Testing