Shift Left
summary
Argues that shifting accessibility left measurably raises code quality: enableable lint rules and tests catch problems before commit, cutting Jira churn and regressions. Demonstrates concrete tools — Ember template lint with accessibility rules and Ember a11y testing — and ongoing work to add automated intent tests and editor integration (IntelliJ). Gives surprising constraints like less than 1500 nodes max depth 32 no parent over 60 children, shows rule additions that run now and reduces later rewrites.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:29Shift left in front-end
- 5:40User-centric questions
- 8:31Good patterns vs anti-patterns
- 10:16Accessibility testing tools
- 13:26Accessibility final frontier
- 14:51Accessible code as performance
- 16:38Turning inspiration into action
related talks
29mBuilding Accessibility Testing into Your Workflow
27mContinuous Accessibility
57mHow (and why) to 'shift-left' your accessibility testing
51mGetting the Most Out of Your Shift Left Regardless of Your Program Maturity
36mAccessibility in Ember: where we are, where we need to go, how to get involved
59mActually Shifting Left: Technical Accessibility for Designers
30mAmbitious for All: Accessibility in Ember
30mLint Your Code Into the Future