HTML5 and Accessibility

Over the past few weeks, I have been asked the same question several times, albeit in a few different guises, but what it boils down to is this:

Is HTML5 accessible?

Apart from the fact that no specification as such, can be deemed accessible or not, what has become evident is that there seems to be a rapid proliferation within the web design and development community of the misnomer that if you build a website using HTML5, it somehow becomes uber-auto-accessible. Although this would be a fabulous feat and the specification is certainly providing a fantastic foundation for accessibility through the inclusion of native functionality that has previously been the domain of 3rd party technologies or has simply not been achievable without considerable tweaking, we need to stop this situation from getting out of hand before it in any way tarnishes the existing and future fabulousity of HTML5.

As with all emerging technologies under development, encouraging early adoption and garnering community support are essential to its success, but of equal importance is a responsibility for these early adopters to understand both the possibilities and the limitations of the technology and to work in a spirit of open learning, knowledge sharing and understanding.

W3C Specifications are inherently accommodating and flexible in that they allow anyone to participate in their development, but no claims can be made about their fundamental performance. The quality of the code and its impact on a site’s accessibility are the responsibility of the developers and designers using these specifications appropriately, incorporating best practices, guidelines, like the WCAG, and ensuring appropriate user engagement and testing are undertaken. And as the use of other specifications and programming languages are required to build the complex dynamic websites that are now the norm, HTML5 is not standalone.

And so it follows that accessibility is not just about front-end code. It is also about good design and giving consideration to how a website’s users interact with the UI overall, as well as each discrete feature, and how the front-end interprets and handles the data that is output from the back-end. As all of these additional considerations are outside of the scope of HTML5, I am concerned that these are in danger of falling through the cracks if people think that HTML5 on its own provides a singular route to accessibility conformance.

But that’s not all. In addition to this, although all modern browsers currently provide a reasonable level of support for some of the important HTML5 features – such as the new semantic elements, HTML5 forms, Canvas, and other APIs – there are considerable workarounds required for certain features to work in IE8 and below, and for other browsers and devices that don’t support the use of certain technologies, such as JavaScript and Flash.

So, what does this all mean for jobbing designers and developers? Well, it is simply a case of “Whoa Nelly!”. Although HTML5 is pretty groovy in my books, it alone does not ensure accessibility, and we need to consider all of the factors that influence and contribute to it.

You didn’t really think it was going to be that easy now, did you?

August Event: Design for the Future

London Web Standards is pleased to announce our next event: Design for the Future with Andy Hume and Richard Rutter. The event will take place on the 16th of August.

Standards we’ve been reading about for years—HTML5, CSS3, WAI-ARIA—are finally making their way into all of the major browsers. At the same time, more and more people are accessing the Web using mobile and tablet devices.

This month at London Web Standards, Richard Rutter (@clagnut) and Andy Hume  (@andyhume) will discuss using emerging standards to create websites that are beautiful and engaging across a range of devices.

A Progressive Web, Andy Hume

The idea of progressive enhancement isn’t new, but the way we approach it needs to evolve. New devices such as those powered by iOS and Android are upon us, just as a throng of emerging technologies like HTML5 and CSS 3 are ready for action. With every day that goes by people are experiencing the web in new, different, undreamed of, impossible ways.  Exciting as this sounds on paper, how do we build websites within that impossibly complex and constantly shifting landscape?

The Future of Typography, Richard Rutter

At no other time has typography been taken so seriously by so many involved in the web, and that means there’s an awful lot of change and innovation to keep up with if you want to stay on the cutting edge of online type. This presentation will cover recent proposals and additions to CSS 3, from ligatures to hyphenation, synthesis to capitalisation, and much in between. It will cover the reasoning behind the new aspects of CSS 3, and reintroduce older properties which only now are becoming implemented and useful. The future of web typography is looking bright.