- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Fri, 26 May 2017 12:58:00 +0000
- To: WCAG <w3c-wai-gl@w3.org>
> Content can be displayed at a minimum width My concern is over the term "minimum". It could be read that supporting something over the minimum passes. Could it be removed? Jonathan Jonathan Avila Chief Accessibility Officer SSB BART Group jon.avila@ssbbartgroup.com 703.637.8957 (Office) Visit us online: Website | Twitter | Facebook | LinkedIn | Blog Download our CSUN Presentations Here! The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited. -----Original Message----- From: Alastair Campbell [mailto:acampbell@nomensa.com] Sent: Thursday, May 25, 2017 7:45 PM To: WCAG Subject: Zoom content updates Hi everyone, Based on the call earlier I've made some updates to the SC text: https://github.com/w3c/wcag21/issues/77 The main change is to switch from saying "allow for this much zoom", to saying "ensure it works at this width". The main reason for this is for testability, as soon as you say it should not create horizontal scrolling then you need to define either: - The starting size (e.g. 1280px) and the zoom factor (400%), or - The end size (e.g. 320px). None of these values were in the SC text, so for testability we'd have to include either: "Starting at 1280px zoom content by 400% without loss of...", or "Content can be displayed at a minimum width of 320 CSS pixels without loss of..." I think the second approach is more effective, and if it starts with "Zoom content", it still has a connection to the user-requirement. It also side-steps the (perceived) issue of how you test on smaller screens. So the SC text is now: ------------------ Content can be displayed at a minimum width of 320 CSS pixels without loss of content or functionality, and without requiring scrolling in the direction of text except for parts of the content which require two-dimensional layout for usage or meaning. Note: The width of 320 CSS pixels is equivalent to a browser width of 1280 pixels wide at 400% zoom. Note: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content. ------------------ I just added the first note, I'm not wedded to it, do you think we need it or can we explain that in the understanding? Any comments here please: https://github.com/w3c/wcag21/issues/77 Cheers, -Alastair
Received on Friday, 26 May 2017 12:58:37 UTC