This is an old draft. The published version of this document is at

W3C logoWeb Accessibility Initiative (WAI)         logo

WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities

Technical Factors in Developing a Web Accessibility Business Case for Your Organization
[Change-marked version of 23 June 2009 incorporating WCAG 2.0 and Older Users]

This is an old draft. The published version of this document is at

Editors Draft: 8 June 2009 [changelog]
Status: This document is a draft and should not be referenced or quoted under any circumstances. Please send comments to (a publicly archived list). The current published version of this document is at

Track changes are indicated as follow:

  1. Additions below are shown with blue highlighting within square brackets "[addition]"
  2. Deletions are shown with orange highlighting and strike-through within braces or curly brackets "{deletion}".
  3. "Web site" changed to the more commonly used "website" unless it is part of the title of another document

end of note

end of note

Page Contents


This page is part of a resource suite that describes the social, technical, financial, and legal and policy factors relevant to developing a customized business case for Web accessibility for a specific organization.

Implementing Web accessibility solutions often results in improved technical performance. The [relative] importance of various technical benefits of Web accessibility is different for specific organizations and situations. For example, reducing server load might be most important to an organization with a large, mission-critical, high-traffic site; whereas another organization that focuses on cutting-edge technology might be more interested in interoperability and being prepared for advanced Web technologies. {Yet} [However,] these same technical benefits might not be very important for organizations with small, simple sites; [they might be more interested in simplifying site maintenance].

This page provides guidance on addressing technical factors in a business case for Web accessibility.

Identifying Technical Factors for a Specific Organization

The following questions {can} help identify how the technical aspects of Web accessibility apply to the organization:

See Web Content Accessibility Guidelines (WCAG) Overview for more information about the WCAG {1.0 Checkpoint} references below.

Reduce Site Development and Maintenance Time

Incorporating accessibility usually increases site development time initially, as discussed in Financial Factors. However, in the long term Web accessibility can reduce the time an organization spends on site development and maintenance, as follows:

Reduce Bandwidth Use and Server Load

Web accessibility techniques can reduce the server load, [which increases the download speed and can reduce the need for additional bandwidth or servers,] {thus reducing the need for additional servers and increasing the download speed,} as follows:

Enable Content on Different Configurations

Many organizations are increasingly interested in Web interoperability and {device-independence} [device-independence, such as making their websites work well on mobile phones]. Web accessibility can enable Web content to be rendered and interacted with on different configurations[,] {--} including different devices, operating systems, and {user agents (such as} Web browsers{) --}[,] as follows:

Be Prepared for Advanced Web Technologies

Web accessibility can help organizations take advantage of advanced Web technologies and be prepared for future Web technologies, for example:

Have High Quality Websites

Some developers and organizations pride themselves on producing high quality websites that meet technical standards. {Web accessibility guidelines such as the Web Content Accessibility Guidelines (WCAG) 1.0 The} [Web Content Accessibility Guidelines (WCAG) and other accessibility specifications ] from the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) are widely-recognized international standards. {Several} [Additional] resources addressing the business case for Web standards in general are available on the Web {and in print}.

[ Previous Page - Social Factors | Top of Page | Next Page - Financial Factors- ]