- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Tue, 20 Jun 2017 15:36:25 -0500
- To: Joshue O Connor <josh@interaccess.ie>
- Cc: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CA+=z1Wn8soGn-kzpNXi=1KojshSHx68JsReJ9ixAhq_rQ=pp6A@mail.gmail.com>
+1 On Tue, Jun 20, 2017 at 1:54 PM, Joshue O Connor <josh@interaccess.ie> wrote: > Hi all, > > I placed older SC text into the CFC - The current SC text for this one is: > [1] > > Content can be zoomed to an equivalent width of 320 CSS pixels without > loss of content or functionality, and without requiring scrolling on more > than one axis except for parts of the content which require two-dimensional > layout for usage or meaning. > NOTE > > 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS > pixels wide at 400% zoom. For web pages which are designed to scroll > horizontally, the 320px should be taken as the height rather than width. > 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. > > [1] https://rawgit.com/w3c/wcag21/resize-content_ISSUE-77/ > guidelines/#zoom-content > > Thanks > > Josh > > > Joshue O Connor wrote: > > Call For Consensus — ends Friday June 23rd at 1:00pm Boston time. > > The Working Group has reviewed and approved a Success Criterion for > inclusion in the Editor’s Draft: "Zoom Content (was Resize Content)" with > the goal of obtaining additional input external to the working group. > > SC TEXT: > > "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. > " > Survey results: > https://www.w3.org/2002/09/wbs/35422/NewSC_April25_2017/results#xq10 > https://www.w3.org/2002/09/wbs/35422/SCs_April_11/results#xq6 > GIT Hub: https://github.com/w3c/wcag21/issues/77 > > The new SC can be reviewed here, in the context of the full draft: > https://rawgit.com/w3c/wcag21/resize-content_ISSUE-77/ > guidelines/#zoom-content > > If you have concerns about this proposed consensus position that have not > been discussed already and feel that those concerns result in you “not > being able to live with” this decision, please let the group know before > the CfC deadline. > > Thanks > -- > Joshue O Connor > Director | InterAccess.ie > > > -- > Joshue O Connor > Director | InterAccess.ie > -- Jim Allan, Accessibility Coordinator Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Tuesday, 20 June 2017 20:37:00 UTC