I've written before about the need for all entities with a Web presence to make sure their Web site is accessible.  In this case, "accessible" means designing the Web site so that it is usable by all people, including those who fall into various classifications:

* People who use assistive technology, such as a screen reader or screen magnifier.
* People with low bandwidth connections or older computer configurations.
* People with disabilities or age-related impairments, such as dexterity limitations or hearing impairments

Still, 95% of all Web sites are inaccessible, according to the Austin organization Knowbility, which promotes barrier-free IT.

Since January, I have been working with Knowbility to promote Web accessibility through a program called AIR-Houston.  AIR stands for Accessibility Internet Rally, and it's a program to match professional Web developers with non-profit organizations that need help developing an accessible Web site.  (Learn more about Knowbility and its AIR programs around the country at http://www.knowbility.org)

As I talk to people about accessible Web sites, I see that everyone agrees they are necessary.  But many people ask me, "What makes a Web site accessible?"  This is one of those questions easier answered by rephrasing it as, "What makes a Web site inaccessible?"  Let's look at a few examples where the design of the site makes it difficult for some people to use.

Most Web sites today are sprinkled with graphics and pictures.  Sometimes those graphic elements are an essential part of the content of the Web site.  While they look nice, a visually impaired individual who is using a screen reader to peruse the Web site can't see these elements.  The screen reader translates text into synthesized speech.  When the screen reader encounters the graphic element, there may be nothing to "read" and the value of this graphic content is lost for that person.  An accessible design technique is to include alt-text that provides a brief but meaningful description of the graphic image.  (If you'd like to see what happens when you use a screen reader to scroll through a Web site, you can sample IBM's Home Page Reader for free at http://www-306.ibm.com/able/solution_offerings/hpr.html)

Tables are often used on Web sites today.  The World Wide Web Consortium, the agency that provides Web accessibility standards, recommends the use of a summary attribute on the table so that the screen reader user can get oriented to the layout and purpose of the table.  Without the summary, a user with a vision impairment may not understand the organization of the information in the table and get confused.

Whitepapers

• Selecting Effective Virtual Directories
• Best Practices for HP Servers and HP Enterprise Virtual Array in a Microsoft Exchange
• Compliance, Protection, Recovery: A Layered Approach to Laptop Security
• Endpoint Security: Data Protection for IT, Freedom for Laptop Users
• IT Departments on Data Security: A Research Concepts Survey
• Laptop Security Tool Helps Allina Hospitals Track 97% of IT Assets

View more SOFTWARE whitepapers

Webcasts

• Managing the End User Experience-A Real World Example of Success
• Lowering the Cost of Email Archives
• Google Webcast: Why archive email? Top challenges and best practices
• High Availability for SQL Server 2005 Using Array-Based Replication and Host-Based Mirroring Technologies
• Technical Overview of Exchange Server 2007 with HP Servers and Storage
• Bringing Order and Security to your Mobile Workforce: Corporate Mobility Policy and Device Management On-Demand

View more SOFTWARE webcasts

Special Reports

• Application Performance Management Executive Guide
• Executive Guide: Building a Service Oriented Architecture
• IT Buyers Guide To: Collaboration

View more SOFTWARE special reports