Ambitious for All: Accessibility in Ember
summary
Ember used at JPMorgan Chase to meet legal WCAG 2.0 AA requirements and a claim that nearly 10% of users have disabilities drive concrete fixes: routing transitions that don’t announce new content, modal focus trap and keyboard management, ARIA rule mapping, and an add-on that injects attributes without rewriting components. Examples point to the ember component attributes add-on, the ember a11y github repo, and practical wins rather than vague principles.
AI-written summary · about
chapters (32)
- 0:00Intro
- 1:02My Story
- 1:54Web Standards
- 2:29WAA
- 2:57Access
- 3:36Web Content Accessibility Guidelines
- 4:15Americans with Disabilities Act
- 4:27Accessibility on Twitter
- 4:53The future is cool
- 5:25Colorblind people
- 6:02Hard auditory brainstem implant
- 6:33Video Indexer
- 7:50What about you
- 9:05Accessibility is emotional
- 9:15Its emotional for our users
- 9:37It can feel overwhelming and daunting
- 10:00Accessibility is also emotional
- 10:55It works
- 11:34Accessibility is hard
- 12:06Challenges
- 16:44Superhero
- 17:31Semantic HTML
- 22:07Fights
- 22:35Batman vs Superman
- 23:01Jib Element
- 23:20H1 Element
- 23:39Tabs vs Spaces
- 25:18Addons
- 27:03Youre not alone
- 28:01My word for 2018
- 28:36What if
- 29:44Outro
related talks
36mAccessibility in Ember: where we are, where we need to go, how to get involved
35m"Single Page Access"
34mBuilding for Accessibility
27mContinuous Accessibility
37mAccessibility Matters: Creating a Better Web
33mA11y First and Everyone Wins
29mAccessibility first is the new Mobile first
33mAccessibility needs to be the future of better technology