PUBLIC MARKS from Monique with tags html5 & accessibilité

Make no mistake: Sectioning elements help you improve document structure, and they’re in the spec’ to stay. Once and for all, I will be exploring the problems these elements solve, the opportunities they offer and their important but misunderstood contribution to the semantic Web.

Vibéo est né suite à un problème récurrent que nous avions qui était le besoin d'un lecteur vidéo accessible HTML5 qui respectait les standards du SGQRI 008-01.

Part polemic, part instruction manual, The Truth About HTML5 has ignited an interesting debate. Here we present an exclusive excerpt on the problems around structuring in HTML5

Compatibility tables for support of HTML5, CSS3, SVG and more in desktop and mobile browsers.

IBM Research-Tokyo recently partnered with NCAM to research ways to deliver online audio descriptions via text-to-speech (TTS) methods, rather than using human recordings. IBM and NCAM explored two approaches which exploit new HTML5 media elements as well as Javascript and TTML

This document contains author conformance requirements for use of the alt attribute in HTML5 and best practice guidance for authors of HTML documents on providing text alternatives for images.

This specification is an extension to the HTML5 specification [HTML5]. All normative content in the HTML5 specification, unless specifically overridden by this specification, is intended to be the basis for this specification.

Recently, Everett Zufelt posted an excellent blog post titled: Are You Confused by HTML5 and WAI-ARIA Yet?. In his post, Everett outlines a number of areas in which the evolving HTML5 specification and the WAI-ARIA specification conflict with one another in ways which can cause confusion among web developers.

In the meantime my advice is to use HTML5 sectioning content elements when they are appropriate, but continue to use h1 - h6 for headings. That way you can safely use the new elements.