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

RE: Navigational features

From: Jim Thatcher <jim@jimthatcher.com>
Date: Fri, 2 Dec 2005 19:19:06 -0600
To: "'Gregg Vanderheiden'" <gv@trace.wisc.edu>, <w3c-wai-gl@w3.org>
Message-ID: <001801c5f7a7$921a6690$6501a8c0@jtcom2400>


Gregg said ...
> They cannot be programmatically determined as being headers. (due to
> definition of programmatically determined.)

I said I caved. Apparently I was not truthful. My whole point is that the SC
does NOT require them to be programmatically determined AS HEADERS. That is
not required. That is the problem. THAT is the weakness of the SC. It only
requires that the structures be programmatically determined. Not that they
expose their structural nature.

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 Gregg Vanderheiden
Sent: Friday, December 02, 2005 3:20 PM
To: jim@jimthatcher.com; w3c-wai-gl@w3.org
Subject: RE: Navigational features



That address the problem?  

I think that the way to make it concretely clear is to list it as a
"failure" in the "HOW TO MEET" for the success criterion.

I think we will do that and that should tie up the loose end.

Make sense to you Jim?
 
Gregg

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


-----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 1:59 PM
To: 'Gregg Vanderheiden'; w3c-wai-gl@w3.org
Subject: RE: Navigational features


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 Saturday, 3 December 2005 01:19:25 GMT

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