Re: [csswg-drafts] [css-grid-2] Masonry layout (#4650)

@rachelandrew raises this point:

> I would also note that even in the most trivial of demos you start to get layouts with some degree of separation of the content order and layout, enough that it would cause weird jumps if tabbing around a list of products for example.

In my accessibility work (testing with users, audits, etc) I see the reading order and tab order get horribly out of sync from user expectations. Zoom, keyboard-only, screen reader, voice, and mobility-impaired users are all affected by source order that does not match visual order ([1.3.2](https://www.w3.org/WAI/WCAG21/quickref/#meaningful-sequence), [2.4.3](https://www.w3.org/WAI/WCAG21/quickref/#focus-order)). This happens with grid, flex, floats, and absolute positioning but is becoming far more prevalent with grid and flex becoming popular.

>  It was brought up in the CSSWG meeting in Spain where this was discussed that perhaps we should be addressing that disconnect before adding additional layout methods which make it easy for people to cause this problem, and I would tend to agree.

This is where I land.

While I agree defining a standard for this is good, that standard should take into account the demonstrated accessibility challenges with these layout methods and incorporate rules for source versus display order.

This proposal is rather well put together and exciting. I also want it to account for the users who care little for the designer's intent and simply want to use the page.

Also, I agree with putting this under flex or as a standalone that borrows properties, but not grid.

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

Received on Wednesday, 6 May 2020 21:14:46 UTC