~/talk

Demystifying Accessibility in React Apps

Talkat React Brussels 2024 · on Friday, 2024-10-18· [react, accessibility]
slides:none on file

Covers how browsers build an accessibility tree, when to use native HTML versus ARIA, and how a demo form is implemented to announce errors and success reliably to screen readers (VoiceOver, NVDA, JAWS, TalkBack). Shows a reusable visually hidden component (polymorphic via an as prop), using React’s useId hook, aria-describedby/aria-invalid/aria-hidden, and role=status/alert for aria-live behavior. Demonstrates :focus-visible and the :has selector for keyboard-friendly hover actions, warns that research finds pages using ARIA often have more accessibility errors.

AI-written summary · about

  1. 0:00Introduction to accessibility
  2. 1:25Foundations of web accessibility
  3. 4:17ARIA and semantic HTML
  4. 6:25Icon buttons and focus management
  5. 12:23Accessible text inputs
  6. 20:34Validation and error handling
  7. 23:03Accessible notifications
  8. 24:29Testing with screen readers
~/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.