~/talk

Web Accessibility - a better user experience for everyone!

TalkinCzechat FrontKon 2023 · on Thursday, 2023-10-12· [accessibility, design-collaboration]
links:none on file
slides:none on file

Practical checklist for improving web accessibility: ensure text contrast >= 4.5 using Chrome DevTools contrast inspector, use a base font size of at least 16px, maintain visible focus states and full keyboard navigation, never replace labels with placeholders and add descriptive aria-labels for ambiguous icons. Use semantic regions (header, nav, main, footer) with a single H1, provide meaningful alt text (or empty alt for decorative images), test with a Windows screen reader, and automate checks with Lighthouse, AXE, lint rules and unit/Cypress tests; examples include skip links (BBC) and Twitter accessibility settings.

AI-written summary · about

  1. 0:00Web accessibility basics
  2. 2:11Accessibility principles examples
  3. 3:17Contrast for older users
  4. 5:44Text size and interactive elements
  5. 6:50Keyboard-only testing
  6. 8:17Visible focus states
  7. 9:00Screen reader basics
  8. 10:28Labeled forms over placeholders
  9. 11:54Descriptive links and ARIA
  10. 13:00Semantic HTML structure
  11. 14:26Image alt text
  12. 15:53Automated testing tools
  13. 16:37Benefits of accessible web
  14. 17:20Accessible website examples
  15. 18:04Skip links for quick nav
  16. 19:08Q&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.