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

RE: Navigational features

From: Loretta Guarino Reid <lguarino@adobe.com>
Date: Fri, 2 Dec 2005 12:41:43 -0800
Message-ID: <0DAF2B31FBCEB6439F63FA7F91601F74512F0F@namail3.corp.adobe.com>
To: "Ben Caldwell" <caldwell@trace.wisc.edu>, <w3c-wai-gl@w3.org>

Should we add Jim's example to the common failures for this success
criterion?

Loretta Guarino Reid
lguarino@adobe.com
Adobe Systems, Acrobat Engineering 
> -----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 12: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 20:41:21 GMT

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