- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Sat, 9 Mar 2013 10:55:07 +0000
- To: Jason Kiss <jason@accessibleculture.org>
- Cc: HTMLWG WG <public-html@w3.org>
Received on Saturday, 9 March 2013 10:56:18 UTC
Thanks Jason, I thought about similar wording, but didn't use it as it implies the navigational aids in the header are scoped to its nearest ancestor sectioning content or sectioning root element. Which I wanted to avoid as I don't consider it to be a necessary or useful restriction any thoughts? with regards SteveF <http://www.paciellogroup.com/resources/wat-ie-about.html> -- HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> <http://www.paciellogroup.com/resources/wat-ie-about.html> On 9 March 2013 10:44, Jason Kiss <jason@accessibleculture.org> wrote: > Hi Steve, > > These various clarifications you're providing are really useful. > > I'd suggest a slight change to the first paragraph as follows, just to > avoid the "a header represents a header" bit: > > "The header element represents a group of introductory or navigational > aids for its nearest ancestor sectioning content or sectioning root > element." > > Jason Kiss > > On 9/03/2013, at 23:14, Steve Faulkner <faulkner.steve@gmail.com> wrote: > > > The header element represents a header for its nearest ancestor > sectioning content or sectioning root element. A header typically contains > a group of introductory or navigational aids. >
Received on Saturday, 9 March 2013 10:56:18 UTC