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
Changelog
Changes September 2012
Changes on 23 September 2010
- Changed to Creative Commons license.
- (no content changes)
Changes from Version 1.1 to Version 2, June 2009
- Several edits throughout the pages to update for WCAG 2.0, and to more explicitly cover issues of older users. A diff-marked version shows the edits.
Changes from Version 1.0 to Version 1.1, January 2008
- Added paragraph at the end:
Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices introduces how Web sites can more efficiently be designed to be accessible from a mobile device and also accessible for people with disabilities when developers understand the significant overlap between the two design goals and guidelines.
[Old Analysis/Requirements and Changelog]
Considerations for next revision
- Number of People Affected (statistics) in Social page and Statistics on People with Disabilities and Web Use in Resources page - review and maybe revise quick fixes:
- in Social page, changed: "Web Accessibility for Older Users: A Literature Review has statistics on ageing demographics and age-related impairments." to: "The Statistics on People with Disabilities and Web Use section of the Resources page has additional statistics, including on on ageing demographics and age-related impairments."
- in Resources page, added: "See Number of People Affected (statistics) section in the Social Factors page for important information on statistics."
- Mobile overlap update - see Yeliz's suggestions from May 2009
- heck the wishlist below
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:
- Clearly relates to the business case for web accessibility, and provides the audience of our business case document with useful information.
- Does not conflict with WAI's position on accessibility, standards, etc.
Does not contain wording that some would find offensive. - Adequately reviewed and approved by at least 2 EOWG participants and/or WAI Staff.
Notes:
- Appendix will have a disclaimer. (top or bottom to be decided)
- Appendix will have "nofollow" (and a note saying so) to discourage submissions just for search rankings.
- Listings will include our annotations, e.g., pointing out info particularly relevant to points in our business case document.
- Open: Grouped by category? Listed chronologically? Table showing relevant points.
- Once the Appendix is set up and we have the review process running smoothly, we will actively solicit submissions of potential listings.
Process:
- Submissions for listing are sent to team-accessibility-business-case@w3.org with subject: [fill in name of listing] (not a publicly archived list).
- 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.
- If potential concerns are identified, EOWG Staff Contact or Chair manages addressing the concerns with EOWG participants and/or WAI Staff.
- If no potential problems identified by initial reviewers, EOWG Staff Contact sends submission to EOWG mailing list for 1 week review.
- If no concerns raised, listing is added with next update.
- If concerns, EOWG Staff Contact or Chair manages addressing the concerns with EOWG participants and/or WAI Staff.
- Listings will be updated periodically, depending on editor availability. Expectation is at least once a month, yet may be more frequent.
References:
Purpose, Goals, Objectives (2008-2009 revision)
Borrowing from “Approach” on the old Change Log page:
- Revise existing Business Case to:
- include more references to older people where appropriate
- reference WCAG 2.0 rather than WCAG 1.0
- 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
- Provide encouragement in technical and non-technical terms, as appropriate, for developing accessible Web sites
- 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
- 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:
- Primary audience for this document is people who are trying to "sell" accessibility to their organization, or get "buy-in" from an organization to start a Web accessibility initiative, adopt a Web accessibility policy, etc.
- Secondary audiences include reporters, trainers, ...
- All types of organizations, including commercial/industry, government, education, non-profit, etc.
- Direct audience for this document could be varied, such as technical Web developer, business analyst, outside accessibility advocate, etc.
- The indirect audience is the people reading the organization's customized "business case" which is often managers and others who are responsible for allocating time and money resources to Web projects. These people may not understand the technical aspects of the Web.
Approach (2008-2009 revision)
- Update all WCAG examples to WCAG 2.0 throughout
- Consider old wish-list items - http://www.w3.org/WAI/bcase/changelog#wish
Are any of these important for WAI-AGE?- Table of Contents?
- Myths?
- ATAG?
- Look for places to add additional emphasis regarding the importance of addressing the needs of older users, without overwhelming the the discussion about people with disabilities. Initial ideas below.
- Link to other relevant docs, e.g., WAI-AGE Lit Rev Analysis Conclusions, throughout as appropriate.
- Record additional WAI-AGE/EO documents that will be revised/developed and that could/should be cross-referenced from the Business Case suite when completed
Initial update ideas for consideration (September 2008)
- 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)
- 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
- maybe talk about needs and reference http://www.w3.org/WAI/WAI-AGE/comparative.html for implementation links
- Technical section - http://www.w3.org/WAI/bcase/tech.html
- Add old configurations (PCs/modems/browsers/plug-ins) under 'different configurations'
- 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)
- 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?]
- Add 'age discrimination' legislation
References (2008-2009 revision)
June 2009 Editor's Drafts:
- Overview [DRAFT]
- Social Factors [DRAFT]
- Technical Factors [DRAFT]
- Financial Factors [DRAFT]
- Legal and Policy Factors [DRAFT]
WAI-AGE Task Force and EOWG discussions:
- EO meeting 5 June 2009
- TF meeting 3 June 2009
- EO meeting 29 May 2009
- EO meeting 22 May 2009
- TF meeting 20 May 2009
- EO meeting 15 May 2009
- EO meeting 01 May 2009 (including some notes for discussion)
- TF meeting 25 March 2009
- TF meeting 12 November 2008
- EO Meeting 17 October 2008
- TF Meeting 15 October 2008
- TF Meeting 17 September 2008
Related documents:
- Version 1.1 of Business Case suite - http://www.w3.org/WAI/bcase/Overview
- WAI-AGE project - http://www.w3.org/WAI/WAI-AGE/
- WAI-AGE deliverables - http://www.w3.org/WAI/WAI-AGE/deliverables.html#buscase
- WCAG 2.0 intro page(s) - http://www.w3.org/WAI/intro/wcag20
References:
- Wikipedia - Corporate Social Responsibility
- Terminology - General Writing Guidelines for Technology and People with Disabilities
Changelog (2008-2009 revision)
Consider for next edit / Wishlist:
- "the innovative benefits of a11y. For instance in the area of mobile web, voice browsing, and accessibility features that have become mainstream functionality of common browsers." (Shadi)
"It also broadens your perspective in a way that can lead you to discover new ways of thinking about your product that will make it work better for more people in more situations." - Involving Users
- add "mobile considerations" sub-section to "Web Accessibility Benefits People With and Without Disabilities" in Social Factors
- consider trying to hide/reveal the WCAG material (the SC and Checkpoints can then be linked) (action 1, TF 12 November 2008)
- from EOWG 15 May 2009 (Actions 5 & 6)
- in Introduction of Overview.html: consider a WOW hook up front (maybe even a call out box) and clear up the middle paragraph
- consider the addition of an Appendix with concrete, real-world examples and links (e.g. Legal and General)
- add links to http://www.w3.org/WAI/intro/people-use-web.php (or direct to the Note) when the document is updated
- adjust spacing around lists to bring the top list item closer to the referring paragraph
To do:
- [Done where it seemed appropriate] - look to include words like 'customer satisfaction' or 'customer relations' or 'customer service' appropriately (action 11, EO 17 November 2008)
2009-06-08 version
- Overview
- reinstated the section "Factors in a Business Case for Web Accessibility"
- added a short paragraphe ahead of the "Introduction" section to make it more apparent that there are more pages other than just this Overview one, and that they include more specific detail, without obstructing the Introduction.
- Social Factors
- changed some of uses of 'decline' in the sub-section "Overlap with Older Users' Needs"
- Technical Factors
- no content changes since 4 June
- Fianancial Factors
- no content changes since 4 June
- Policy and Legal Factors
- no content changes since 4 June
- Global change - (Web site) to (website) as appropriate
2009-06-04 version
- Overview
- Moved (and slightly reworded) the section "Factors in a Business Case for Web Accessibility" to become the leading section
- In "Introduction"
- change (Organizations with accessible Web sites benefit from search engine optimization, increased customer loyalty, demonstration of corporate social responsibility, and reduced legal risk) to (Organizations with accessible Web sites benefit from search engine optimization (SEO), reduced legal risk, demonstration of corporate social responsibility (CSR), and increased customer loyalty)
- change (Organizations can recoup their initial costs of implementing Web accessibility through substantial returns on investment (ROI).) to (Organizations can realize substantial return on investment (ROI) that offset any costs of implementing Web accessibility.)
- Change "Copyright and Reuse" heading to "Permission to Use", make H2 and add to 'contents'
- under Examples:
- 'government ministry' changed (requirements based on laws and policies such as anti-discrimination legislation or information and communications technology policy that ensures that public services are available to all) to (laws and policies that require public services are available to all, such as anti-discrimination legislation or information and communications technology (ICT) policy)
- Social Factors
- Under "Overlap with Older Users Needs", note use of "vision/hearing/physical/cognitive decline" rather than "vision/hearing/physical/cognitive impairment".
- Shadi noted: I personally like these changes. We are talking about Web accessibility guidelines addressing older peoples needs. These may not be necessarily impairments that constitute a disability in the usual sense. Even very mild vision or cognitive decline can be well assisted by a better level of usability that is promoted by the Web accessibility guidelines. Note: later on when we are talking about specific benefits and mapping these to Success Criteria, then talking about the actual impairments as per EO discussion seems more sensible.
- Under "Overlap with Older Users Needs", note use of "vision/hearing/physical/cognitive decline" rather than "vision/hearing/physical/cognitive impairment".
- Financial Factors
- deleted the heading "Financial Benefits" and following paragraph
- upgraded "Increased Web Site Use", "Direct Cost Saving", and "Decreasing Costs" to H2 heading (and added to Page Contents)
- question about "What is the current level of Web accessibility in the organization?" removed to reduce number of clarifying questions (considered the least important)
- turned the points under "Increases potential use by more people, expands potential market share" into a list and re-ordered them
- re-ordered the points under "Decreases cost of translating"
- Technical Factors
- moved success criteria and checkpoints to the end of bullets where they occurred mid-bullet
- Legal and Policy Factors
- changed question (Might the org be subject to policies in the future?) to (Will policies later become applicable?)
- the "Understanding Risks for Non-Compliance" section was moved to the end of the page as a better 'conclusion' and adjust the Page Contents menu accordingly
- Global changes
- Additional wordsmithing
- made all references to resources elsewhere on the Web consistent
- change (Success Criteria) to (success criteria) throughout
- change (Checkpoint) to (checkpoint) throughout
- change (text and markup rather than images of text) to (styled text instead of images of text)
- change text color for success criteria & checkpoints to "#515151" to reduce emphasis
- removed "File (not content) last updated on $Date: ..." from footers
2009-06-01 version
- Overview
- no change since 29 May
- Social factors
- in "Access for Older People" changed (Older people with cognitive limitations will benefit from similar aspects as those those with low literacy) to (Older people with cognitive decline will benefit from similar aspects as people with low literacy and people not fluent in the language)
- Financial factors
- no change since 29 May
- Policy and Legal factors
- no changes since 4 May
- Technical factors
- no changes since 21 May
2009-05-29 version
- Overview
- changed (The Web is increasingly an essential resource many aspects of life) to (The Web is increasingly an essential resource for many aspects of life)
- Social factors
- under "Number of People Affected" changed (To estimate how many people are affected by Web accessibility is difficult because) to (Estimating how many people are affected by Web accessibility is difficult because)
- change heading (Overlap with Design for Older Users) to (Overlap with Older Users Needs)
- under "Overlap with Older Users Needs"
- changed (vision/hearing/physical/cognitive impairment) to (vision/hearing/physical/cognitive decline)
- changed (including reductions in fine motor control) to (including reductions in dexterity and fine motor control)
- under "Access for Older People"
- changed (The accessibility provisions that make the Web accessible provide many benefits for people experiencing impairments due to the ageing process) to (The accessibility provisions that make the Web accessible provide many benefits for people experiencing impairments due to the ageing process, even though they may not be regarded as having a disability)
- changed (Older people with age-related visual deterioration benefit from) to (Older people with deteriorating visuion benefit from)
- changed (Older people with diminished fine motor control benefit from) to (Older people with reduced dexterity benefit from)
- added: Older people with cognitive limitations will benefit from similar aspects as those those with low literacy.
- Financial factors
- Under "Additional testing time" changed (Testing design ideas and early prototypes with users with disabilities and older users, and including assistive technologies) to (Testing design ideas and early prototypes with users with disabilities and older users, and with assistive technologies)
- Policy and Legal factors
- no changes since 4 May
- Technical factors
- no changes since 21 May
2009-05-26 version
- Overview
- no changes since 19 May
- Social factors
- introductory sentence to "Web Accessibility is a Social Issue" changed from (People with accessibility needs include people with disabilities, people with ageing related impairments, and people with temporary impairments.) to (Web accessibility focuses on people with all types of disabilities - visual, auditory, physical, speech, cognitive, and neurological disabilities - including older people with age-related impairments.)
- Financial factors
- no changes since 21 May
- Policy and Legal factors
- no changes since 4 May
- Technical factors
- no changes since 21 May
2009-05-21 version
- Overview
- no changes since 19 May
- Social Factors
- Web Accessibility is a Social Issue section
- added open sentence ([People with accessibility needs include people with disabilities, older people with age-related impairments, and people with temporary impairments.])
- changed ( [community participation] for people with disabilities.) to ( [community participation] for people with disabilities and older people.)
- changed (Therefore it is essential that the Web be accessible in order to provide equal access and equal opportunity to people with disabilities.) to (Therefore, Web accessibility is essential for providing equal access and equal opportunity to people with disabilities.)
- changed (there were significant barriers for many people with disabilities) to (many people with accessibility needs faced significant barriers) and changed (it is [still] difficult for some people to get resources from a library) to (some people still face difficulties getting resources from a library)
- Barriers to Web Use subsection
- change (Currently there are significant barriers on the Web for many people with disabilities.) to (Currently, significant barriers on the Web remain for many people with disabilities.)
- change (many people with disabilities have unnecessary difficulties using the Web) to (many people with accessibility needs have unnecessary difficulties using the Web)
- Change link on How People with Disabilities Use the Web to the 2009 intro page (How People with Disabilities Use the Web)
- change (scenarios that illustrate people with different kinds of disabilities) to (scenarios that illustrate people with different kinds of accessibility needs)
- Access for Older People section
- changed (The accessibility provisions that make the Web accessible provide many benefits for older people experiencing age-related impairments) to (The accessibility provisions that make the Web accessible provide many benefits for people experiencing ageing related impairments)
- Number of People Affected sub-section
- changed (It is difficult to estimate how many people are affected by Web accessibility) to (To estimate how many people are affected by Web accessibility is difficult)
- added (Some people with disabilities may not want to disclose their disability in a census, including older people who may not perceive themselves as having a disability.) to first para
- removed final para referring to Lit review - add sentence to the reference para ([The Web Accessibility for Older Users: A Literature Review has statistics on ageing demographics and age-related impairments.])
- Digital Divide subsection
- changed (An organization that is committed to reducing the digital divide can include in its business case a description of how Web accessibility can reduce the impact of the digital divide for people with disabilities.) to (An organization that is committed to reducing the digital divide can include in its business case a description of how Web accessibility can reduce the impact of economic and social barriers to Web use for people with accessibility needs.)
- Web Accessibility Benefits People With and Without Disabilities section
- removed (See Web Content Accessibility Guidelines (WCAG) Overview for more information about the WCAG {1.0 Checkpoint} references below.) and merged with previous para
- Access for Older People subsection
- changed opening para to read: (The accessibility provisions that make the Web accessible provide many benefits for older people experiencing impairments due to the ageing process. For example:) as the issue of older people not perceiving themselves as having a disability is already covered in the "Number of People Affected" section
- Access for People with Low Literacy subsection
- removed SC 3.1.6 from 'clear and simple language as appropriate'
- added SC 1.3.1, 2.4.2, 2.4.10 and 3.3.2 to 'clear and consistent design, navigation, and links'
- added bullet for "provide users enough time to read and use content" with WCAG 2.0 Success Criteria 2.2.1, 2.2.2, 2.2.3; WCAG 1.0 Checkpoint 7.4, 7.5
- Access for People with Low Bandwidth subsection
- change H3 heading to (Access for People with Low Bandwidth Connections to the Internet or Using Older Technologies)
- change (people whose connections are too low to download) to (people whose connections are too slow to download)
- added SC 1.3.1 to 'sites that are organized so they can be read [and understood] without style sheets'
- Role of Organizations' Web Sites section
- changed (people with disabilities) to (people with accessibility needs)
- Web Accessibility is a Social Issue section
- Financial factors
- Purchasing evaluation tools
- change (Web accessibility evaluation tools are software that helps identify accessibility problems) to (Web accessibility evaluation tools are software that help identify accessibility problems) and changed link to http://www.w3.org/WAI/ER/tools/
- Purchasing assistive technologies
- change (Assistive technologies, such as those listed in Alternative Web Browsing, are used by some people with disabilities to access the Web.) to (Some people with disabilities use assistive technologies] to access the Web.)
- Increases usability
- added SC 1.4.4 to the bullet on "using a small black-and-white display" and removed repetitive SC
- Increases potential use in more situations
- change "in a noisy environment" SC from (1.1.1, 1.2.2, 1.2.4) to (1.2.1, 1.2.2, 1.2.4, 1.2.9)
- added new bullet: (working away from their normal connection and experiencing lower bandwidth -
WCAG 2.0 Success Criteria 1.1.1, 1.2.8, 1.4.5, 1.4.9; WCAG 1.0 Checkpoint 1.1, 3.1)
- Increases findability
- change (Some search engines are unable to access some script-generated content such as mouse-overs) to (making content keyboard-accessible might make content more searchable by search engines)
- Increases usability
- change "clear and consistent design, navigation, and links" SC from (2.4.4, 2.4.9, 2.4.5, 3.2.3, 3.2.4, 2.4.1, 2.4.6, 3.2.3, 3.2.4) to (SC 2.4.2, 2.4.4, 2.4.5, 2.4.6, 2.4.9, 3.2.3, 3.2.4, Guideline 3.3)
- Decreases cost of
translating
- change "clear and consistent design, navigation, and links" SC from (2.4.4, 2.4.9, 2.4.5, 3.2.3, 3.2.4, 2.4.1, 2.4.6, 3.2.3, 3.2.4) to (2.4.2, 2.4.4, 2.4.5, 2.4.6, 2.4.9, 2.4.10, 3.1.5, 3.2.3, 3.2.4
- Purchasing evaluation tools
- Policy and Legal factors
- no changes since 4 May
- Technical factors
- Change order of SC under bullet 'Reduce time and effort needed to change presentation' from (1.4.5, 1.4.9, 1.3.1, 2.4.10) to (1.3.1, 1.4.5, 1.4.9, 2.4.10)
- Change SC under bullet 'Facilitate efficient debugging' from (4.1.1, 1.3.1) to (1.3.1, 4.1.1, 4.1.2)
- Change heading (Reduce Server Load) to (Reduce Bandwidth Use and Server Load)
Amend page navigation to match - Under Reduce Bandwidth and Server Load, change (Web accessibility techniques {can} [usually] reduce the [per page] server load, [which increases the download speed and can reduce the need for additional bandwidth,]) to (Web accessibility techniques can reduce the server load, [which increases the download speed and can reduce the need for additional bandwidth or servers,])
- Under the 'Reduce unwanted page downloading' bullet, change SC from (2.4.4, 2.4.9, 2.4.5, 3.2.3, 3.2.4, 2.4.1, 2.4.6, 3.2.3, 3.2.4) to (2.4.2, 2.4.4, 2.4.5, 2.4.9, 3.2.3, 3.2.4)
- Change question in Identifying Technical Factors from (How important is it to the organization to reduce server load?) to (How important is it to the organization to
reduce bandwidth use or server load?)
and change (See Reduce Server Load) to (See Reduce Bandwidth Use and Server Load) - under bullet 'Allow users and user agents to access content for different configurations, and servers to provide content for different configurations' added mention of Conformance Requirements - i.e. change (WCAG 2.0 Success Criteria 4.1.1, 4.1.2) to (WCAG 2.0 Success Criteria 4.1.1, 4.1.2 and Conformance Requirements 1, 4)
- under bullet 'Render stylized information across a wide range of configurations' change SC from (1.4.1, 1.4.5, 1.3.1) to (1.3.1, 1.4.1, 1.4.3, 1.4.4, 1.4.5, 1.4.6)
- under bullet 'Allow content re-use' change SC from (1.3.1, 4.1.2) to (1.3.1, 1.4.3, 1.4.4, 1.4.6, 4.1.2)
2009-05-19 version
- Overview
- first para
- correct 'afirms' to 'affirms'
- change (The Web is increasingly an essential resource around the world for many aspects of life:) to (The Web is increasingly an essential resource for many aspects of life:)
- change (The Web is [important] {used} for receiving information as well as providing information and interacting with society) to (The Web is used not only for receiving information, but also for providing information and interacting with society)
- comma added - social interaction,
- second para
- change (While accessibility focuses on people with disabilities, accessibility also benefits older users, mobile phone users, and other individuals, as well as organizations that develop accessible products.) to (While accessibility focuses on people with disabilities, accessibility also benefits older users, people with low literacy, mobile phone users, and other individuals, as well as organizations.)
- change (Older users with age-related accessibility needs are an increasingly important customer base for most organizations as the percentage of older users is significantly increasing) to (Older users with age-related accessibility needs are an increasingly important audience for most websites, as the percentage of older users is increasing significantly.)
- change (Organizations with accessible Web sites can also benefit from ...) to (Organizations with accessible Web sites benefit from ...)
- comma added - mobile phone users,
- third para
- change ([While there] are initial costs for organizations implementing Web accessibility, [there can be substantial returns on investment (ROI).]) to (Organizations can recoup their initial costs of implementing Web accessibility through substantial returns on investment (ROI).)
- How to Use sub-section
- change (The five pages, called a "resource suite", are designed to help develop) to (The five pages, called a "resource suite", cover social, technical, financial, and legal and policy factors, and are designed to help develop)
- Factor section
- change 3rd bullet from (... cost savings, and cost considerations including initial {costs} and on-going costs.) to (... cost savings; and considerations for initial costs, on-going costs, and ways to decrease costs.)
- Developing a Business Case section
- change (Just as organizations' objectives and motivations are different, their business cases for Web accessibility are {somewhat} different.) to (Just as organizations' objectives and motivations vary, so too do their business cases for Web accessibility.)
- Examples
- removed "the" from the start of all sub-bullets
- Under Government Department, add a sub-bullet ([demonstration of social responsibility and provision of information and services that are accessible to all citizens])
- Related resources section
- added the opening para back in; added (Additional resources that might assist in the preparation of a business plan include:) at the end of this opening para
- added (Also includes some statistics about changing demographics and the prevalence of impairment with age.) to the WAI-AGE Lit Review resources description.
- removed mention of the Implementation Plan from "WAI Resources" item
- first para
- Social Factors
- Change to follow
- Financial factors
- Changes to follow
- Policy and Legal factors
- Changes to follow
- Technical factors
- Changes to follow
2009-05-04 version
- Overview
- Adopted actions recorded in http://www.w3.org/2009/05/01-eo-minutes.html regarding the Introduction
- Social
- Added subsection about "Overlap with design for older users" after "Overlap with digital divide issues" and moved much of the added text from "Access for Older People" to here
- Reinstated the deleted text from "Access for Older People" as a short intro to the specific benefits
- Changed the link associated with the question "Does the organization focus on other groups that benefit from Web accessibility?" to go to the new subsection on "Overlap with design for older users"
- changed "How People with Disabilities Use the Web" links to http://www.w3.org/WAI/intro/people-use-web
- Moved "Web Accessibility is an Aspect of Corporate Social Responsibility" and "Role of Organizations' Web Sites" to bottom of page
- Financial factors
- no changes
- Policy and Legal factors
- no changes
- Technical factors
- no changes
2009-04-30 version
- Overview
- Wordsmithing on Introduction
- Financial factors
- wordsmithing on the "Decrease personnel costs" bullet under Direct Cost Saving
2009-04-29 version
- Overview
- Wordsmithing
- Social factors
- Wordsmithing
- Resolved - the issue that a "consideration of the social factors associated with Web accessibility can help understand the potential market" and thus influence the "marketing an organization undertakes" is a very indirect benefit of creating accessibility Web sites. While an organization should take advantage of creating accessible sites, there is probably little or no quantifiable benefit. This factor has not been included at this stage.
- Financial factors
- Wordsmithing
- Policy and Legal factors
- no changes
- Technical factors
- no changes
2009-03-23 version
- All sections:
- updated for clarity and readability after suggestions from Shawn
- general wordsmithing
- corrected UK spelling to US spelling
- use of quotes (single/double) made consistent
2009-01-19 version
- Overview
- separated out older and other users from the opening para
- linked to the different docs in the 'Developing a Customized Business
Case' section - turned the extra resources into a DL as per www.w3.org/WAI/gettingstarted/Overview.html
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).
- Overview
- linked to the Overview page for the Lit Review, rather than the Lit Review itself
- Social
- refined the section on Older People
2008-11-11 version
Additional word-smithing for consistency and tone (Shawn & Andrew). Minor content changes include:
- Social
- Added mention of benefit to older people after examples under "barriers to Web Use"
- Legal and policy
- added mention of laws requiring 'accessibility accommodations' under "Determining Applicable Policies"
- Technical
- moved use of authoring tool bullet to Financial benefits
- Financial
- added 'completing course work' under "increased Web site usage"
2008-11-06 version
The following changes were discussed and recommended at during the EOWG teleconference of 17 Nov 2008
- Overall
(all sections)
- place WCAG 2.0 SC ahead of WCAG 1.0 checkpoints
- if something is not definite benefit or a clear requirement in WCAG 2.0, then consider dropping (mark for deletion)
- check tone of document to be stronger or more definitive, e.g. 'can' > 'will'
- Overview
- strengthened opening paragraph to refer to the Web as "an essential resource"
- moved and expanded 'business benefits' to separate introductory paragraph
- clearly mention 'corporate social responsibility' under the corporation example
- added bullet to 'educational institution example about ageing staff
- changed bullet under e-Commerce to SEO
- Social Factors
- add mention of UN Convention
- mentioned the ' importance of social factors to marketing issues' in the introduction
- Technical Factors
- no specific changes
- Financial Factors
- added "customer loyalty" and "word of mouth" marketing to 'expand market share'
- Legal and Policy Factors
- add mention of UN Convention
2008-10-16 version
- Overview
- added placeholder for an e-Commerce business or SME under "examples" - expanded this in 17/Oct draft
- Social Factors
- added "For people with limited mobility due to age or disability, the Web provides an ongoing opportunity for active participation in the community" under Equal Opportunity
- Legal and Policy Factors
- added "the provision of public funds to an organization may mean it is required to comply with government policies" under Considerations for Different Types of Organizations
- Technical Factors
- Made a technical correction to "reduce server load"
2008-10-06 version
- Overview
- mention 'social interaction' in the Introduction
- added reference to UN Convention in the Introduction
- updated citation note (editor and date)
- added "the increased productivity from supporting and retaining older workers and their experience" to Corporation examples
- added "the benefits from encouraging people with disabilities and older users to interact with them online" to Government examples
- added "attracting older donors to support the organization" to NGO examples
- added H3 headings to highlight 'how to use' and 'copyright' sections
- Social factors
- added "service delivery" to the the open para of 'Web Accessibility is Essential for Equal Opportunity
- added "In addition to people with disabilities, the "Web Accessibility for Older Users: A Literature Review" has identified that a large proportion of older people experience age-related functional and sensory impairments. Older people will also benefit from enhanced Web accessibility. Furthermore, the changing demographics in many countries indicates a rapid change in proportion of older people to those in the work in the coming decades, emphasizing the importance of supporting this group." and linked to Lit Review for age-related impairment statistics to the section 'Barriers to Web Use'
- Added mention of ATAG to the section 'Role of Organizations' Web Sites'
- re-wrote the introduction in "Access for Older People", added hearing as an issue, and linked to 'comarative.html' for additional examples
- Added "or because they didn't use computers during their working life and are discovering their relevance later in life" to the section 'Access for New and Infrequent Web Users'
- Technical factors
- Added "Reduce post-publication accessibility adjustments by using an authoring tool or content management system (CMS) that is conformant with the Authoring Tools Accessibility Guidelines and generates accessible pages" to the section 'Reduce Site Development and Maintenance Time'
- Financial factors
- Added "Does the organization want to retain the knowledge and experience of its older employees?
If so, the business case can emphasize the internal benefits of an accessible Web site" to the section 'Identifying Financial Factors for a Specific Organization' - Added "filing tax returns and paying rates online" and "or monitoring their pension funds" to the section 'Increased Web Site Use' and added "many countries, as discussed in Social Factors, age demographics are changing rapidly" to the 'market share section'
- Added "Retention of knowledge and expertise of older employees - The expertise and experience of older employees experiencing some age-related functional impairments as discussed under Access for Older People in Social Factors can be retained if an organization develops its intranet to conform to Web accessibility guidelines." to the 'Direct Cost Savings' section.
- Added "people with disabilities and older users, some of whom may use" and "and testing for an appropriate tabbing order for keyboard users" to 'Additional testing time'
- Added "Does the organization want to retain the knowledge and experience of its older employees?
- Legal and Policy Factors
- Added "Is there any disability or age discrimination legislation applying to the workplace? If so, the business case can list those laws or mandates as requirements for accessible Web sites. See Determining Applicable Policies" to the section 'Identifying Legal and Policy Factors for a Specific Organization'
- Added "In some countries, an inaccessible intranet may also contravene laws that protect the rights of people with disabilities and older people with respect to employment opportunities." to the section 'Determining Applicable Policies'
- Added local government to the Government example under the subsection 'Considerations for Different Types of Organizations'
- All sections - added reference to appropriate WCAG 2.0 Success Criteria