- From: Wayne Dick <wayneedick@gmail.com>
- Date: Sat, 6 Jul 2019 11:57:28 -0700
- To: "Charles 'chaals' (McCathie) Nevile" <chaals@yandex.ru>
- Cc: W3C WAI ig <w3c-wai-ig@w3.org>
- Message-ID: <CAJeQ8SAY-B-0d8bM=8nd0MuucTV6psKtLtKPXi+-eiJv9CPw9Q@mail.gmail.com>
I have done a lot of testing with spacing, and here is what I have found: 1. If you include a reasonable space for your field (say 20%), it usually will not fail with the maximum settings for spacing. 2. Truncated content is really bad. It frequently wipes out the most important part of the text content. 3. Line spacing is more of a problem than letter or word spacing. This really occurs with older grid configurations that do not use the CSS grid techniques. I base these observations on all my web usage since 2.1 was in final draft. I use the following app to produce changes in spacing, font family and color. Only the spacing is supported by 2.1, but I try to change color and font just for my own needs. http://nosetothepage.org/N2tPAssist/ Best, Wayne On Fri, Jul 5, 2019 at 12:48 PM Charles 'chaals' (McCathie) Nevile < chaals@yandex.ru> wrote: > 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 Saturday, 6 July 2019 18:58:27 UTC