~/talk

Accessibility Testing Techniques, Issues and Tricks

Talkat TestCon Vilnius 2017 · 2017-10-18..10-20· [accessibility, testing]
links:none on file
slides:none on file

Projects for a large financial institution reveal concrete outcomes: automated and manual runs using NVDA plus a Chrome plugin uncover 40+ issues per site, most fixed by adding keyboard focus, ARIA labels and contrast tweaks. The team builds an accessibility test plan early, wires checks into user stories and sprints, measures screen‑reader and keyboard paths, and reduces regressions. Configuration cost for screen readers is high, so lightweight plugins and color‑contrast checkers become practical tradeoffs.

AI-written summary · about

  1. 0:00Accessibility testing intro
  2. 3:15What accessibility testing means
  3. 10:56Starting accessibility testing
  4. 14:29Keyboard navigation & screen readers
  5. 17:19Color contrast & visual access
  6. 20:55Browser plugins for checks
  7. 23:27Screen readers on platforms
  8. 27:52Form accessibility mistakes
  9. 30:00Design choices affecting access
  10. 33:34Language in accessibility
  11. 36:30Q&A
~/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.