~/talk

Harnessing the Accessibility Tree

Talkat SquiggleConf 2024 · 2024-10-03..10-04· [accessibility, web-platform]
slides:none on file

Explains that the accessibility tree is a render-time, filtered DOM exposed to assistive tech and shows how to view it in DevTools (Edge toggle, Firefox Accessibility tab, Chrome tree or bottom view, Safari node inspector). Demonstrates concrete fixes: replace div-with-click with a native button instead of adding tabindex+role+keydown, use ARIA-hidden and aria-expanded properly, and check nodes for role name focusable. Notes Lighthouse only catches ~30% of issues.

AI-written summary · about

  1. 0:00Introduction
  2. 0:41What is accessibility
  3. 1:25Accessibility tree explained
  4. 2:28Dev tools accessibility tree
  5. 4:15Semantic HTML tags
  6. 5:19ARIA attributes
  7. 6:03Bad button example
  8. 7:49Why use semantic tags
  9. 8:30Finding the tree in browsers
  10. 9:14Key takeaways
  11. 9:57Q&A session
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.