- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Mon, 06 Oct 2025 07:36:45 +0000
- To: public-css-archive@w3.org
If the full text is displayed somehow (including in a tooltip), then I'd think about it differently, but as specified, that is not the case, the remainder of the content is just not visible. In general, I think screen readers, as their names indicates, are intended to give an audio rendition of what's on screen, not an independent audio rendition of the source document regardless of how it's styled. If something is invisible yet read aloud, I believe that can be confusing, for instance in cases where a (partially) sighted user is accessing the page with a screen reader, and cannot easily reconcile what they're hearing with what they're seeing, or in case where a blind user discusses the content of the page with a sighted user, and they have a different understanding of what's there. > Just stopping in the middle of a sentence or even a word seems pretty bad for UX. That is exactly the UX that a sighted user is getting, though. As long as the ellipsis or some audio equivalent is rendered, I'm not certain that's an issue. That said, I am not personally a screen reader user, nor have I don't user research on this specific question, so my guesses as to what's best are just that: guesses. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12859#issuecomment-3370299734 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 October 2025 07:36:46 UTC