- From: Léonie Watson <lwatson@paciellogroup.com>
- Date: Tue, 1 Dec 2015 12:00:42 -0000
- To: "'Martin Janecke'" <w3.org@prlbr.com>, "'Steve Faulkner'" <faulkner.steve@gmail.com>, "'Cynthia Shelly'" <cyns@microsoft.com>
- Cc: <info@3zero.co.uk>, <public-html@w3.org>
> From: Martin Janecke [mailto:w3.org@prlbr.com] > Sent: 01 December 2015 10:26 > On 01.12.15 09:22, Léonie Watson wrote: > >> From: Martin Janecke [mailto:w3.org@prlbr.com] > >> Sent: 30 November 2015 22:06 > >> Isn't it strange to have these two but no page-specific headers? > > > > When <header> is scoped to <body> it represents the header for the > document. From the HTML5.1 spec [1]: > > > > "When the nearest ancestor sectioning content or sectioning root element > is the body element, then it applies to the whole page." > > > But the accessibility mapping to the banner role implies something else [1]: > > "banner (role): A region that contains mostly site-oriented content, rather > than page-specific content." The HTML spec says that when scoped to <body>, the <header> is the header for the page. The ARIA spec says that the element with the banner role should contain sitewide information. In other words the page header should contain sitewide information - exactly the way we've been designing websites for the past 20 years. Léonie. -- Senior accessibility engineer @LeonieWatson @PacielloGroup
Received on Tuesday, 1 December 2015 12:01:05 UTC