Angular Accessibility Adventures: Navigating the Web for Everyone
summary
Claims: European Accessibility Act forces e‑commerce accessible by 2025 and maps to EN 301 549 / WCAG 2.1 AA; a single concrete stat is 4% of babies born with disabilities. Demos show concrete Angular fixes: update document title via TitleStrategy, add aria-current for router links, build skip links that read router.url on NavigationEnd, handle focus after navigation (autofocus only runs on full load), and LiveAnnouncer adds an aria-live region automatically — code examples mostly work but require router-aware logic.
AI-written summary · about
chapters (17)
- 0:00Angular accessibility intro
- 1:04Why accessibility matters
- 2:28European Act & WCAG overview
- 4:40Angular inherently accessible?
- 7:57Demo: Angular accessibility impact
- 10:03WCAG in Angular apps
- 10:47Fixing page titles in SPAs
- 12:14ARIA for navigation
- 14:00Skip links in Angular routing
- 15:51Focus in single-page navigation
- 17:18Focus management best practices
- 19:04Autofocus in Angular forms
- 20:29LiveAnnouncer for status
- 23:41Accessible forms & errors
- 25:49Dynamic content accessibility
- 27:13Semantic HTML in components
- 28:59Final thoughts & Q&A
related talks
25mAccessibility! is! important!
29mAngularJS Accessibility
38mAccessibility 101-102: What every tester should know about digital accessibility
29mAccessibility Matters: Creating a Better Web
37mAccessibility Matters: Creating a Better Web
17mAccessibility in Single Page Applications
01h 00mBuild more accessible apps in Angular
26mWeb Accessibility 101: An Introduction to A11Y