~/talk

How to test a website's accessibility?

TalkinFrenchat DevFest Paris 2025 · on Friday, 2025-11-21· [accessibility, frontend-architecture]
links:none on file
slides:none on file

The talk reviews the six most common web accessibility mistakes and gives practical HTML (and some CSS) fixes for each. It also demonstrates how to run user tests using a screen reader and keyboard, and how to set up automated accessibility tests.

AI-written summary · about

  1. 0:00Web accessibility intro
  2. 1:05Top six accessibility mistakes
  3. 3:37Keyboard navigation
  4. 6:50Color contrast checks
  5. 9:07Site language for screen readers
  6. 12:59Image alt text
  7. 16:34Accessible forms
  8. 21:46Clear buttons and links
  9. 27:51HTML semantics
  10. 33:11Automated accessibility tools
  11. 36:34ARIA best practices
  12. 39:02Legal obligations
  13. 43:44Accessibility by design
  14. 46:35Conclusion
~/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.