- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sun, 12 May 2024 22:51:16 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-position-1] Improve accessibility guidance == The description here: https://drafts.csswg.org/css-anchor-position-1/#accessibility spends several paragraphs saying 3 useful things: - Anchor positioning doesn't affect screenreader order (navigation order is not mentioned), so don't rely on it to create semantic connections. - The “Popover API” (which is named but not linked, explained, or illustrated anywhere in this spec) can be used to perform semantic linking when that's appropriate. - The aria-describedby and aria-details attributes might also help. Other than that, there are no examples (of either good or bad practices), or concrete actionable guidance that would help an author actually do things correctly. The goal of the section should be to help authors understand the implications of what they're doing, identify what tools they have available to do a good job, and explain when and how to use them. They should come away knowing how to think about the interaction of accessibility and anchor positioning, and be able to implement the guidance, at least for straightforward cases such as the basic use cases that drove the spec. I don't think it's fulfilling that goal yet. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10311 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 12 May 2024 22:51:19 UTC