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

RE: [techs] Test 37, 38, 39, 40 and 41

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Thu, 17 Feb 2005 09:37:00 -0600
To: <w3c-wai-gl@w3.org>
Message-ID: <auto-000219121227@spamarrest.com>
Hmmmmm

 

I have been looking at these tests for awhile and wondering why they looked
more detailed than they needed to some times.

This posting clarified it.    I think we sometimes are writing the tests
like text algorithms.   This is fine but we shouldn't name them and describe
them that way.  It is precise but it is not human friendly. 

 

Suggest we have a description in words - followed by a section called
"algorithm' that details the test step by step.                     

 

Also,

where there is a 

-          test for presence of alt tag

-          test for empty tag

-          test for placeholder 

I think we should have a single checklist item that says

"there is alt text and it is not empty or filled with placeholder text."

 

The three tests could then be combined into one three step test - or as
Chris prefers - kept separate but all linked to this one check list item. 

 

Just some thoughts

 

 

 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 

  _____  

From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Alistair Garrison
Sent: Thursday, February 17, 2005 9:10 AM
To: w3c-wai-gl@w3.org
Subject: [techs] Test 37, 38, 39, 40 and 41

 

Dear Chris, All, 

*         Test 37 : Header
<http://www.w3.org/WAI/GL/WCAG20/tests/test37.html>  nesting - H2 must
follow an H1. 

*         Test 38 : Header
<http://www.w3.org/WAI/GL/WCAG20/tests/test38.html>  nesting - H3 must
follow an H2. 

*         Test 39 : Header
<http://www.w3.org/WAI/GL/WCAG20/tests/test39.html>  nesting - H4 must
follow an H3. 

*         Test 40 : Header
<http://www.w3.org/WAI/GL/WCAG20/tests/test40.html>  nesting - H5 must
follow an H4. 

*         Test 41 : Header
<http://www.w3.org/WAI/GL/WCAG20/tests/test41.html>  nesting - H6 must
follow an H5. 

These tests are not rights.

 

Looking at a possible page structure i.e.

 

            H1 - 

                        H2 - 

                                    H3 - 

                                                H4 - 

                                    H3 - 

                                                H4 - 

                        H2 - 

 

You can see that an H3 can follow either an H2 or and H3, and that an H4 can
be followed by H3 or H2. this goes on.

 

The following testable statements should all be answered 'TRUE' for the
header technique to have been properly applied: 

 

*         A single h1 header element has been used? 

*         The next header after an HTML h1 element is an HTML h2 element? 

*         The next header after an HTML h2 element is an HTML h2 element or
an HTML h3 element? 

*         The next header after an HTML h3 element is an HTML h2 element or
an HTML h3 element or an HTML h4 element? 

*         The next header after an HTML h4 element is an HTML h2 element or
an HTML h3 element or an HTML h4 element or an HTML h5 element? 

*         The next header after an HTML h5 element is an HTML h2 element or
an HTML h3 element or an HTML h4 element or an HTML h5 element or an HTML h6
element? 

*         The next header after an HTML h6 element is an HTML h2 element or
an HTML h3 element or an HTML h4 element or an HTML h5 element or an HTML h6
element? 

Hope this makes sense.  Just to check about the h1 header, is it only one
per page??? 

 

Alistair

 

Alistair Garrison 

Managing Director 

Accessinmind Limited UK Filial

 

Tel.: 0046 8 44 65 287
Website: http://www.accessinmind.com
 
IMPORTANT: This e-mail, including any attachments, is for the addressee   
only.  It may contain privileged and/or confidential information.  If it   
has come to you in error, please notify the sender immediately.  If you   
are not the intended recipient you must not use, disclose, copy, print,   
distribute or rely on its contents.  All e-mails and any attachments are
believed, but not warranted, to be virus free.  However, all e-mails   
should be virus checked before being downloaded and we accept no  
responsibility therefore. 

 
Received on Thursday, 17 February 2005 15:37:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:35 GMT