- From: Charles 'chaals' (McCathie) Nevile <chaals@yandex.ru>
- Date: Fri, 05 Jul 2019 21:41:53 +0200
- To: w3c-wai-ig@w3.org
On Fri, 05 Jul 2019 15:13:12 +0200, Joppe Kroon <J.Kroon@topdesk.com> wrote: > I am currently in the process of auditing our software and ran into some > elements where _more_ of the text will be truncated >when zooming or > changing text spacing. > > These elements display the first few words of (end-user provided) text > truncated to the available width using the CSS ‘text->overflow’ property. > > The reflow and text-spacing criteria mention that a user should be able > to zoom or increase text spacing without loss of >content, so, in a > strict interpretation, these elements would fail. > > When I’m in a lenient mood, I feel that the truncated text was already > not expected to be provided in it’s entirety, so the >additional loss of > content would be acceptable. > > Would you fail or accept this situation? Generally I would fail it, unless the purpose is really to get a sense of what happens without the text itself being legible. (My assumption is that most of the time that is unlikely to bne part of the use case. In any event, even when it is it is usually pretty frustrating). That's a hard line to take, I think. It is a case I think can be argued reasonably easily against the written requirements, but I would prefer not to spend a lot of time on it since it seems that it is first based on a bad practice that should be fixed anyway, and second otherwise it is probably not a very impactful problem. > Would it be worth adding this situation to the reflow/text-spacing > understanding documents? Probably, if we can reach agreement on an answer... cheers Chaals > Regards, > Joppe Kroon -- Using Opera's mail client: http://www.opera.com/mail/
Received on Friday, 5 July 2019 19:42:23 UTC