RE: Navigational features

I agree with Loretta's and Gregg's suggestion that we list Jim's example
under Common Failures. In fact, it could be listed under both 2.4.1 and
1.3.1, I think.

John 



"Good design is accessible design." 
John Slatin, Ph.D.
Director, Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, f 512-495-4524
email jslatin@mail.utexas.edu
web http://www.utexas.edu/research/accessibility/


 


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Jim Thatcher
Sent: Friday, December 02, 2005 2:38 pm
To: 'Ben Caldwell'; w3c-wai-gl@w3.org
Subject: RE: Navigational features


I cave. Thanks for thinking about it.

Jim
 
Accessibility Consulting: http://jimthatcher.com/
512-306-0931

-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Ben Caldwell
Sent: Friday, December 02, 2005 2:19 PM
To: w3c-wai-gl@w3.org
Subject: Re: Navigational features


I don't think a class name on a non-heading element is enough to meet
this SC with our definition of programmatically determined because there
aren't any user agents (or assistive technologies) that are able to
identify an element with a randomly selected class name as a heading (or
any other type of structure).

So, in Jim's example, my feeling is that these items should be marked as
headings in order to meet the SC.

-Ben

Jim Thatcher wrote:
> We are getting nowhere. I will try once more.
> 
> I believe that if all the heading text on a page has the same class, 
> then the headings can be programmatically determined. But the fact 
> that they
are
> headings cannot be programmatically determined.
> 
> If folks disagree - fine. But if some agree, maybe 1.3.1 needs to be 
> revisited.
> 
> Jim
>  
> Accessibility Consulting: http://jimthatcher.com/
> 512-306-0931
> 
> 
>

Received on Friday, 2 December 2005 22:17:27 UTC