Re: [csswg-drafts] [css-grid] Masonry layout in CSS Grid 3 has potential to cause accessibility problems with reading order. (#5675)

> The benefit I can see to building a task board with grid-lanes is that items can be moved from one column to another using styling rather than DOM manipulation

That seems a bad practice. See e.g. https://drafts.csswg.org/css-display-4/#reading-order

> The source document should express the underlying logical order of elements. The [reading-flow](https://drafts.csswg.org/css-display-4/#propdef-reading-flow) and [reading-order](https://drafts.csswg.org/css-display-4/#propdef-reading-order) properties exist for cases where a given document can have multiple reading orders depending on layout changes, e.g. in response to [media queries](https://drafts.csswg.org/mediaqueries-5/#media-query). In such cases, the most common or most fundamental reading order should be encoded in the source order so that the document is sensical without CSS.

-- 
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5675#issuecomment-4846180427 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 30 June 2026 17:24:21 UTC