Issue #2: ARIA vs. HTML 5
•ARIA
• Landmark Roles
• <div role=”navigation”>
•
• ARIA Properties and States
• <input name=”email” aria-required=”true”>
•HTML 5
• New structural elements
• <nav>
•
• HTML 5 form attributes
• <input name=”email” type=”email required”>
But...
Many ARIA roles that have no HTML5 equivalent, e.g. application, banner, main.
And…
Argument over structural elements in HTML 5 = major shit-storm.
Conflict between proposed HTML 5 spec & ARIA, specifically:

  HTML 5 structural elements vs ARIA landmark roles:
   <div role=”banner”> or <header> or <header role=”banner”>?

HTML 5 form attributes and states vs ARIA properties and states:
   <input name=”email” type=”email required”> or <input name=”email” aria-required=”true”>

From official WAI-ARIA spec: “If the host language incorporates WAI-ARIA support and there is a conflict between a host language feature and an WAI-ARIA feature, assistive technology SHOULD assign preference to the WAI-ARIA feature.”

BUT are number of ARIA roles that have no HTML5 equivalent, e.g. application, banner, main, search (see http://www.paciellogroup.com/blog/?p=106).

Structural elements in HTML 5 argument = shit-storm. Worth reading up on this if you’re interested in the development of HTML5 -  definitely check out zeldman.com; “HTML5 is a mess: now what?”.