Accessibility in Ember: where we are, where we need to go, how to get involved
summary
Goal is that a newly generated Ember app no longer fails basic a11y checks; the working group sets scope, severity levels (1–3), and ships incremental fixes. Delivered: ember-a11y-refocus (focus reset, skip link, route-change announcement), ember-page-title in the app blueprint, a lang flag for ember new, ember-template-lint with 26 accessibility rules and a to‑do feature, and ember-select-light; RFCs for unique-id and interactive new-app mode exist but remain to be implemented. An a11y automation tracker (a11yautomation.dev) catalogs gaps.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:05Step Two: Identify Primary Issues
- 6:40Step Three: Measuring User Impact
- 7:30Severity Level Three
- 22:01Community Participation
