Hi @dizhang168, thanks for your review request. I have an accessibility question: the examples that I've seen in the explainers concentrate on showing how the (keyboard) focus navigation order, and visual rendering order, would be kept in synch when using `reading-flow` (which will be great, especially for masonry layout). The examples I've seen all use interactive elements (specifically `<buttons>`) to demonstrate this. I just want to confirm: would this re-ordering apply to _all_ content (i.e. not just interactive elements), though? (I am thinking of the case where, for example, a screen reader user would be navigating via their virtual cursor, following the order of content in the accessibility tree.) From the explainers, and CSS spec, I imagine the intention is for the ordering to affect all content (not just interactive elements) - effectively the accessibility tree will come from the visual order, rather than source order. Am I understanding this correctly? -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/978#issuecomment-2460752849 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/978/2460752849@github.com>
Received on Wednesday, 6 November 2024 20:51:09 UTC