• Skip to content
• | To change text size or colors

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

Site Navigation

W3C Home

Web Accessibility Initiative (WAI) Home

WAI document edits along with WCAG 2.0 Rec publication

Potential New & Updated WCAG Documents

Overall WCAG Overview

• [done] Web site navigation
• [done] Web Content Accessibility Guidelines (WCAG) Overview
  
  • note that this follows a template structure and content, along with UAAG, ATAG, and EARL overviews (and we're not keen on making drastic changes at this point)

WCAG 2.0 Pages

• WCAG 2.0 friendly landing page - potential new page - maybe annotated nav page for all the docs
• [done] The WCAG 2.0 Documents
  
  • open: video for this bit ?
• [done] WCAG 2.0 at a Glance
  • open: provide print version
• [done, but will probably add to] WCAG 2.0 FAQ
  
  • open: is the AST FAQ integrated here or a separate document?
• Benefits of WCAG 2.0 - presentation material and video
  [status: a few updates needed, to the images especially; also need cover page]
  • [Draft] Benefits of WCAG 2.0 presentation material (.ppt, 500KB), HTML version

Transition Pages

• [done] How WCAG 2.0 Differs from WCAG 1.0
• [done] Comparison of WCAG 1.0 Checkpoints to WCAG 2.0 (current page)
  • minor tweak pending (from before)
• [done] How to Update Your Web Site from WCAG 1.0 to WCAG 2.0
  • ideas for later edit
• [Judy] Transitioning Web Accessibility Policies to WCAG 2.0
  • draft in development, might be an update to Developing Organizational Policies on Web Accessibility and not a new page
  • draft from Lisa Pappas ready for Judy 24 Nov, sent in e-mail

WCAG 1.0 Pages

• [done] Web Content Accessibility Guidelines (WCAG) 1.0 Documents (current page)
• [done] Navigating WCAG 1.0 Guidelines and Techniques Documents (current page)
• [done] Quick Tips to Make Accessible Web Sites
  • consider what to do with this, e.g,. take it out of the main site nav? ...
• [done] http://www.w3.org/WAI/WCAG1-Conformance.html
  [done] WCAG1A-Conformance.html, WCAG1AA-Conformance.html, WCAG1AAA-Conformance.html

Other WAI pages - edits completed

• [done] Process 101
  • Current: Web Content Accessibility Guidelines: WCAG Overview, WCAG 1.0 (May 1999)
    Edit: Web Content Accessibility Guidelines: WCAG Overview, WCAG 1.0 (May 1999), WCAG 2.0 (December 2008)
  • Current: WAI Resources cover a wide range of Web accessibility topics, such as Overview of WCAG 2.0 Documents, Quick Tips to Make Accessible Web Sites, Essential Components of Web Accessibility, and many others listed in the WAI Resources.
    Edit: WAI Resources cover a wide range of Web accessibility topics, such as Essential Components of Web Accessibility, WCAG 2.0 at a Glance, Developing a Web Accessibility Business Case for Your Organization, and many others listed in the WAI Resources.
• [done] ATAG Overview
  • Current: ATAG 2.0 is being developed to be compatible with WCAG 2.0, which is under development, and WCAG 1.0, which was completed in May 1999. WAI anticipates ATAG 2.0 may be completed in 2008.
    Edit: ATAG 2.0 is being developed to be compatible with WCAG 2.0, which was completed in December 2008, and WCAG 1.0, which was completed in May 1999. WAI anticipates ATAG 2.0 will be completed in 2009.
• [done] Participating in WAI
  • Current: Place WCAG logos on your site if it meets WCAG 1.0
    Edit: Place WCAG logos[update link] on your site if it meets WCAG 2.0
  • Note: While there, good to fix ATAG 1.0 and UAAG 1.0 too
• [done] WAI Guidelines and Techniques
  • Current: WCAG 1.0
    Edit: WCAG 2.0
• [done] Contacting WAI
  • Current: For example, Techniques for Web Content Accessibility Guidelines 1.0 links to techniques and examples for making Web sites accessible.
    Edit: For example, Understanding WCAG 2.0 provides extensive guidance on making Web sites accessible, including the intent of guidelines and success criteria; how they help people with different disabilities, browser and assistive technology support notes, examples, and resources.
  • Current: For example, Send comments on WCAG 2.0 Working Drafts to: public-comments-wcag20@w3.org (a public list)
    Edit: just delete it
• [done, although would be good to check when fresh sometime] WAI sitemap
• [done, although a few things pending review] Translating WAI Documents
• [done, unless I hear otherwise to change it] UAAG Overview
  • Current: "UAAG 2.0 is being developed to be compatible with WCAG 2.0, which is under development, and WCAG 1.0, which was completed in May 1999."
    Edit: Jeanne, Judy, Jim have been asked for a different sentence for this. [Tues 18 Nov]
    for now: "UAAG 2.0 is being developed to help make the next and future generations of Web browsers functionally accessible, provide access to alternative information based on the users technology and platform, and align with WCAG 2.0 and ATAG 2.0." based on last email from Jim on 11/20/2008

Other WAI pages - edits in progress

[done] Added the following "update note" to most of the pages below:

Note: WCAG 2.0 was published in December 2008, and is recommended over WCAG 1.0. See Web Content Accessibility Guidelines (WCAG) Overview.
We will soon update this page to reflect this change.

Try to fix before 2 Dec

• [done] WAI Resources
• [done - doc update/re-write in progress] Standards Harmonization (update note added)
  • Current: While W3C's Web Content Accessibility Guidelines 1.0 (WCAG 1.0) is the most broadly adopted Web accessibility standard internationally, many countries have developed or are in the process of developing their own versions of technical guidelines or standards.
    Edit: @@
  • Current: For Web developers using today's authoring tools, development of accessible Web sites first requires an awareness of the need for Web accessibility, then a deliberate effort to apply WCAG 1.0.
    Edit: ...then a deliberate effort to apply WCAG.
  • Current: - the Web Content Accessibility Guidelines 1.0 (WCAG 1.0), which describe how to make Web content and Web sites accessible;
    Edit: - the Web Content Accessibility Guidelines (WCAG)...
  • OPEN: Need to do a closer review of this for other changes.
  • NOTE: Consider fixing other 1.0 references while in there, e.g., take "1.0" out of: "Authoring tools that conform to ATAG 1.0 provide...", "the Authoring Tool Accessibility Guidelines 1.0 (ATAG 1.0)" and "the User Agent Accessibility Guidelines 1.0 (UAAG 1.0)".
• [done] Developing Policies (update note added)
  • Judy working on, with Lisa Pappas, Shadi, others
  • draft from Lisa Pappas ready for Judy 24 Nov, sent in e-mail
• [done] Improving the Accessibility of Your Web Site (update note added)
  • Current: For example, an organization sets its target to meet WCAG 1.0 Priority 1 and Priority 2 checkpoints (also known as Level Double-A conformance).
    Edit: For example, an organization sets its target to meet WCAG 2.0 Level A and Level AA success criteria.
  • Current: For example, meet WCAG 1.0 Priority 1 Checkpoints in key Web pages within 2 months, and meet Priority 2 Checkpoints in all pages within 9 months.
    Edit: For example, meet WCAG 2.0 Level A success criteria in key Web pages within 2 months, and meet Level AA success criteria in all pages within 9 months.
  • Current: Checklist of Checkpoints for WCAG 1.0 lists the WCAG checkpoints by priority level and topic. (For background, see the "What is in WCAG 1.0" section of the Web Content Accessibility Guidelines (WCAG) Overview document.)
    Edit: With How to Meet WCAG 2.0: A customizable quick reference to Web Content Accessibility Guidelines 2.0 requirements (success criteria) and techniques allows you to generate a list of success criteria by Level. [and maybe more, see context for if want to mention Understanding or other]
  • Current: Accessibility barriers are often identified by WCAG 1.0 Checkpoint. Each Checkpoint has a Priority that helps determine the impact of a particular accessibility barrier.
  • OPEN: Review for other edits to take advantage of new WCAG 2.0 support materials.
• [n/a - resources marked as out-of-date] Overview of the Web Accessibility Initiative (WAI) Slides - slides that reference WCAG 1.0:
  
  • note: Judy wants to update (and it's badly needed (e.g., has unreadable shadow headings :(, including to the new slidey...)
  • overview page (update note added)
  • all slide content in one HTML file (update note added)
  • 2. Developing Guidelines for Accessibility
  • WCAG
  • Supporting Resources for WCAG
  • 4. Conducting Education & Outreach

Evaluation Suite pages

Shadi doing these after R-day. While there:

• Consider putting a note that these are not current best practice, such as:
  @@
• Fix in the footers "Version note: Document currently being revised (Change log), will be updated in 2006."

WCAG 1.0 references and links that need to be fixed (notes on finding fixes) (in some cases probably just delete the link):

• Preliminary Review of Web Sites for Accessibility
• Is <a href="http://www.w3.org/TR/WCAG10/#equivalent" shape="rect">equivalent</a> information available through the voice or text browser as is available through the <acronym title="Graphical User Interface">GUI</acronym> browser?
  
• Conformance Evaluation of Web Sites for Accessibility
• Determine and disclose the target conformance level of WCAG 1.0.
• Examine the selected sample of pages using checkpoints from the Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 that are applicable to your site.
• Is <a href="http://www.w3.org/TR/WCAG10/#equivalent" shape="rect">equivalent</a> information and function (for example, links and scripted events) available through the text browser as is available through the GUI browser?
  
• Is <a href="http://www.w3.org/TR/WCAG10/#equivalent" shape="rect">equivalent</a> information available through the voice browser as is available through the GUI browser?
• Evaluation Approaches for Specific Contexts
• Evaluate static templates using the Web Content Accessibility Guidelines 1.0.
• For pages that are generated as a result of a query to a database, the source generated as the page is rendered should be captured and evaluated using the Web Content Accessibility Guidelines 1.0
• Web Accessibility Evaluation Tools: Overview
  • no references to WCAG 1.0 in the text, but will want to add WCAG 2.0 in the database & search UI
• Using Combined Expertise to Evaluate Web Accessibility
• simple links in the Appendix
• Template for Accessibility Evaluation Reports
  • several ones that may be easy to just change to 2.0
  • NOTE: also need to fix links in the "References" section that go to old drafts where we now have completed documents to point to

Could wait until after 15 Dec

• [done] Developing a Web Accessibility Business Case for Your Organization: Overview
  • Andrew is working on. Bcase changes draft.
• [not needed] Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities
• [done] Implementation Plan for Web Accessibility
  • Some changes needed for references and links to WCAG 1.0, WCAG 1.0 Techniques, ATAG 1.0
  • Some changes needed to fix links to the Eval Suite, e.g., /WAI/eval/#eval and /WAI/eval/#prelim no longer exists
• [done] Selecting and Using Authoring Tools for Web Accessibility
  • Current: become familiar with the general concepts (at the guideline level, not necessarily the individual checkpoints) in Web Content Accessibility Guidelines 1.0 (WCAG 1.0) and ATAG 1.0;
    Edit: become familiar with the general concepts (at the guideline level, not necessarily the individual success criteria) in Web Content Accessibility Guidelines (WCAG) and ATAG;
  • Current: If an authoring tool does not display a linearized version of tables [ATAG 1.0 Checkpoint 3.2] and techniques for [WCAG 1.0 Checkpoints 5.1 - 5.4]
    Edit: If an authoring tool does not display a linearized version of tables [ATAG 1.0 Checkpoint 3.2] and techniques for [WCAG 2.0 Success Criteria X.X]
  • Also skim for any other edits needed
    

Document Information

Last updated: $Date: 2011/11/14 18:46:56 $ by $Author: shawn $

[Contacting WAI]