W3C home > Mailing lists > Public > w3c-wai-au@w3.org > January to March 2010

Re: [Fwd: ATAG review]

From: Jan Richards <jan.richards@utoronto.ca>
Date: Tue, 23 Feb 2010 16:31:20 -0500
Message-ID: <4B844928.7030207@utoronto.ca>
To: w3c-wai-au@w3.org
Here are the four outstanding issues from Cynthia's comments along with 
proposals for addressing them:

  > B.1.2.2 End Product Cannot Preserve Accessibility Information
  > An example would be nice here.  (e.g. saving a structured graphic to
  > raster image format)

JR: I suggest using the example (plus streamlining (a) and (b) wordings):

B.1.2.2 End Product Cannot Preserve Accessibility Information: If the 
web content technology of the output of a web content transformation 
cannot preserve recognized accessibility information (WCAG 2.0 Level A) 
(e.g., saving a structured graphic to a raster image format), then at 
least one of the following are true: (Level A) [Implementing B.1.2.2] 
(a) Option to Save: the author(s) have the option to save the 
accessibility information in another way (e.g., as a "comment", as a 
backup copy of the input); or
(b) Warning: the author(s) are warned that this will result in web 
content accessibility problems in the output.


  > B.2.2.8 Metadata for Discovery: If the authoring tool records the
  > accessibility status of web content, then authors have the option to
  > associate this status with the web content as metadata to facilitate
  > resource discovery by end users. (Level AA)
  >
  > Do any authoring tools do this now?  This seems far less important, and
  > far less proven, than B.2.2.4, yet they're the same level.  I'd make
  > this AAA.

JR: This should probably go on the survey.


  > Implementing Guideline A.3.4 [For the authoring tool user interface]
  > Enhance navigation and editing via content structure
  >
  > It might be good to add a note that these sorts of keyboard
  > optimizations are often very much appreciated by power users, whom one
  > would expect in large numbers among certain types of web authors.

JR: While this is a good point, there are lots of curb-cuts in our 
requirements and if we called out this one we would need to call out the 
others and it isn't our primary goal.

  > B.1.2.2 need an example of when accessibility info can't be preserved.
  > Maybe saving to .jpg?

JR: I suggest updating one of the existing examples:
Make backup of accessibility info:
An authoring tool automatically archives a backup copy of the original 
web content, if accessibility information will be lost (e.g., when a 
structured SVG graphic is saved as an unstructured JPG graphic), and 
notifies the author of both the location of the backup copy and the fact 
that the new content will not be available to any end users who need the 
accessibility information.





-- 
(Mr) Jan Richards, M.Sc.
jan.richards@utoronto.ca | 416-946-7060

Adaptive Technology Resource Centre (ATRC)
Faculty of Information | University of Toronto
Received on Tuesday, 23 February 2010 21:32:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 February 2010 21:32:03 GMT