W3C logoWeb Accessibility Initiative (WAI)         logo

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

Analysis/Requirements and Changelog for "Developing a Web Accessibility Business Case for Your Organization" - 2009 Revisions

Page Contents

The document Developing a Web Accessibility Business Case for Your Organization is at www.w3.org/WAI/bcase/Overview


Changes September 2012

Changes on 23 September 2010

Changes from Version 1.1 to Version 2, June 2009

Changes from Version 1.0 to Version 1.1, January 2008

[Old Analysis/Requirements and Changelog]

Considerations for next revision

2009 Q3 Appendix and mobile update

Appendix parameters and process

Here is a proposal for an appendix listing supporting material for a web accessibility business case, such as case studies showing costs and benefits of improving accessibility, articles on the overlap between accessibility and SEO, blog posts or e-mails demonstrating support for accessible sites ("viral marketing").

Criteria for listing:



  1. Submissions for listing are sent to team-accessibility-business-case@w3.org with subject: [fill in name of listing] (not a publicly archived list).
  2. At least 2 designated EOWG reviewers read each listing for potential problems, and send internal comments and suggested public annotations to team-accessibility-business-case@@w3.org.
  3. Listings will be updated periodically, depending on editor availability. Expectation is at least once a month, yet may be more frequent.


Purpose, Goals, Objectives (2008-2009 revision)

Borrowing from “Approach” on the old Change Log page:

  1. Revise existing Business Case to:
    • include more references to older people where appropriate
    • reference WCAG 2.0 rather than WCAG 1.0
  2. Introduce reasons for building accessible Web sites that will resonate with technical and non-technical people in a broad range of organizations, including the private and public sector and large and small organizations
  3. Provide encouragement in technical and non-technical terms, as appropriate, for developing accessible Web sites
  4. Expand the audience for Web accessibility by showing that what you do for Web accessibility benefits others, including older users, users without disabilities, the organization owner of the Web site, the developers, etc
  5. Provide a ‘buffet of ideas’ that can be sampled according to what factors may be important for a particular organization

Audience (2008-2009 revision)

No obvious changes, however emphasize that the indirect audience may not understand the technical aspects of the Web:

Approach (2008-2009 revision)

Initial update ideas for consideration (September 2008)

  1. Overview section - http://www.w3.org/WAI/bcase/Overview.html
    • Ensure the Introduction clarifies "that the paramount goal is including people with disabilities due to equal rights".
    • Possibly mention the "UN Convention on People with Disabilities"
    • Examples (consider:- financial institution, entertainment portal (football?), org/company with older workers, local government with older ratepayers)
  2. Social section - http://www.w3.org/WAI/bcase/soc.html
    • Add in social networking and interaction (email, forums, blogs, photo sites, etc)
    • Add older users into 'barriers' & 'digital divide' & 'new/infrequent'
    • Add more older people examples into 'older people'
    • Section "Access for Older Users" needs complete revision
  3. Technical section - http://www.w3.org/WAI/bcase/tech.html
    • Add old configurations (PCs/modems/browsers/plug-ins) under 'different configurations'
  4. Financial section - http://www.w3.org/WAI/bcase/fin.html
    • Under 'identifying factors', add CMS conformance with ATAG
    • Somewhere (maybe financial benefits?) add something (with good ref) about demographic changes, "baby-boomers" retiring, etc
      Note: EOWG previously purposely did not list disability statistics - see paragraph starting with "It is difficult to estimate how many people are affected by Web accessibility,..." in <http://www.w3.org/WAI/bcase/soc.html>  - therefore, it might be awkward to list ageing statistics
    • Within 'increased audience' add demographic changes and older users
      (although probably not with stats - maybe link to that section in the Lit Review)
  5. Legal/Policy section - http://www.w3.org/WAI/bcase/pol.html
    • Add 'age discrimination' legislation
      (e.g. Australia has general legislation; UK has employment legislation; must be others across Europe and elsewhere)
    • Under 'Different Types of Organizations / government' add local government ratepayers and service delivery
    • Under 'Different Types of Organizations / education' add older workers and life-long-learning
      [or under Social?]
    • Under 'Different Types of Organizations / industry' add older worker retention
      [or under Financial?]
    • Under 'consideration for future' add new markets (and retain markets) where accessibility would be beneficial (e.g. ageing population)
      [or under Financial?]

References (2008-2009 revision)

June 2009 Editor's Drafts:

WAI-AGE Task Force and EOWG discussions:

Related documents:


Changelog (2008-2009 revision)

Consider for next edit / Wishlist:

To do:

2009-06-08 version

2009-06-04 version

2009-06-01 version

2009-05-29 version

2009-05-26 version

2009-05-21 version

2009-05-19 version

2009-05-04 version

2009-04-30 version

2009-04-29 version

2009-03-23 version

2009-01-19 version

2008-11-27 version

Added [Previous Page | Top of Page | Next Page] links, as appropriate, at the bottom of all pages (action 2, TF 12 November 2008).

2008-11-11 version

Additional word-smithing for consistency and tone (Shawn & Andrew). Minor content changes include:

2008-11-06 version

The following changes were discussed and recommended at during the EOWG teleconference of 17 Nov 2008

2008-10-16 version

2008-10-06 version