- From: Nat Tarnoff via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Oct 2020 17:38:53 +0000
- To: public-css-archive@w3.org
If you look again at my first sentence, you'll see my concern is not how a screen reader will relay the information. > Assuming all authors code their masonry grid in a valid reading order, screen reader user who are non-visual will have no problem with it I think @rachelandrew nailed my biggest concern. As the layout adjusts to content, viewport, or any other factor, the visual reading flow as well as the tab order are going to create problems for other sets of disabled users. - Neuro-divergent (cognitive) may get lost on where to focus their attention next - Low vision, no AT may lose where their focus indicator has moved to, or may need to read content from a block that isn't proximate to where they are looking - Low vision, screen reader will be hearing one thing while trying to locate it on the page because it doesn't follow the visual flow of the page - Keyboard only - expect a linear flow of tabstops. If the tabstops follow code order, not visual order, they may get lost trying to track things Using positive `tabindex `seems tempting here, but if item two goes from being on the right of item 1 to below it, while item 3 slides into where 2 was (these are pure hypothetical) the tab order now may make no sense. So we don't want to force that with HTML code or create a similar thing for reading order. We need a method though that will ensure that users will be able to read things in their proper comprehension order and that tab order matches visual order. A thought here could be "item priority" which defaults to code order (or no priority), while other options allow you to specify any number of blocks to accept a value that then makes sure the tab order changes to match the visual. -- GitHub Notification of comment by nattarnoff Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5675#issuecomment-718097362 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 October 2020 17:38:55 UTC