13960 2011-08-29 20:34:19 +0000 I am concerned about the way the Article element is used in examples. Doesn't it make sense that Screen Readers will want to use the article element to skip over the HEADER and NAV elements to the main content. Instead of this: <article><heading>...</hea 2011-10-25 03:26:25 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#top a11y P3 normal --- 1 contributor ian greg.tarnoff ian jfoliot laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 56004 0 contributor 2011-08-29 20:34:19 +0000 Specification: http://www.w3.org/TR/html5/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: I am concerned about the way the Article element is used in examples. Doesn't it make sense that Screen Readers will want to use the article element to skip over the HEADER and NAV elements to the main content. Instead of this: <article><heading>...</heading><nav>...</nav><p>...</p><footer>...</footer></a rticle> Why not save the article element for pure content like this: <heading>...><nav>...</nav></heading><article><p>...</p></article><footer>...< /footer> I know WAI-ARIA can do landmarks to find main content... but should there not be a native way in HTML 5 to do this easily, why not article? Let's save <article> for the content of the article, not all the chrome, nav, headers and footers too. Also I agree with those who want to drop the HRgroup element... it might be confusing for Screen readers to miss a lower heading because only the highest level of the HRgroup is exposed. <hrgroup> <h2>I don't only want to see this Heading</h2> <h3>But I want to see this heading too</h3> </hrgroup> Posted from: 70.26.12.108 User agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) 56767 1 greg.tarnoff 2011-09-14 11:56:29 +0000 This has always sat a little off with me too. However my understanding of the ARTICLE is that it is a chunk of content that can survive on its own without the remainder of the page, such as in a RSS feed. In this scenario, the HEADER & FOOTER are there to provide containers for things like author, publish date and meta content. How would we provide this information semantically without being able to include these elements? 58466 2 ian 2011-10-19 23:09:29 +0000 I don't understand. What's wrong with having accessibility tools intelligently skip past <nav> elements? 58844 3 ian 2011-10-25 03:26:25 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: see comment 2