IBM comments on Gateway to Techniques July 30, 2004, public draft

Here are the public comments from IBM in response to the Gateway to 
Techniques document

1) There is some confusion about the purpose of this document.  Reading 
the document certainly helps to clarify that this is the 
rationale/guidance for the techniques.  A  paragraph in the beginning of 
the document which declares its purpose better would help.  This will be a 
very useful document when completed.  Some folks feel that "Gateway" 
doesn't really make sense as the title of the document. 

2)  1.1 L1 SC1 contains an editorial note regarding "Ask, "What is the 
function of the non-text content?" and express that function clearly and 
concisely."   One suggestion for changing this to:
 "Ask, "What is the function of the non-text content?" and express that 
function.   Do it as clearly and concisely as possible. 
 I would suggest that this is now testable, with a little subjective 
guidance. 

3) Regarding "Editorial Note: In this draft, part C of the Level 1 success 
criterion for Guideline 1.1 is divided into two techniques this one (music 
without words) and the next (visual art). Is this confusing? Should they 
merge into one?"  At least two folks responded with a preference to keep 
them separate.

4)  Consider adding "Is it already described in the accompanying text?" as 
one of the questions to ask after the statement, "If the non-text content 
does not provide functionality or convey information, then mark the 
non-text content so that it may be ignored. Ask, "Will it be distracting? 
Is the non-text content necessary to understand the rest of the content? 
Is there another way to create the effect?" 

5) In the future work section a question asks, "How do we make it clear 
that there are some techniques that are sufficient and some that are 
optional?".  Consider labeling each technique Required/Sufficient and 
Optional. 

6) At least one person prefers the style in the CSS and HTML Techniques 
documents to the style used in the Gateway document.

7) TYPO.  In 1.1 Text Alternatives - music without words.  In the task 
description the word "Deaf" should not be capitalized.

8) For  the "Text alternatives for content that doesn't provide 
functionality" section there is confusion about what  "Create decorative 
effects with more accessible methods" means.  If they are really just 
decorative, why wouldn't you just want to ignore them like null alt text? 
I think this needs an example, as it doesn't seem to be covered by the 
techniques listed below it.


Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com