Processing ATAG2 Comments (comment: "Search functions")

Comment at:
http://lists.w3.org/Archives/Public/public-atag2-comments/2009May/0001.html

My comments marked with JR:

========
> Guideline A.3.5 [For the authoring tool user interface] Provide text
> search.
> 
> Both when editing contents produced by others and when writing my own
> things I'm searching a lot (I'm a screen reader user, and screen reader
> users probably are search experts:-)!). Therefore I think this is a very
> important guideline.
> 
> When working with contents produced by others I also often search for
> attributes: bold, underline, spesific colours, font size, ... These
> attributes are hard to find when using a screen reader (at least in
> contents using several different markings). Therefore I also think
> attribute/formatting search should have been included in ATAG.

JR: Since markup attributes and their values are "information that is 
text" , they would already be covered by checkpoint A.3.5.1 unless the 
authoring tool could not be used to modify the content (e.g., a WYSIWYG 
HTML editor might display SVG without being able to edit it). But it 
might help readability to change to the e.g. to:

"(e.g., text content, text alternatives for non-text content, metadata, 
markup elements, markup attributes, etc.)."

We MIGHT consider another checkpoint if we wanted to add the condition 
that the search work on views where the elements/attributes were 
rendered. Currently condition (d) allows the tool to move the user to 
the view in which the elements/attributes are displayed as text.


Cheers,
Jan

-- 
Jan Richards, M.Sc.
User Interface Design Lead
Adaptive Technology Resource Centre (ATRC)
Faculty of Information
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896

Received on Tuesday, 26 May 2009 15:48:44 UTC