Chapter 9. Accessibility Testing

"The dream behind the web is a common information space in which we communicate by sharing information"

—— Tim Burners-Lee

So far we have spent a great deal of time discussing the types of testing used to ensure that the web applications you have created function correctly — such as providing the correct data in a timely manner. It's now time to focus on testing to ensure that the web applications you have created are accessible to a wide audience.

Accessibility is often confused with usability. Usability is how intuitive and easy the application is to use for all people, whereas accessibility means access to all. Accessibility issues make it more difficult for people with disabilities to use an application than for a nondisabled person. Although two different definitions have been provided, usability and accessibility often are complementary.

Some people cannot use their hands whereas others are unable to distinguish between colors. Some people cannot hear, some cannot see. Accessible web applications remove the barriers that make it difficult or impossible for those users who need extra support.

This chapter is presented differently than the others, as it explores accessibility patterns and practices in-depth and shows you how to create accessible sites (compared to the previous chapters that just provided an explanation of the tools to help find the problems). The reason this approach is taken is because the automated tools for accessibility ...

Get Testing ASP.NET Web Applications now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.