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
escalated from http://www.w3.org/Bugs/Public/show_bug.cgi?id=8000
Currently the a element is defined in the HTML5 specification as an element that cannot have its native role overridden by ARIA roles 
The reasons for creating ARIA centered around the inability of the HTML specification to address how author would create content. In fact, with the exception of forms, it was assumed that HTML would only be used for documents. Clearly, that was a miscalculation.
It is essential that authors be given the tools to produce accessible applications. The perception, by some, is that ARIA is meant to circumvent the semantics of the host language, but rather it is the author that is circumventing the host language to create UI controls that satisfy their needs. WAI-ARIA simply provides the semantics to make them interoperable with assistive technologies.
Add notes (no markup allowed, URIs get automatically hyperlinked):
ARIA roles added to the a element should be conforming in HTML5
[paulc_]: When the TF has updated bug 10066 the Chairs will ensure it gets expedited processing.