- From: Granquist, Christina M <christina.granquist@usbank.com>
- Date: Mon, 8 Jul 2019 15:17:50 +0000
- To: Mitchell Evan <mtchllvn@gmail.com>, "Charles 'chaals' (McCathie) Nevile" <chaals@yandex.ru>
- CC: WAI Interest Group <w3c-wai-ig@w3.org>
- Message-ID: <221CAD31-8412-4BBF-930F-0966B3ED0B9A@usbank.com>
Understanding Success Criterion 1.4.4 Resize Text<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_WCAG21_Understanding_resize-2Dtext.html&d=DwMFaQ&c=1hIq-C3ayh4zm6RZ7m4R2A&r=rPRXoPtZnwPOcJRAWwcp5j8F5oVccBZjq9-nnXNTGD8&m=uZg8JFcqpdmEUbDolrbborQMrpsfhS-MUQiezdBR5JY&s=4P_EE9xZL7-UYjPqjqskdZjsvfisIz8A3VaUMkfckI8&e=> offers an answer which I agree with. The truncated content should offer a control which enables the full content. I'll quote the full paragraph here because it's very relevant. "Some user interface components that function as a label and require activation by the user to access content are not wide enough to accommodate the label's content. For example, in Web mail applications the subject column may not be wide enough to accommodate every possible subject header, but activating the subject header takes the user to the full message with the full subject header. In Web-based spreadsheets, cell content that is too long to be displayed in a column can be truncated, and the full content of the cell is available to the user when the cell receives focus. The content of a user interface component may also become too wide in user interfaces where the user can resize the column width. In this type of user interface component, line wrapping is not required; truncation is acceptable if the component's full content is available on focus or after user activation and an indication that this information can be accessed, is provided to the user in some way besides the fact that it is truncated." -When considering this problem on mobile and in a non editable element, where content is still truncated. How would this problem be handled, considering the smaller screen and also that mouse hover, to reveal the extended label would not be possible. Additionally, having multiple show all buttons in a non editable table would clutter up the interface. The above quote seems relevant to editable and or actionable content but how would this same issue be handled when considering content that is not actionable (for example, an informational table)? Best, Christina From: Mitchell Evan <mtchllvn@gmail.com> Date: Saturday, July 6, 2019 at 12:37 AM To: "Charles 'chaals' (McCathie) Nevile" <chaals@yandex.ru> Cc: WAI Interest Group <w3c-wai-ig@w3.org> Subject: [EXTERNAL] Re: Does text-overflow fail reflow and/or text-spacing Resent-From: <w3c-wai-ig@w3.org> Resent-Date: Saturday, July 6, 2019 at 12:32 AM Understanding Success Criterion 1.4.4 Resize Text<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_WCAG21_Understanding_resize-2Dtext.html&d=DwMFaQ&c=1hIq-C3ayh4zm6RZ7m4R2A&r=rPRXoPtZnwPOcJRAWwcp5j8F5oVccBZjq9-nnXNTGD8&m=uZg8JFcqpdmEUbDolrbborQMrpsfhS-MUQiezdBR5JY&s=4P_EE9xZL7-UYjPqjqskdZjsvfisIz8A3VaUMkfckI8&e=> offers an answer which I agree with. The truncated content should offer a control which enables the full content. I'll quote the full paragraph here because it's very relevant. "Some user interface components that function as a label and require activation by the user to access content are not wide enough to accommodate the label's content. For example, in Web mail applications the subject column may not be wide enough to accommodate every possible subject header, but activating the subject header takes the user to the full message with the full subject header. In Web-based spreadsheets, cell content that is too long to be displayed in a column can be truncated, and the full content of the cell is available to the user when the cell receives focus. The content of a user interface component may also become too wide in user interfaces where the user can resize the column width. In this type of user interface component, line wrapping is not required; truncation is acceptable if the component's full content is available on focus or after user activation and an indication that this information can be accessed, is provided to the user in some way besides the fact that it is truncated." On Fri, Jul 5, 2019 at 12:48 PM Charles 'chaals' (McCathie) Nevile <chaals@yandex.ru<mailto:chaals@yandex.ru>> wrote: On Fri, 05 Jul 2019 15:13:12 +0200, Joppe Kroon <J.Kroon@topdesk.com<mailto: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/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opera.com_mail_&d=DwMFaQ&c=1hIq-C3ayh4zm6RZ7m4R2A&r=rPRXoPtZnwPOcJRAWwcp5j8F5oVccBZjq9-nnXNTGD8&m=uZg8JFcqpdmEUbDolrbborQMrpsfhS-MUQiezdBR5JY&s=_2wYJDiUs9KHiZWPZsfIf10nblYRq1SHe8sa5edpp4I&e=> -- Mitchell Evan mtchllvn@gmail.com<mailto:mtchllvn@gmail.com> (510) 375-6104 mobile U.S. BANCORP made the following annotations --------------------------------------------------------------------- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ---------------------------------------------------------------------
Received on Monday, 8 July 2019 15:18:23 UTC