Technologic (Human After All): Accessibility remix
summary
Examples show that plain HTML often gives accessibility for free and that pragmatic fixes use ARIA and scripting to add role, name and state — a disclosure widget is rebuilt from inert span to focusable control with aria-expanded, aria-controls and hidden content and it works with keyboard and screen readers except where only one screen reader supports that attribute. The talk names the Tenon API, cites 25% less code if native button is used, and flags Flexbox reordering and generated CSS content quirks.
AI-written summary · about
chapters (14)
- 0:00Accessibility introduction
- 1:03Breaking fixing upgrading
- 4:14HTML roles
- 6:14DOM order keyboard
- 8:02Accessibility tree
- 10:29ARIA for fixing accessibility issues
- 12:57Disclosure widget ARIA
- 21:04Testing tools
- 26:42Screen reader testing
- 27:04CSS accessibility
- 32:22CSS content screen readers
- 32:43Flexbox keyboard issues
- 39:07Steps to improve
- 40:41Conclusion
