- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Feb 2023 07:55:04 +0000
- To: public-css-archive@w3.org
> One of my goals here was to make it impossible for an author to apply `* { use-layout-order-as-speech-order }` and thereby convince themselves that a) they don't need to manage source order correctly and b) they've solved accessibility properly for the whole page.
I get that, however it does seem odd to be making people do more work just in case they do something bad. Having `reading-order: <integer>` is only useful in those cases where the developer doesn't want the document order OR the grid/flex-modified order. I can't think of any good cases for that, so we are adding this additional complexity purely to make it harder for developers to do a thing they want to do. Do we do this anywhere else?
I think it would be worth bringing this issue back to the WG, my comment above and @fantasai's response explain the issue reasonably well I think.
--
GitHub Notification of comment by rachelandrew
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/8257#issuecomment-1427493824 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 February 2023 07:55:06 UTC