- From: James Teh via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Aug 2024 03:12:11 +0000
- To: public-css-archive@w3.org
From an accessibility perspective, my concerns with this are exactly the same as they were for the inert HTML attribute. They are perhaps stronger concerns here because CSS has (at least historically) been primarily associated with presentation, not semantics, so the chances of someone doing this without considering semantics are higher. The risk here is that someone will use this for some unintended semantic purpose where the content is actually semantically relevant but ends up being hidden from a11y APIs. This is particularly problematic for the CSS inertness property (proposed option 1), probably a bit less so for the other proposed options. The impact of this risk is very severe because this content would be entirely inaccessible to some users with absolutely no recourse. For HTML, this was addressed by adding clear, firm, *normative* [guidance about when it is inappropriate to use inert](https://github.com/whatwg/html/pull/8122). If something like this is added to CSS, I think it is critical that similar normative guidance is included. I understand there may be reluctance to do this given that CSS is primarily associated with presentation, but since this has such a severe impact on semantics, I think omitting such guidance could be very harmful for accessibility. -- GitHub Notification of comment by jcsteh Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10711#issuecomment-2306101100 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 August 2024 03:12:12 UTC