W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2006

RE: About tests 37-41 (headers) *wkey

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Tue, 2 May 2006 11:29:43 -0500
To: "'Chris Ridpath'" <chris.ridpath@utoronto.ca>, "'Johannes Koch'" <koch@w3development.de>, "'WCAG'" <w3c-wai-gl@w3.org>
Message-ID: <008d01c66e05$9e911d40$ee8cfea9@NC6000BAK>

Hmmm

Do you mean does WCAG 2.0 forbid this?  

Or do you mean "is there and accessibility rule somewhere". 

If you mean does WCAG 2.0 forbid this you need to look ONLY at the success
criteria.  They are the only thing that forbids.

If you want to know if the working group documented something specific that
the success criteria forbid - look at the Common Failures.    

Techniques only show how to do things. Never what is or isn't allowed. 

Does that help clarify? 



Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
The Player for my DSS sound file is at http://tinyurl.com/dho6b 

-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Chris Ridpath
Sent: Tuesday, May 02, 2006 11:08 AM
To: Gregg Vanderheiden; 'Johannes Koch'; 'WCAG'
Subject: Re: About tests 37-41 (headers)


Gregg wrote:
> Techniques NEVER forbid anything.  A technique cannot forbid.
>
Perhaps "forbid" is the wrong word.

The question that started this was "Is there an accessibility rule that
avoids nesting forms?"

I suggested that technique G134[1] covered this.

Do you agree?

Cheers,
Chris


[1] http://www.w3.org/TR/WCAG20-TECHS/#G134
Received on Tuesday, 2 May 2006 16:29:48 GMT

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