The Accessibility Tree

Just a Spec

Gather ’round the accessibility tree, dear listeners, and hear a grand tale about roles and attributes, screen readers and DOM inspectors, and how to be a good A11Y. We also touch on why accessibility isn’t something you bolt on after you design a website but is part of the process from the very beginning.
Hosted by Jared White & Ayush
Links:

• Want to keep the discussion going?
  • Join the The Spicy Web Discord Server
  • Follow @[e-mail] on Mastodon
• HTML Design Principles: Priority of Constituencies
• WAI (Web Accessibility Initiative)
• The Accessibility Tree
• ARIA Resources for Developers
• ARIA Attributes (MDN Docs)
• ARIA Roles (MDN Docs)

Additional resources:

• Adrian Roselli
• Common ARIA mistakes and how to avoid them
• (No ARIA is better than bad ARIA!)
• WebAIM - web accessibility in mind
• Basecamp Accessibility Guidelines
• The Patchability of the Open Web
• (aka the “Right to Inspect”)

Luvut

1. Introduction (00:00:00)

2. Weather Report (00:01:21)

3. Become an a11y (00:02:22)

4. HTML's Priority of Constituencies (00:03:37)

5. Accessibility is for **everyone** (00:06:05)

6. Confess! (00:07:59)

7. Everyone has different abilities (00:12:16)

8. Accessibility is tied closely to Design (00:14:24)

9. Getting into the nuts and bolts (00:14:58)

10. Buttons shall be buttons! (00:20:35)

11. WAI-ARIA? (00:22:12)

12. role and aria-* attributes (00:23:17)

13.  and modal stuff (00:25:32)

14. Fav roles and attributes, and HTML grids! (00:26:42)

15. Modals, focus lock, and inert (00:31:43)

16. SPAs, React, and accessibility (00:36:30)

17. Tailwind…again… (00:39:31)

18. Right to "Inspect" (00:42:42)

19. Wrapping up (00:53:17)