Prioritizing Remediation of Accessibility Issues
summary
Treat accessibility issues as defects and prioritize by concrete factors: measured user impact, ease and speed of repair, location and volume of occurrences, impact on interface/business logic, and secondary benefits. Use automated scans plus expert review, log issues with extra fields (Bonfire or Excel), weight factors (user impact ≈ 3.95, interface ≈ 1.5 from a Delphi exercise), and track remediation as a concentration metric: bugs divided by lines of code. Example: Target’s ~$10M settlement yields an $800k expected-risk at 10% probability.
AI-written summary · about
chapters (7)
- 0:00Start
- 31:12Remediation Challenges
- 33:48Remediation Approaches
- 34:44Simple Prioritization
- 35:28Advanced Prioritization
- 47:08Managing Remediation
- 50:44Conclusion
related talks
50mShift Left on Accessibility: Beyond the Audit
57mHow (and why) to 'shift-left' your accessibility testing
48mGet It Right the 1st Time: Stop 80%+ of A11Y Bugs During Development
45mTips from the Trenches: Accessibility Testing
33mHow to make your application accessible (and keep it that way!)
29mAccessibility That Scales
59mFixing Accessibility After the Fact Is Already Too Late
48mFind and Fix Your Accessibility Problems