2.4.1 thru 2.4.4 Techniques proofreading

I have reviewed all of the techniques for 2.4.1, 2.4.2, 2.4.3, and 2.4.4. 
Here are the issues I found.

Using structural elements to group links. - issues previously submitted to 
Gregg. 

C6: Positioning content based on structural markup has extra example 
headings. There is really only one example with 3 parts.  The headings for 
example 2 and example 3 should be removed. 

G125: Providing links to navigate to related Web units - the link in the 
example, discussion of Baseline and WCAG 2.0 ,  does not load

H59: Using the link element and navigation tools   - Example 1 should not 
be there.  It is from a general technique about links and doesn't contain 
specific HTML information about using the link element.   Example 1 was 
not included in the wiki version of this technique. 

H30: Providing link text that describes the purpose of a link for anchor 
elements  - the link in the description, Using null alt text and no title 
attribute on img elements for images that are purely decorative , does not 
go to that technique. 

H20: Identifying the purpose of a link using link text and text associated 
with the parent element of the link 
1) The following paragraph appears twice  in the User Agent and Assistive 
Technology Support Notes section: The "speak parent element" command in 
Firevox (Ctrl+Shift+u) supports Example 3. This keystroke works without 
changing the focus. Firevox is a free screen reader designed specifically 
for Firefox 1.0 and later. It supports Windows, Macintosh, and Linux. 
2)Minor nit: example 1 requires scrolling the page horizontally to view. 

C7: Supplementing link text with hidden text - Example 1 heading is not 
needed. This is the CSS that is used for the following example and is not 
an example by itself. 


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