agree it is too strict. Two thoughts Jason 1) linearizing a table must be done in both directions since sometimes you want to compare columns and sometimes rows. if you want to do both — then only the table works I worry that tables are tables for a reason — (and not linear lists) I would suggest that if you forces tables to linearize that were too wide for the page — you would see a user revolt amongst most users. And that still leaves Maps and all the other examples. and we can’t use lists for exceptions We need to figure this out (how to clearly define when it should or should not apply) without using any judgement. And we also cannot include the phrase “user can” in the SC since we don’t know who the user is… (another trap we kept falling into and climbing out of in the WCAG 2.0 work. gregg > On Jul 4, 2016, at 3:22 PM, White, Jason J <jjwhite@ets.org> wrote: > > > <> > From: David MacDonald [mailto:david100@sympatico.ca <mailto:david100@sympatico.ca>] > Sent: Monday, July 4, 2016 3:06 PM > > SC X.X.X If text is resized up to 200% (or 300, 400, 800%?) without assistive technology, the layout of the Web page ensures that it can be viewed in its entirety without requiring the user to scroll the viewport horizontally, and without loss of content or functionality, unless a particular presentation of text is essential to the information being conveyed. > [Jason] Having thought about this a little further, I suspect it’s too strict. For example, data tables can be linearized, hence one could argue that the tabular format isn’t essential to conveying the information, and perhaps not even to the user’s carrying out of tasks that can reasonably be expected to be performed. However, it may make the performance of these tasks more difficult for the user than preserving the spatial layout and requiring horizontal scrolling. > > Perhaps we could say “unless a spatial layout that requires such scrolling is substantially more effective than any alternative layout in enabling users to read and interact with the content”. > Let’s keep thinking about this and refine the text further. > > > This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. > > > Thank you for your compliance. >
Received on Monday, 4 July 2016 20:35:09 UTC