Hi all,
I am making a request to the Working Group to publish the main element HTML
extension specification as a FPWD.
https://dvcs.w3.org/hg/html-extensions/raw-file/tip/maincontent/index.html
Recent changes:
* After consideration of feedback I have changed the name of the element
from <maincontent> to <main>. The reasoning for the change:
Feedback indicates preference for a shorter one word element name.
Most commenter's proffered <main> as a name.
The element name <content> is already proposed for use in the shadow DOM
specification [1]
As the element maps onto the ARIA role=main it seems an appropriate name to
use.
* Use agent guidance on the provision of a method to navigate the main
element has been clarified
* UA stylesheet advice has been added
* advice to HTML spec editors on removal of existing advice in the spec in
relation to the main content section.
* modified code examples to illustrate the use of the main element in
conjunction with a nav element containing in-page navigation links.
* added links to the rationale /use case document [2] and to new data
supporting the concept of a main element [3]
[1]
http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#content-element
[2] http://www.w3.org/html/wg/wiki/User:Sfaulkne/main-usecases#Introduction
[3] http://lists.w3.org/Archives/Public/public-html/2012Oct/0109.html
--
with regards
Steve Faulkner
Technical Director - TPG
www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html