In a recent blog post, Steve Faulkner of the Paciello Group began to examine how HTML5, which is supposed to help improve the accessibility of web sites and applications, is being exposed to assistive technologies. The current state of things, as documented on HTML5Accessibility.com, leaves a considerable amount to be desired.

The current accessibility support implemented in browsers lags behind their implementations of the sexy new features themselves. These are still early days in the implementation of HTML5 features, so lets keep our fingers crossed that Google, Apple (Safari on Windows) and Opera will get their acts together to provide at least a basic level of HTML support in their browsers for assistive technology users. Equally it is hoped Mozilla, Apple (Safari on Mac) and Microsoft will strive to have their rate of accessibility support match their rapid implementation of the new HTML5 features.

To address the need for standardizing the implementation of accessibility features, Steve and others have begun working on the HTML to Platform Accessibility APIs Implementation Guide.

We can’t thank Steve enough for his work on this and wish him well as these efforts continue.

[...] This post was mentioned on Twitter by Matt May, Kimberly Blessing, sin3rss, Peter Winnberg, WebStandardsProject and others. WebStandardsProject said: HTML5? Check. Accessible HTML5? Um… http://bit.ly/f526NO [...]

It’s disappointing that people are keen to work on bling, but not the full substance to back it up. Without accessibility the job’s only half done – here’s hoping the browsers follow through. I have faith that some of them will, at least.

(Also, typo: should be http://html5accessibility.com/)

HTML5Accessiblity.com don’t work, but that initiative of accessible check is really good, In the last years accessible is a big importance under web.

“supposed”?

Don’t you mean “designed”?

Thanks for the tip, I hadn’t heard of this yet. You have a typo in the URL of html5accessibility.com.

That should be http://html5accessibility.com/, no?

Fixed the link (apologies).

Accessibility is an absolute must. I attended a talk by an IBM engineer who is blind recently. But I do not see HTML 5 doing enough.

Looking forward to learning more on this subject and agree that the browsers must provide a framework and show a willingness to implement accessibility features.

In Internet speed, it is no longer early days for HTML 5. Has there been any perceptible update on the accessibility issue?

Hopefully mobile browsers will catch up with the features fast…

I agree with Accessibility, we are currently reworking our webproject in order to make it useable for disabled people. For this we are getting deeper into HTML5. So far the improvements from the earlier versions are quite good and will help our users to use the site better.

Great work thanks for the link and thanks Steve.

My earlier comment (#9) is being held in moderation since Feb 20th? Has moderation seized, though accepting comments has not?

The table on the link showing tables and supported browsers is certainly disappointing. Surely, browser companies need to take notice of such developments and get the technology integrated.

I’d further suggest that many countries have now introduced legislation at statute concerning accessibility of websites. This is not something people can ignore any more.

Hi Steve. Thanks a lot! Ok, these are still early days in the implementation of HTML5 features but your Implementation Guide helps to live with that fact.

Just today i changed to the new Firefox version. Cant wait to see more html5 improvements in the browser sector. What browser has the best html5 implementation so far?