~/talk

How to create accessible JavaScript widgets with basic HTML components

links:none on file
slides:none on file

Argues that accessible, robust widgets come from native HTML form controls not heavy ARIA hacks, audits Google/Amazon autocompletes and finds mediocre screen‑reader support, then builds a working autocomplete using radio buttons as autocomplete, visual hiding of inputs, and only a tiny bit of ARIA. Demonstrates it works with NVDA and VoiceOver, degrades without CSS, and requires about ~200 lines of JS and 60 lines of CSS; WAI‑ARIA is for polishing, not replacing native semantics.

AI-written summary · about

  1. 0:00Introduction and philosophy
  2. 3:47Benefits of traditional HTML
  3. 9:20Why custom code fails
  4. 13:30Understanding ARIA limitations
  5. 20:40The first rule of ARIA
  6. 25:02Accessible widget examples
  7. 29:02Recap and final advice
  8. 32:50Q&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.