# Visual Layout Must Preserve Sequential Meaning and Focus Order ## Claim A layout algorithm is inaccessible when its visual sequence diverges from DOM reading and keyboard focus order. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Applies when cards or controls have a meaningful visual sequence and contain focusable content. - Decorative collections without sequential meaning may tolerate independent placement. - CSS controls that reduce divergence still require keyboard and assistive-technology testing at realistic viewport sizes. ## Evidence [[3. Resources/Readwise/Articles/Your Grid Lanes will likely fail WCAG 2.4.3 - Manuel Matuzovic]] shows that shortest-column placement in CSS Grid Lanes can separate visual order from DOM focus order and that `flow-tolerance` may trade one navigation problem for another. ## Links - [[Watching a System Run Beats Reading It]] — applies-in: keyboard traversal exposes ordering failures that a stylesheet review can miss. - [[A Defense Experts Fail Is Not a Defense for Users]] — extends: a technically valid DOM does not rescue a confusing user-visible sequence. - [[Zet · Feature friction analysis improves UX decisions]] — supports: focus jumps are measurable task friction, not a cosmetic defect. - [[3. Resources/MOCs/Accessibility & Disability Inclusion MOC]] — the layout constraint underneath most keyboard and screen-reader failures - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — applies-in: the MOC lists this note under Synthesis additions.