HTML5: bolt-on or built-in accessibility?

Parallel with the discussion in the comments to my post HTML5 details element, built-in and bolt-on accessibility, some cleverer minds than mine (Edward O’Connor, John Foliot, Tab Atkins, Jonas Sicking) have been working on a proposal Retain several newly-introduced semantic elements, attributes, and controls to retain structures that some have proposed be scrapped, such as aside, details, figure, meter, progress and the hidden attribute.

It’s a short but must-read if you’re interested in the debates between bolt-on and built-in accessibility in HTML5.

I had no hand in its authoring, but fully support the proposal and arguments. (I tried to add my name to the end of the proposal to demonstrate immoral support, but am so crap I couldn’t even remember my W3C password.)

See also this interesting and impassioned email from John Foliot.

3 Responses to “ HTML5: bolt-on or built-in accessibility? ”

Comment by Matt Wilcox

Sadly the URL gives this error:

Fatal error: Class ‘AuthPlugin’ not found in /u/wikis/mediawiki/extensions/LdapAuthentication/LdapAuthentication.php on line 65

Comment by Jeremy Keith

I offered to help draft this and then didn’t follow through (story of my life). Ted and the others have done an excellent job with the zero-edit change proposal.

Comment by David Rodriguez

That is a very informative proposal and I think easier to read than what’s in the current w3 draft. Hopefully they can add this ‘real world’ language to the spec, which would in turn make it much easier to learn and teach these new elements. I now see how useful these new elements will (hopefully) be.