WCAG 2.0
Articles and resources about the Web Content Accessibility Guidelines 2.0 (better known as WCAG 2.0).
- Release of WCAG 2.0 Techniques for PDF
- By Andrew Arch - AGIMO Blog, 12 January 2012. "On 3 January 2012, the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) published updated Techniques for Web Content Accessibility Guidelines (WCAG) 2.0, including new techniques for the Portable Document Format (PDF) and Silverlight, and an update to Understanding WCAG 2.0..."
- PDF Techniques for WCAG 2.0
- W3C Working Group Note, 2012. "This Web page lists PDF Techniques from Techniques for WCAG 2.0: Techniques and Failures for Web Content Accessibility Guidelines 2.0. Technology-specific techniques do not supplant the general techniques: content developers should consider both general techniques and technology-specific techniques as they work toward conformance..."
- Info and Relationships: Understanding SC 1.3.1
- Understanding WCAG 2.0 - W3C. "The intent of this Success Criterion is to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes. For example, the presentation format changes when the content is read by a screen reader or when a user style sheet is substituted for the style sheet provided by the author..."
- The Hidden Nuggets of WCAG2: Information Relationships
- By Gian Wild. SitePoint, November 2, 2011. "The Information and Relationships Success Criterion is a very complex requirement. Unlike other success criterion, it is not sufficient to comply with only one or two of the listed techniques – it is important to comply with all the relevant techniques. This means that this success criterion covers a wide range of requirements – in fact it covers many WCAG1 checkpoints, such as table headers, headings, coding lists etc..."
- The Hidden Nuggets of WCAG2: An Introduction
- By Gian Wild. SitePoint, October 25, 2011. "WCAG2 – it's complicated. But just like climate change, that doesn't mean we can ignore it and hope it goes away. Just like climate change, there are proponents on both sides of the issue, and just like climate change, people are vehement about the subject.
But WCAG2 doesn't need to be that complicated. Yes – it is a long series of documents. Yes – sometimes it isn't clear exactly what is required. But I'm here to demystify the set of guidelines, and tell you the hidden bits and pieces that you really need to know about.
In this series of articles, I'll be talking about all the big issues in accessibility: images and alt attributes, video, keyboard accessibility, forms, tables, skip links and many more. I'll be including concrete examples, and actual code that you can implement as well as linking to useful how-to guides. I hope this series of articles serves to simplify some of the more confusing areas of WCAG2..."
- Silverlight Techniques for WCAG 2.0
- W3C, 21 June 2011. "... Silverlight support for assistive technologies is based on implementing Silverlight for Microsoft UI Automation (often abbreviated as UIA). In the UIA accessibility framework, Silverlight is implemented as a UI Automation server. This means that Silverlight provides information about the application itself and its current content through the framework. Any subscriber to the operating system's automation can consume that information as a UI Automation client. One such client role is typically implemented by assistive technologies, most notably by screen readers. By acting as a UI Automation client, an assistive technology can programmatically determine many aspects of Silverlight content and content structure. In addition, UIA has APIs that can change the content in a predictable way that maintains security boundaries between applications. Reading information from Silverlight through the UIA accessibility framework requires no extra work on the part of a given assistive technology, presuming that the assistive technology has already implemented UIA. All information that Silverlight reports to UIA comes through the common property set, and a fixed set of possible user interactions is programmatically accessible through a discoverable set of automation patterns and techniques..."
- PDF Techniques for WCAG 2.0 - W3C Editor's Draft
- W3C, 21 June 2011. "... The Portable Document Format (PDF) is a file format for representing documents in a manner independent of the application software, hardware, and operating system used to create them, as well as of the output device on which they are to be displayed or printed. PDF files specify the appearance of pages in a document in a reliable, device-independent manner. The PDF specification was introduced by Adobe Systems in 1993 as a publicly available standard. In January 2008, PDF 1.7 became an ISO standard (ISO 32000-1)...
PDF includes several features in support of accessibility of documents to users with disabilities. The core of this support lies in the ability to determine the logical order of content in a PDF document, independently of the content's appearance or layout, through logical structure and Tagged PDF. Applications can extract the content of a document for presentation to users with disabilities by traversing the structure hierarchy and presenting the contents of each node. For this reason, producers of PDF files must ensure that all information in a document is reachable by means of the structure hierarchy..."
- For Review: Updated WCAG 2.0 Techniques
- W3C - Web Accessibility Initiative, 21 June 2011. "WAI announces a Call for Review of draft updates to supporting documents for WCAG 2.0: Techniques for WCAG 2.0 (Editors' Draft) and Understanding WCAG 2.0 (Editors' Draft). (This is not an update to WCAG 2.0, which is a stable document.) To learn more about the updates, see Call for Review: WCAG 2.0 Techniques Draft Updates e-mail. Please submit comments by 26 August 2011..."
- Yes I'm recommending WCAG2 now
- Gian Wild - Practical accessibility, April 1, 2011. "I had a client ring me yesterday, wanting to know if they should be trying to comply with WCAG1 or WCAG2. They had read my article: Why I'm sticking with WCAG1… for now, and wanted to check if my opinion still held. I wrote that post a little over a year ago, and although much has stayed the same (there are still few free accessibility testing tools that test against WCAG2 for example), much has changed. For example, the Australian Government Information Management Office (AGIMO) has released the Web Accessibility National Transition Strategy, the Australian Human Rights Commission (AHRC) have updated their Web Advisory Notes and most states in Australia now have formalised compliance to WCAG2 or are following the federal strategy. There is still a lot of confusion regarding WCAG2. It is still a very complex series of documents that require specialist interpretation..."
- Understanding WCAG 2.0
- A guide to understanding and implementing Web Content Accessibility Guidelines 2.0. W3C Working Group Note, 14 October 2010. "Abstract - This document, "Understanding WCAG 2.0," is an essential guide to understanding and using Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. It is part of a series of documents that support WCAG 2.0. Please note that the contents of this document are informative (they provide guidance), and not normative (they do not set requirements for conforming to WCAG 2.0). See Web Content Accessibility Guidelines (WCAG) Overview for an introduction to WCAG, supporting technical documents, and educational material. WCAG 2.0 establishes a set of Success Criteria to define conformance to the WCAG 2.0 Guidelines. A Success Criterion is a testable statement that will be either true or false when applied to specific Web content. "Understanding WCAG 2.0" provides detailed information about each Success Criterion, including its intent, the key terms that are used in the Success Criterion, and how the Success Criteria in WCAG 2.0 help people with different types of disabilities. This document also provides examples of Web content that meet the success criterion using various Web technologies (for instance, HTML, CSS, XML), and common examples of Web content that does not meet the success criterion. This document indicates specific techniques to meet each Success Criterion. Details for how to implement each technique are available in Techniques for WCAG 2.0, but "Understanding WCAG 2.0" provides the information about the relationship of each technique to the Success Criteria. Techniques are categorized by the level of support they provide for the Success Criteria. "Sufficient techniques" are sufficient to meet a particular Success Criterion (either by themselves or in combination with other techniques), while other techniques are advisory and therefore optional. None of the techniques are required to meet WCAG 2.0, although some may be the only known method if a particular technology is used. "Advisory techniques" are not sufficient to meet the Success Criteria on their own (because they are not testable or provide incomplete support) but it is encouraged that authors follow them when possible to provide enhanced accessibility. Another support category is "Common Failures", which describe authoring practices known to cause Web content not to conform to WCAG 2.0. Although failures provide advisory information about certain authoring practices, authors must avoid those practices in order to meet the WCAG 2.0 Success Criteria..."
- Techniques for WCAG 2.0
- Techniques and Failures for Web Content Accessibility Guidelines 2.0. W3C Working Group Note, 14 October 2010. "Abstract - "Techniques for WCAG 2.0" provides information to Web content developers who wish to satisfy the success criteria of Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. Techniques are specific authoring practices that may be used in support of the WCAG 2.0 success criteria. This document provides "General Techniques" that describe basic practices that are applicable to any technology, and technology-specific techniques that provide information applicable to specific technologies. Use of the techniques provided in this document makes it easier for Web content to demonstrate conformance to WCAG 2.0 success criteria than if these techniques are not used. Besides the techniques provided in this document, there may be other techniques that can be used to implement conformance to WCAG 2.0. The WCAG WG encourages submission of such techniques so they can be considered for inclusion in this document, in order to make the set of techniques maintained by the WCAG WG as comprehensive as possible..."
- New and Improved WCAG 2.0 Techniques
- by Shawn Henry. W3C Blog, October 14, 2010. "Today W3C WAI published updated Techniques for WCAG 2.0 and Understanding WCAG 2.0, following a public review and comment period... etailed guidance, including technology-specific guidance, on meeting WCAG 2.0 is provided in the following supporting documents: Techniques for WCAG 2.0 - guidance for developers with general and technology-specific examples, including for HTML/XHTML, CSS, scripting, multimedia, Flash, and WAI-ARIA; Understanding WCAG 2.0 - includes the intent of the guideline or success criterion; how it helps people with different disabilities, browser and assistive technology support notes, examples, and resources..."
- Call for Review: WCAG 2.0 Techniques Draft Updates
- by Shawn Lawton Henry. W3C, 8 July 2010. "The W3C WAI announces a Call for Review of updates to two supporting documents for Web Content Accessibility Guideline (WCAG) 2.0. This is not an update to WCAG 2.0, which is a stable document. The supporting documents (W3C Notes) are updated periodically to reflect current practices and technologies. The existing Techniques and Understanding documents remain in place as W3C Notes while the separate draft updates are under review and the WCAG Working Group addresses comments. The following draft updates are available for review as Editors' Drafts: Techniques for WCAG 2.0 Editors' Draft; Understanding WCAG 2.0 Editors' Draft.."
- Australian Government endorses WCAG 2.0 - stipulates compliance by 2015
- eGov AU - Craig Thomler's personal eGovernment and Gov 2.0 thoughts and speculations from an Australian perspective, Monday, March 1, 2010. "Finance Minister Lindsay Tanner and Parliamentary Secretary for Disabilities Bill Shorten issued a joint media release last Tuesday 23 February confirming that the Australian Government had endorsed the W3C's latest accessibility standard, Web Content Accessibility Guidelines 2.0 (or WCAG 2.0)..."
- How should the UK public sector adopt WCAG 2.0?
- by Jack Pickard. The Pickard's Blog, Friday, October 16, 2009. "Well, quickly would be a good start, as it's a lot better than WCAG 1.0 — it doesn't rely testing based on specific technologies, but instead looks at the impact on the user. But that's not what I'm looking at here. I'm looking at what parts of WCAG 2.0 that I think are appropriate to set as a minimum standard for public sector sites in the UK..."
This category last updated: 3 February 2012