W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

RE: CFC Add Zoom Content (formerly Resize content) to Editors Draft

From: James Nurthen <james.nurthen@oracle.com>
Date: Tue, 20 Jun 2017 15:11:09 -0700
To: "'Jim Allan'" <jimallan@tsbvi.edu>, "'Joshue O Connor'" <josh@interaccess.ie>
Cc: "'WCAG'" <w3c-wai-gl@w3.org>
Message-ID: <0b6f01d2ea12$221a5e30$664f1a90$@oracle.com>
+1 – although the Note will need to be expanded to provide more examples of things where 2-d layout is required. I’d suggest this probably belongs in the understanding document rather than a note in the SC.

Another exception which has just come to mind is code editors where the UI cannot simply wrap text for various reasons (languages which use carriage return as the statement terminator so wrapping would cause problems understanding the content, and comment syntax where ther remainder of the line is a comment)

 

From: Jim Allan [mailto:jimallan@tsbvi.edu] 
Sent: Tuesday, June 20, 2017 1:36 PM
To: Joshue O Connor <josh@interaccess.ie>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft

 

+1

 

On Tue, Jun 20, 2017 at 1:54 PM, Joshue O Connor <josh@interaccess.ie <mailto: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://urldefense.proofpoint.com/v2/url?u=https-3A__rawgit.com_w3c_wcag21_resize-2Dcontent-5FISSUE-2D77_guidelines_-23zoom-2Dcontent&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=ELX2morANsauwtoroVrFb2wD7s1u7PsR47DTXqRvJ34&m=olXQfy88oiqEgv86ZSAlQs4oD03aVIJIc1bn0QQ52l0&s=An2vBJ7L7KIFfjnShJ69YLrlv7PNWnW4o68reW9ENn8&e=> 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2002_09_wbs_35422_NewSC-5FApril25-5F2017_results-23xq10&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=ELX2morANsauwtoroVrFb2wD7s1u7PsR47DTXqRvJ34&m=olXQfy88oiqEgv86ZSAlQs4oD03aVIJIc1bn0QQ52l0&s=alLmDrufz3J8Zm4hcd9HEp2D1mtY_Op7ruUApk21C7c&e=> https://www.w3.org/2002/09/wbs/35422/NewSC_April25_2017/results#xq10 
 <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2002_09_wbs_35422_SCs-5FApril-5F11_results-23xq6&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=ELX2morANsauwtoroVrFb2wD7s1u7PsR47DTXqRvJ34&m=olXQfy88oiqEgv86ZSAlQs4oD03aVIJIc1bn0QQ52l0&s=WDDXQWHs5IhKmZ2vzzZ6bYIEtwxqhLdiIpBVB9D49ys&e=> https://www.w3.org/2002/09/wbs/35422/SCs_April_11/results#xq6
GIT Hub:  <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_wcag21_issues_77&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=ELX2morANsauwtoroVrFb2wD7s1u7PsR47DTXqRvJ34&m=olXQfy88oiqEgv86ZSAlQs4oD03aVIJIc1bn0QQ52l0&s=jZ-Qp0QISK2g46yM5VIBTrMzNANYmV3HgbWgZMb3aa4&e=> https://github.com/w3c/wcag21/issues/77 

The new SC can be reviewed here, in the context of the full draft: 

 <https://urldefense.proofpoint.com/v2/url?u=https-3A__rawgit.com_w3c_wcag21_resize-2Dcontent-5FISSUE-2D77_guidelines_-23zoom-2Dcontent&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=ELX2morANsauwtoroVrFb2wD7s1u7PsR47DTXqRvJ34&m=olXQfy88oiqEgv86ZSAlQs4oD03aVIJIc1bn0QQ52l0&s=An2vBJ7L7KIFfjnShJ69YLrlv7PNWnW4o68reW9ENn8&e=> 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/ <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.tsbvi.edu_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=ELX2morANsauwtoroVrFb2wD7s1u7PsR47DTXqRvJ34&m=olXQfy88oiqEgv86ZSAlQs4oD03aVIJIc1bn0QQ52l0&s=2Yui4vA_sM5jBw3SSXv36EmAFZTADm0Gg097ONJbPDI&e=> 

"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Tuesday, 20 June 2017 22:12:12 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:13 UTC