After the audit: Integrating accessibility into the testing process
summary
Audit results and a VPAT become artifacts to drive ongoing testing not an endpoint: map audit findings into regression tickets, add linters and CI checks, run Lighthouse and WAVE but expect 20–30% found by automation, and prioritize inexpensive wins like keyboard testing first before introducing screen reader sessions. Build checklists tied to WCAG criteria, upskill teams by assigning tasks that match strengths, and treat the vendor report plus re-tests as the baseline for monitoring regressions and new-feature validation.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:39AFTER THE AUDIT INTEGRATING ACCESSIBILITY INTO THE TESTING PROCESS
- 3:11WHAT IS AN ACCESSIBILITY AUDIT?
- 4:55Review of features to be audited • Testing (manual and automated) • Result Report • Remediation of issues • Re-Testing and Validation • Voluntary Product Accessibility Template (PAT)
- 7:15Area/Feature of Focus • Issue Description • Violations • Recommendations (techniques, potential solutions)
- 9:07Report of your company's conformance to accessibility standards Section 508 of the U.S. Rehabilitation Act of 1973 • Used by Federal agencies and government buyers when evaluating venders
- 17:12ESTABLISH A BASELINE OF KNOWLEDGE
- 18:27PLAY TO PEOPLE'S STRENGTHS
- 21:04OPEN AND POSITIVE ENVIRONMENT
- 23:27UPSKILL THE WHOLE ORGANIZATION
- 25:51STEP BY STEP
- 26:28Checklists • Keyboard Testing Automation Tools
- 33:36REGRESSION SUITES
- 35:42ONLY 20-30% OF ACCESSIBILITY ISSUES ARE FOUND WITH AUTOMATION TESTING
- 37:58TAKEAWAYS
related talks
26mThe Ultimate Practical Guide to Accessibility Testing
45mAccessibility feedback loop: Continuous a11y improvement in your development life cycle
38mHow to set up an accessibility program in an imperfect world
50mShift Left on Accessibility: Beyond the Audit
56mAccessibility Testing 101
52mAccessibility Testing 101
33mAutomated Accessibility Testing
23mAccessibility audit and what's after it