- From: James Craig via GitHub <noreply@w3.org>
- Date: Fri, 13 Mar 2026 05:03:26 +0000
- To: public-css-archive@w3.org
Yes. Let’s say we have the following sentence: “Lorem ipsum dolor sit amet, consectetur adipiscing elit.” And in the default font size the line clamp renders: > Lorem ipsum dolor sit > amet, consectetur… And in the case of a low-vision, sighted screenreader user (who uses a combination of VoiceOver, Zoom, and HoverText) the font might be extra large, rendering only the following: > Lorem > ipsum… But a different sighted user with better than average vision (or a visually impaired person with high clarity but low peripheral vision) could also set their font size to xx-small, and the whole sentence would be rendered: > Lorem ipsum dolor sit amet, > consectetur adipiscing elit. In the above three possible renderings of this single hypothetical scenario, the low vision screen reader user should not be penalized for displaying large text, especially if the large text benefits their remaining usable vision. Clamping the Accessibility API value to the visibly rendered text would prevent their screen reader and tools like HoverText from voicing the text, the same text that their sighted colleagues can read visually. Moving on from the low vision screen reader user example, many fully blind screen reader users don’t always know (nor should they have to care) whether their browser window is rendered large or small. Changing what is exposed to the accessibility tree this way could leave them with unpredictable results. One day being able to access content at the end of the line clamp, and the next having that content missing due to it being rendered in a slightly smaller window. -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12859#issuecomment-4052707482 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 March 2026 05:03:27 UTC