Most of us are excited about HTML5 and all the benefits it will bring. Overly excited maybe is a more accurate term, which includes myself. We as a community need a “sanity check” about the readiness of HTML5 and its accessibility because:
- The spec isn’t complete (2012 for Candidate Recommendation) thus requirements may still change.
- The browsers are in the middle of implementation and much accessibility support isn’t provided yet.
- There are many accessibility issues remaining such as Canvas in general; no semantic information to assistive technology for many elements; keyboard access lacking in audio & video controls in most conditions.
The web site HTML5Accessibility.com is a great place to learn about these issues for each major web browser. Along with that is a presentation by Steve Faulkner (@stevefaulkner) of the Paciello Group: HTML5 Accessibility – Is It Ready Yet? presentation by Steve Faulkner and and Hans Hillen (SlideShare).
- HTML5 Cross browser Polyfills – Shims, fallbacks, and polyfills in order to implant html5 functionality in browsers that don’t natively support them.
- The most pressing Accessibility issue in HTML5 today? by John Foliot (@johnfoliot).
- Creating Your Own Accessible HTML5 Media Player by Terry Thompson (@terrillthompson)
- HTML5, ARIA Roles, and Screen Readers by Accessible Culture