It's been seven years since the W3C released the first version of the web content accessibility guidelines (WCAG 1.0). Since then, accessibility has slowly but surely turned up on the radar of web managers in most large organisations.
The benefits of accessibility are pretty well known too - a quick Google search for web accessibility benefits returns over 37 million results! Because of this, more and more large profile websites have offered better and better accessibility as the years have gone by. There's still a long way to go but the progress over the past few years is highly visible and indeed positive.
Web 2.0 refers to the ‘next generation’ of websites and online applications. Websites using Web 2.0 technologies have started to spring up all over the Internet, and are likely to exponentially increase in number over the next few years. Although the term itself, Web 2.0, has become a bit of a buzzword, there's no doubt that Web 2.0 is here and is becoming more and more commonplace.
Two characteristics of Web 2.0 include AJAX and user generated content. Many websites are beginning to embrace these two concepts, causing never-before seen accessibility issues...
The Amazon diamond search, for example, showcases a great example of using AJAX to create an interactive and highly useful interface. It basically uses click-and-drag sliders to allow users to broaden and narrow a wide range of filtering criteria. The page then automatically updates to show how many results conform to the users' selected criteria.
The Amazon application offers fantastic usability for many web users. But it's totally impossible for screen reader and keyboard-only users to use, and very difficult for any screen magnifier user to use. The solution? A separate simplified accessible version, which Amazon have actually provided (ironically, this separate version hasn't been built to high levels of accessibility, although it could easily have been).
Another concept of Web 2.0 is content generated by users. Blogs and wikis are becoming more and more commonplace, as stand-alone websites or within an organisation's website. Currently, many large organisations struggle to control the accessibility of their content due to the large number of content editors - how are they going to cope with users contributing content as well as employees of the organisation?
Websites such as Blogger, Flickr and YouTube are totally reliant on user generated content, in the form of blogs, photos and videos respectively. How can these websites control the accessibility of their content? Content is created at such a rapid speed that it wouldn't be reasonable (or even possible) for any of these websites to police that content for accessibility.
Image- and photo-driven websites, such as Flickr, could request users insert alternative descriptions, either of their own or other people's photos. Ensuring this actually happens across the site though will be difficult to impossible to achieve.
Other websites, including those of large organisations, are attempting to build up communities by allowing users to upload images, post comments and generally interact with each other and the site. Will the website owners provide a mechanism to ensure this content is produced accessibly? Can they?
The second version of the web content accessibility guidelines (WCAG) from the W3C is currently in final working draft and is soon to be released officially.
One of the main differences between version 2.0 and 1.0 of the guidelines is that WCAG 2.0 is technology-neutral. This means that the guidelines themselves are far more vague and open to interpretation than previously.
There are three major factors that will shape web accessibility in the future: AJAX, user generated content and WCAG 2.0. The increased prominence of these factors could lead to some of the following: