W3C home > Mailing lists > Public > public-html@w3.org > August 2009

Re: Proposal: <content> element

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Fri, 28 Aug 2009 12:27:08 +0200
Message-ID: <4A97B0FC.2050407@lachy.id.au>
To: Steven Faulkner <faulkner.steve@gmail.com>
Cc: HTML WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
Steven Faulkner wrote:
> hi lachlan,
> It would be useful if these were  defined in the HTML5 spec no?

Yes, presumably in the section defining ARIA role mappings.  See below.

> my thinking would be that untill such times that the various elements and
> associaated algorithms are implemented in user agents, use of landmarks to
> mark up unsupported semantics be allowed.

Yes, of course they would be allowed.  I never suggested otherwise.

> Lachlan Hunt wrote:
>> Steven Faulkner wrote:
>>> 2. there is no comparable element to role="banner" as <header> is
>>> allowed to be used multiple times within a document and it
>>> states in the ARIA spec that 'Within any document or application,
>>> the author *SHOULD* mark no more than one element with the banner
>>> role.'
>> This could be defined to map to the first header element in the page who's
>> nearest sectioning element ancestor is the body element.

The current spec already maps <header> to the banner role, but the 
definition needs to be refined as described.

>>> 3. while currently role="contentinfo" does not have an authoring
>>> restriction like role="banner", i believe this is an oversight, 
>>> and it should have. If so there will be the same issue with
>>> mapping it to <footer>, which can also be present multiple times
>>> in a html5 document.
>> If that restriction were to be applied to role="contentinfo", then it could
>> similarly be defined to map to the first (or maybe last) footer element in
>> the page who's nearest sectioning element ancestor is the body element.

The spec also maps <footer> and <address> to the contentinfo role, but I 
don't think the spec needs to change anything here, at least until ARIA 
does restrict contentinfo to just one element, if they do as Steve 

Lachlan Hunt - Opera Software
Received on Friday, 28 August 2009 10:27:44 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:50 UTC