View Full Version : What is accessibility?

09-17-2007, 05:08 PM
When designing a web site, many designers, developers and program managers always focus on the "usability" of the site. There are many factors to consider when addressing the usability of a site, but often they will boil down to the following features:

* Ease of use
* Navigation
* Common layout
* Familiar Layout methodologies

Sites which successfully implement these strategies often enjoy a higher "sticky-ness" on the site. That is, their average visit lengths are longer, as are the pages viewed per visit. We all know that the easier a site is to use, the more likely we are to use it. Additionally, if your site is geared towards some type of conversion by either a sale or contacting your organization, the longer you can keep a visitor at your site, the greater your chance of that conversion.

Usability vs. Accessibility

The fundamental difference between usability and accessibility is that usability measures the users ability to find and locate information, and accessibility measures the users ability to access the information. Sites can be very usable, with clean, easy to understand navigational and heirarchical structures, yet be very inaccessible.

Often organizations are so focused on usability testing that they forget to do accessibility testing. The consequences of this can be devastating, possibly shutting down access to upward of 20% or more of your user base.

A common issue with sites that are not accessible is a reliance on a particular browser configuration or plug-in. Often times this may be the use of a configuration to such an extent that the site does not function without that configuration. Examples of technologies that can lead to this are below:

* JavaScript and / or AJAX
* Flash
* ActiveX Scripting
* Java Applets
* Media Files

A good rule of thumb is: Anything that requires browser configuration or a browser plug-in has the potential to be an inaccessible technology.

Note: Just because a technology is not accessible does not mean you can't use it. All it means is that you should provide alternative methods to access similar content.

Understanding the difference between accessibility and usability will go a long way to helping your site's overall accessibility.

Until next time

08-06-2008, 10:12 AM
Web accessibility means that people with disabilities can use the Web.
Web accessibility also benefits people without disabilities. For example, a key principle of Web accessibility is designing Web sites and software that are flexible to meet different user needs, preferences, and situations.

10-14-2008, 08:55 PM
accessibility is the goal of ensuring that people can more easily access and use your web site as effectively as people who don’t have disabilities. That is, allow more people in different situations such as being Disabled or being wirelessly connected to the Internet to be able to functionally use your web site.

11-13-2008, 12:32 AM
I don't know if accessibility has ever been properly defined. I guess it is an impossible venture. For the most part, when we talk about accessibility, we tend to assume accessibility for people with disabilities. It is fair to an extent, because mostly these people suffer from the lack of accessibility. However, what accessibility really means, above usability, is that regardless of the circumstances, all people should be able to access something. A site, software, building, environment. But if we just want to talk about web technologies, in fact, if a visitor comes to your site who does not speak your language, it is an accessibility issue. Obviously, we cannot make web technology totally accessible to all. But within reason, we should aim to do so.