Continuous Accessibility
summary
A concrete claim: establish continuous accessibility by combining a three-part strategy—fix the code already shipped, make new code accessible by default, and measure progress with metrics. Implementation uses Ember template lint (the new to-do feature), x-core, Lighthouse, Accessibility Insights, Ember a11y testing add-on and an open a11y automation tracker. LinkedIn pilots rollouts and builds automated checks and trackers; the tracker shows about half automated or automatable violations and the tooling reduces recurring issues.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:26Common Terms
- 2:32Continuous Accessibility
- 4:16Essential Points of Strategy for Continuous Accessibility
- 6:12The Upgrade Path
- 8:34Automation and Accessibility
- 14:01Key Criteria of Quality Metrics
- 15:31Potential Violation Count
- 17:32A11y Automation Tracker
- 25:52Closing
- 26:11Keep the End Goal in Mind
related talks
36mAccessibility in Ember: where we are, where we need to go, how to get involved
30mAmbitious for All: Accessibility in Ember
22mAccessibility: The Sprint Filler Way
29mBuilding Accessibility Testing into Your Workflow
45mAccessibility feedback loop: Continuous a11y improvement in your development life cycle
50mShift Left on Accessibility: Beyond the Audit
45mAccessible by default
53mAutomating Accessibility Assurance