~/talk

The Dark Side of the Grid

Talkat FrontEnd Con 2018 · 2018-12-04..12-05· [css]
slides:none on file

CSS Grid is powerful but risky: visual reordering (explicit placement, order, auto-flow, template-areas) breaks DOM/tab/screen‑reader order and confuses keyboard and magnifier users; about 15.7% of people reportedly use keyboards on mobile. Browsers shipped Grid rapidly (Chrome/Firefox in March 2017, Edge Oct 17) but subgrid unsupported and display:contents bug in Chrome/Safari/Edge can remove elements from the accessibility tree. Old IE grid needs explicit placement; Autoprefixer fakes gaps with extra rows. Use progressive enhancement, test with keyboard across breakpoints.

AI-written summary · about

  1. 0:00Start
  2. 1:07CSS Grid Layout?
  3. 3:15A Brief overview of Grids History
  4. 4:59Grid-related properties and value
  5. 7:09Visual Order
  6. 9:24Who uses the keyboard for navigation?
  7. 10:15Who uses screen readers for navigation?
  8. 12:00$ order property
  9. 15:49Our options
  10. 17:28So...what do we do?
  11. 25:14Properties: Level 1 vs. MS Spec
  12. 27:39Autoprefixer gotchas
  13. 30:55Responsible use of Grid
~/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.