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 14:38:18 -0600
To: "'Ben Caldwell'" <caldwell@trace.wisc.edu>, <w3c-wai-gl@w3.org>
Message-ID: <000c01c5f780$57831490$6501a8c0@jtcom2400>

I cave. Thanks for thinking about it.

Accessibility Consulting: http://jimthatcher.com/

-----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.


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
> 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 20:38:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:57 UTC