[Bug 13960] New: 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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13960

           Summary: 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
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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)

-- 
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 Monday, 29 August 2011 20:34:22 UTC