W3C home > Mailing lists > Public > public-html@w3.org > November 2007

Re: HTML 5 Authoring Guidelines Proposal the use of the section element and its potential impact on screen reader users

From: Henri Sivonen <hsivonen@iki.fi>
Date: Wed, 28 Nov 2007 15:02:28 +0200
Cc: public-html@w3.org
Message-Id: <B01122E6-F62A-411F-8960-9601317299BE@iki.fi>
To: Dr.Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>

On Nov 28, 2007, at 12:54, Dr. Olaf Hoffmann wrote:

> But if a reader has a method to 'style' audible a difference between  
> h1 and h2, it should be possible to count headings outside sections  
> and
> sections nested in each other with heading to derive the numbering  
> as specified in the working draft. Then it is the same problem as
> to style h1 and h2 differently in an aural stylesheet. If the  
> document only uses section structures and no h2...h6,
> I think, it is simple to create a default aural CSS stylesheet. But  
> if both systems are mixed, indeed, this gets more difficult,
> but as far as I can see (from an author point of view) not impossible.

It seems to me that the usefulness of the proposed outline depends  
largely on whether there will be a companion CSS selector for matching  
an element by its outline depth. A new selector like that should  
cascade reasonably with legacy styles written for h1-h6 or h1/section.  
I don't know if that's even possible. Moreover, it isn't clear whether  
it is performance-wise feasible for selectors to depend on the outline  
algorithm when there are dynamic DOM changes.

See also

> From this point of view of course it would be simpler for
> implementors to separate the two methods either using
> section+h or using h1-h6. Separation of different functionalities
> is mostly a good idea to avoid more difficulties as necessary.

What should happen when the UA gets a mix anyway?

Henri Sivonen
Received on Wednesday, 28 November 2007 13:02:53 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:24 UTC