- From: <bugzilla@jessica.w3.org>
- Date: Wed, 28 Nov 2012 11:37:10 +0000
- To: public-html@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20118 Bug ID: 20118 Summary: Several clarifications / suggestions for improvement Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: maincontent element Assignee: faulkner.steve@gmail.com Reporter: silviapfeiffer1@gmail.com QA Contact: public-html-bugzilla@w3.org CC: public-html@w3.org Here are a few suggestions for how to clarify the specification of <main>: * Introduce a "Note" that essentially says: The <main> element can be thought of as the element that encapsulates the area on the page that you would point out to a blind user as containing the core information of the page. * Explain the second note better: "Authors are advised to use ARIA role=main attribute on the main element until user agents implement the required role mapping." Add something like: "The <main> element provides a landmark for accessibility technology [link to ARIA landmarks], which eg. allows a blind user to gain directly access to this part of the Web page. * The examples could be much clearer if they didn't (just) include <header>, <nav> and <footer> elements, but others, in particular after <header> and before <main>. For example an iframe with an ad. * I think that the <nav> in the example should not be part of the <main> section, because it's a landmark that can already be directly accessed. However, I think it might make sense to include two examples that differ on this point to explain that both are valid and both are useful for a11y users because in both cases they get the a11y user closer to "where the action is". * I think the "Guidance for User Agents and HTML specification editors" section needs to include something about which element should be chosen as the "main" landmark if there are both a <main> element and a role=main and they are different. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 28 November 2012 11:37:11 UTC