- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Nov 2010 14:16:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11199 --- Comment #4 from Laurent Goderre <laurent.goderre@gmail.com> 2010-11-03 14:16:01 UTC --- (In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > HTML5 defines an algorithm to extract an outline from a document based on > > > sectioning elements and headings. > > > > So we have to rely on WAI-ARIA to define the structure (which stream is the > > main document etc..)? > > There shouldn't be any need for additional structure or "streams". > > The outline retains information about <nav>, etc. Your user agent can choose > to present just the <nav> headings, separate from the main document headings, > all by itself. That would be semantically incorrect. On a web page not everything is related to the content and it's important to make a distinction. For example, a breadcrumb heading (hidden in graphic user agent but available for screen reader to jump to it) does not belong in the content structure. For example: h2 Breadcrumbs h1 History of writing h2 Prehistoric writings h2 Antiquity h3 Witing in Ancient Egypt h3 Writing in Ancient Greece h3 Writing in the Roman Empire h2 Medieval h2 Footer Breadcrumb and Footer, are very useful heading allowing screen reader users to more easily access part of the page but they don't belong with the same heading structure. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 3 November 2010 14:16:04 UTC