~/talk

So How Do I Know if my Website is Accessible?

Talkat Inclusive Design 24 2014 · on Thursday, 2014-05-15· [accessibility, developer-experience]
slides:none on file

A practical yes/no checklist shows whether a site actually works: keyboard-only navigation and visible focus, correct tab order, keyboard-accessible drop‑downs and lightboxes, meaningful link text, alt text present (or empty when decorative), captions on videos, labelled form fields, logical headings, resizable text without layout break, and sufficient color contrast with no meaning conveyed by color alone. The talk demonstrates the WAVE toolbar and Colour Contrast Analyzer and warns that automated checks help but never replace manual verification.

AI-written summary · about

  1. 0:00Start
  2. 11:24What I'm going to cover
  3. 12:47Health warning
  4. 13:18Keyboard interaction
  5. 27:27Signposting content
  6. 28:33Using headings
  7. 31:48Text
  8. 33:35User input
  9. 36:19Colour contrast
  10. 38:48Colour & shape
  11. 41:47Useful links
  12. 47:36Some things I didn't cover
~/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.