~/talk

Not a designer? You can make your website more accessible

Talkat Laracon AU 2019 · on Thursday, 2019-10-31· [accessibility, design-collaboration]
slides:none on file

Concrete rules and examples: set root type with rem units (browser default 16px), limit lines to about 50–60 characters, use looser line-height (1.8 instead of 1.5) as tested on a real blog built with CSS Grid, keep visible labels not placeholders, mark up forms and navigation with semantic elements like figure and figcaption, meet WCAG contrast ratios, make interactive targets at least 44‑pixel tap targets, avoid hover‑only menus, and favor progressive enhancement so heavy fonts and scripts don’t break core functionality.

AI-written summary · about

  1. 0:00Intro
  2. 0:45Is anyone a designer
  3. 1:18Who am I
  4. 1:36Accessibility
  5. 2:09Situational impairments
  6. 2:51Typography
  7. 4:39Maximum width
  8. 5:29White space
  9. 5:47Line height
  10. 8:08Contrast ratios
  11. 8:53Semantic HTML
  12. 9:06Shell
  13. 9:52Semantic elements
  14. 10:57Inputs
  15. 11:57Logical order
  16. 13:03Take away
  17. 13:21hyperlinks
  18. 16:50hover
  19. 18:03web performance
  20. 18:49website bloat
  21. 19:32website performance
  22. 20:06progressive enhancement
  23. 20:42zooming and scrolling
~/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.