- From: Eric Eggert via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Nov 2023 08:14:54 +0000
- To: public-css-archive@w3.org
Thumbs down for this suggestion. Content hidden from screen but available to assistive technologies (not only to screen readers) is [a hack that needs to be resolved, not enshrined](https://www.scottohara.me/blog/2023/03/21/visually-hidden-hack.html), as @scottaohara so eloquently put it. Hidden content seems great when it is built in, but through updates by (visual) developers the content is often out of sync. And it also can be an obstacle to screen reader users who see the screen. Making it easier for developers to employ such a hack will make these issues even more likely. Content that is not visible on the screen, gets out of sync and is misleading already accounts for a sizeable percentage of accessibility issues. Also, these practices stem from a time when ARIA was much less available and so hidden text used to be the only option. Now ARIA labels etc. can be used instead in most, if not all, times when hidden additional information is needed. Don’t make the lives of testers and especially disabled people harder by making it easier for developers to use these kinds of non-best practices. -- GitHub Notification of comment by yatil Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9579#issuecomment-1803346126 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 November 2023 08:14:56 UTC