- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Nov 2010 17:01:37 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11199 --- Comment #9 from Tab Atkins Jr. <jackalmage@gmail.com> 2010-11-03 17:01:36 UTC --- (In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > (In reply to comment #5) > > > > ...like I said, your user agent can choose to separate out some types of > > > > headings for you automatically, if they occur in a <nav> or similar rather than > > > > just part of the normal document structure. > > > > > > I understand but that's just guessing from the user agent. My understanding was > > > that HTML is to try to remove the guessing part from user agent by having a > > > clear and semantic format. > > > > I didn't say anything about guessing. The fact that a heading is in a <nav> > > indicates that it's a heading for the navigation, not a heading for the main > > content. Thus, a user agent wanting to present a list of all navigation > > headings can, without any guessing involved, grab all the headings in the > > <nav>. > > > > Similarly, a user agent could grab headings or links in <footer> separately. > > What id the headings in nav and footer are in the same structure...then the > user agent would break the structure because it doesn't know what is really > going on. I don't understand what such a structure would look like. Could you give an example? > In the web today, there is usually there type of content displayed on a > page...Site level content, page related content and content itself and as per > HTML 5, it's all mixed together. Agreed that *currently* the structure is often mixed together. This is why HTML5 introduced several new structural elements, so you can more explicitly indicate the structure of your page. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Wednesday, 3 November 2010 17:01:38 UTC