Edit comment LC-469 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-866 Next: LC-1062

Comment LC-469: Comment Shortname:; Commenter: Greg Gay <g.gay@utoronto.ca> on behalf of ATRC UofT; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Comment (Including rationale for any proposed change):
There is currently no item number relevant to this comment. Technique G96 seems to be the only place within the WCAG 2.0 documents that mentions anything about "relative positioning", or more specifically use of relative measures. Using relative measures is particularly important for low vision users who use a browser function to blow up the text size. It is also important for those using small screens like PDAs.

Proposed Change:
This requirement seems to fit best under WCAG principle 4, regarding robust. Perhaps a new guideline 4.1.3, at level 2. something like "Ensure that content can be resized without losing its symmetry" Then in the techniques describing the use of relative measures for sizing block level items, text, images, etc.; Related issues: 564
(space separated ids); WG Notes: [TEAMB] Submitted from Team A 5/23/06 ----------------------------- 1) @@ add the following advisory technique "Using relative positioning." to guideline 1.3 2) @@ check with Ben to incorporate the C6 idea. BBC: C6: Positioning content based on structural markup" - currently includes only an example of absolute positioning, but could be expanded to address both or retitled to be specific to absolute positioning. 2) close item with {Partial Accept} "An advisory technique "Using relative positioning." has been added to guideline 1.3 to explain that allowing pages to maintain relative layout as fonts are increased is of value to those with low vision that must scale fonts but do not want the page to increase in width beyond the width of the screen." --------- Surveyed and discussed 5/25/06 and put on HOLD @@ ACTION: Gregg check with Ben to incorporate C6 idea for LC-469 [recorded in http://www.w3.org/2006/05/25-wai-wcag-minutes.html#action01] resolution: put LC-469 put on hold because more comments will likely come in. Discussed in the 25 January 2007 telecon: accepted by unanimous consent http://www.w3.org/WAI/GL/2007/01/25-wai-wcag-minutes.html {accept} DONE Add new level 2 SC 1.4.5 : Visually rendered text can be resized without assistive technology up to 200 per cent without loss of content or functionality. DONE Add new level 3 SC 1.4.6: Visually rendered text can be resized without assistive technology up to 200 per cent without loss of content or functionality in a way that does not require the user to scroll horizontally. @@Add HTML, CSS technique "Using percent for font sizes" DONE Add CSS technique "Using named font sizes" DONE Add HTML, CSS technique "Using em units for font sizes" DONE Add HTML, CSS, Script technique "Calculating size and position in a way that scales with text size" DONE Add general technique "Ensuring that all content can be scaled uniformly"; Resolution: Although resizing is primarily a user agent function, we have added new success criteria to address the author's responsibility for supporting text resizing: Level AA: Visually rendered text can be resized without assistive technology up to 200 percent and down to 50 percent without loss of content or functionality. Level AAA: Visually rendered text can be resized without assistive technology up to 200 percent and down to 50 percent without loss of content or functionality and in a way that does not require the user to scroll horizontally.; (Please make sure the resolution is adapted for public consumption)