Re: [csswg-drafts] [css-overflow] Line-clamp and screen readers (#12859)

The CSS Working Group just discussed `[css-overflow] Line-clamp and screen readers`, and agreed to the following:

* `RESOLVED: line clamped material is left hidden to both screens and screen readers`

<details><summary>The full IRC log of that discussion</summary>
&lt;ydaniv> andreubotella: not sure I agree with my last post on that issue.<br>
&lt;ydaniv> ... the hidden content after the clamping is set to invisible, and defined in display<br>
&lt;ydaniv> ... things that require interaction are not rendered<br>
&lt;ydaniv> ... it would make sense to behave like that<br>
&lt;ydaniv> ... after discussing with a11y folks at Igalia, clamp depends on layout, it's not only the max-height, also aspect-ratio<br>
&lt;ydaniv> ... there are many things that can determaine where to clamp<br>
&lt;ydaniv> ... like in middle of paragraph, my concern is how to expose it to a11y tree<br>
&lt;ydaniv> ... I think this is more of an ongoing conversation<br>
&lt;ydaniv> ... not sure what you would see if the elippsis is there<br>
&lt;emilio> q+<br>
&lt;florian> q+<br>
&lt;ydaniv> ... like if there's a different width of the window etc.<br>
&lt;astearns> ack emilio<br>
&lt;ydaniv> emilio: seems to me there are precedents for this<br>
&lt;ydaniv> ... like for text-overflow for text that is not selectable<br>
&lt;ydaniv> ... so just match it<br>
&lt;ydaniv> s/text-overflow/text-overflow: clip/<br>
&lt;ydaniv> andreubotella: so for text-overflow: ellipsis, on initial behavior for selection etc. it's described as ...<br>
&lt;astearns> ack florian<br>
&lt;ydaniv> florian: not completely certain that we want to take text-overflow as a model here<br>
&lt;ydaniv> ... in general screen readers read the screen, if it's invisible it would make sense to hide there as well<br>
&lt;ydaniv> ... text-overdlow in the inline direction is meant to be interactive and scrollable, might bring certain consideration<br>
&lt;andreubotella> s/on initial behavior for selection etc. it's described as .../the ellipsis is probably not copied when copying the selection, and I assume AT is the same<br>
&lt;ydaniv> ... conceptually anything hidden should be removed from a11y tree, from my opinion<br>
&lt;ydaniv> fantasai: in general a11y ppl say we should keep both visual and a11y tree similar<br>
&lt;emilio> q+<br>
&lt;ydaniv> astearns: shall we resolve that content hidden by clamp line is not available for a11y tree?<br>
&lt;ydaniv> astearns: there are impl concerns<br>
&lt;ydaniv> emilio: no objections to making it work, a bit tricky<br>
&lt;ydaniv> ... might be a bit of a gray area but not objecting<br>
&lt;ydaniv> andreubotella: from me the same, and if we can make it work seems fine to me<br>
&lt;ydaniv> PROPOSED RESOLUTION: line clamped material is left hidden to both screens and screen readers<br>
&lt;lwarlow> +1<br>
&lt;ydaniv> astearns: objections?<br>
&lt;ydaniv> +1<br>
&lt;ydaniv> RESOLVED: line clamped material is left hidden to both screens and screen readers<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12859#issuecomment-3960669124 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 25 February 2026 17:02:23 UTC