~/talk

Web Accessibility For WordPress

Talkat WordCamp Atlanta 2019 · 2019-05-03..05-05· [wordpress, accessibility, web-platform]
links:none on file
slides:none on file

Explains concrete requirements: WCAG 2.1 AA via Section 508, and reports lawsuit growth from 57 (2015) to 814 (2017) to ~2,200 (2018), mostly NY and FL. Lists 11 practical steps — alt text or decorative labels, labeled form fields, captions/audio descriptions, 4.5:1 contrast, descriptive link text, keyboard/tab focus, skip-nav, ≥16px fonts, clear error messages, flexible timeouts. Demonstrates automated and manual testing with WAVE, Lighthouse, Axe, NVDA and a free WordPress missing-alt finder plugin that aggregates media, flags issues and suggests fixes.

AI-written summary · about

  1. 0:00Introduction and speaker background
  2. 1:48Why web accessibility matters
  3. 4:23Understanding Section 508 and WCAG
  4. 6:34Eleven easy accessibility steps
  5. 26:57Limitations of these steps
  6. 28:03Free tools for testing accessibility
  7. 33:47Screen readers and resources
  8. 36:16Legal requirements and compliance
  9. 38:42Accessibility statements and lawsuits
  10. 40:29Q&A and closing remarks
~/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.