- From: Loretta Guarino Reid <lguarino@adobe.com>
- Date: Thu, 9 Feb 2006 17:51:37 -0800
- To: "Yvette Hoitink" <y.p.hoitink@heritas.nl>, <public-wcag-teamb@w3.org>
If I understand you correctly, you are defining a hierarchy, just one in which we are looser with our definition of "next level". I actually think this will be more confusing for people than just requiring hierarchy. The sense that I got from the working group today is that they don't want to introduce hierarchical requirements for HTML under GL 1.3. We might be able to bring them in under 2.4.6, although I think even there we were getting some pushback. Loretta Guarino Reid lguarino@adobe.com Adobe Systems, Acrobat Engineering > -----Original Message----- > From: public-wcag-teamb-request@w3.org [mailto:public- > wcag-teamb-request@w3.org] On Behalf Of Yvette Hoitink > Sent: Thursday, February 09, 2006 1:31 PM > To: public-wcag-teamb@w3.org > Subject: Headings test > > > Hi group, > > I will not try to write this in an understandable manner > yet but focus on > mathimatical exactness (I've defined the heading level of > H1 as lower than > the heading level of H2): > > For each header H, determine the heading number (X). For > each heading level > lower than X, determine the last occurrence (L) of that > heading that > preceedes X. H should be a logical child of L. > > This algorithm should allow the following case: > H1 - H2 - H4 - H2 as long as both the H2s are childs of > the H1 and the H4 is > a child of H2 and H1. > > It does not allow H1 - H2 - H2 - H4 where H4 is the > heading for a set of > related links that are about the whole page (h1) and not > the second > subsection (h2). > > Yvette Hoitink > Heritas, Alphen aan den Rijn, the Netherlands > E-mail: y.p.hoitink@heritas.nl > WWW: http://www.heritas.nl >
Received on Friday, 10 February 2006 01:51:56 UTC