canvas 2d context
Encrypted Media Extensions
HTML 5 spec
HTML 5: The Markup Language
HTML WG website
HTML5 differences from HTML4
HTML5 Spec - PR Blockers
Media Source Extensions
pre-LC1 alt techniques
pre-LC1 authoring guide
pre-LC1 HTML 5 spec
Erika Doyle Navara
Philippe Le Hégaret
Joshue O Connor
Integration of the aria specification in html requires detailed processing requirements for the states and properties it defines when used in html. It also requires consideration of how aria features interact with html-native features and, where functionality is duplicated, consideration of whether the advantages of having more than one way to achieve the same effect outweighs the cost.
Overlap between longdesc and aria-describedby:
Add notes (no markup allowed, URIs get automatically hyperlinked):
this "issue" represents a fundamental mis-understanding of the point of ARIA markup and the PFWG's attempts to work with the HTML WG -- as stated by Al Gilman in a post to public-html
The working group likes the idea of having built in semantics in HTML and in particular would prefer to have common document elements, such as widgets built
in to the markup. This reduces download size and the effort required to make a web page accessible. For these reasons, we would promote the use of such
markup over the ARIA approach. That said, we do believe that HTML 5 will not incorporate document elements for all those included in the ARIA role taxonomy
nor will it include all the states and properties. For these reasons, backward compatability for the ARIA specifications is a must.
further on in his email, Al Gilman also states:
To summarize, our goals for HTML 5 are as follow:
* Support for issues highlighted in Table: 1 of the ARIA Roadmap
* Backward compatability to ARIA, including the role attribute.
* Allow for full interoperability with assistive technologies
* A preference for access to accessibility information via the DOM
* Reduced efforts by authors to support assistive technologies
* Support for the access element or a version of it.
* Maintain equivalent or improved accessibility features of HTML 4.01
i vote that this is a NON-ISSUE
using RAISED to represent lower priority as discussed in http://lists.w3.org/Archives/Public/public-html-wg-issue-tracking/2008Aug/0005.html
closing issue-68 as a dup of this one, opening this one instead, after discussion with Sam, who chaired the 2009-02-05 HTML WG conference call
'Call for Review: WAI-ARIA Last Call and New Document for Browsers' - http://lists.w3.org/Archives/Public/w3c-wai-ig/2009JanMar/0037.html
Steven's first pass at a matrix:
Per the CfC, this issue is closed without prejudice. Individual changes to ARIA processing requirements can still be raised separately.
ACTION 138 was unbound from HTML ISSUE 35 in January 2010 when this issue was closed.
At the March 25 HTML teleconference , the HTML Chairs opened Action 177  to have a bug raised to track Action 138 , as Maciej had unbound   Action 138 from HTML ISSUE 35  when this ISSUE 35 was closed.
The tracking bug is Bug 9326: "HTML elements mapping to ARIA and A11y APIs" reported by Cynthia Shelly.