~/talk

Designing for accessibility

Talkat WordCamp US 2022 · 2022-09-09..09-11· [accessibility, ux-and-product-design]
links:none on file
slides:none on file

Design guidance with concrete rules: 97.4% of top sites fail accessibility so fixable specifics matter — use body text >= 18px, constrain paragraphs to 60–80 characters, set line-height ≥130%, and avoid justified or all‑caps text; ensure link targets are ≥44×44px with 8px spacing, visible focus states, and not reliant on color alone; follow WCAG contrast ratios (AA 4.5:1 for normal text, 3:1 for large UI elements) and test with Figma plugins like Contrast/Contrast Grid, pinetools.com for darkening, prefers‑color‑scheme/‑reduced‑motion media queries, OpenDyslexic, transcripts, and annotated Figma handoffs plus an a11y checklist.

AI-written summary · about

  1. 0:00Introduction and speaker background
  2. 1:29Why accessibility matters
  3. 3:35Current state of web accessibility
  4. 4:39Typography best practices for accessibility
  5. 10:40Link design and accessibility
  6. 16:25Form accessibility guidelines
  7. 21:26Color and contrast fundamentals
  8. 31:17Content structure and simplicity
  9. 33:24Alt text and media accessibility
  10. 35:51Motion and dyslexia considerations
  11. 38:37Handoff and accessibility checklists
  12. 40:21Call to action and conclusion
  13. 41:10Q&A session
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.