background preloader

WCAG

Facebook Twitter

508

National Transition Strategy to WCAG 2.0 - SA Government Web Community of Practice - South Australian Government Exchange. WCAG 2.0 Web Accessibility Resources - South Australian Government Exchange. The WCAG 2.0 Documents. WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities Site Navigation: W3C Home > WAI Home > WCAG Overview This page describes the different WCAG 2.0 technical documents, to help you know where to go for which type of information. For background, an introduction to WCAG, and links to additional information, see Web Content Accessibility Guidelines (WCAG) Overview. Different documents for different purposes Figure 1: WCAG 2.0 documents Web Content Accessibility Guidelines (WCAG) 2.0 itself is designed to be a stable, referenceable technical standard.

How to Meet Customizable Quick Reference Figure 2: Example customization box How to Meet WCAG 2.0: A customizable quick reference to WCAG 2.0 requirements (Success Criteria) and techniques is a key resource for designers and developers using WCAG 2.0. The success criteria are the testable statements that define how Web content meets (conforms to) WCAG 2.0.

Understanding WCAG 2.0 Techniques for WCAG 2.0. Techniques for WCAG 2.0. Techniques and Failures for Web Content Accessibility Guidelines 2.0 W3C Working Group Note 8 April 2014 This version: Latest version: Previous version: Editors: Michael Cooper, W3C Andrew Kirkpatrick, Adobe Systems Inc. Joshue O Connor, NCBI Centre for Inclusive Technology (CFIT) Previous Editors: Loretta Guarino Reid (until May 2013 while at Google, Inc.) Gregg Vanderheiden (until May 2013 while at Trace R&D Center, University of Wisconsin-Madison) Ben Caldwell (until September 2010 while at Trace R&D Center, University of Wisconsin-Madison) Wendy Chisholm (until July 2006 while at W3C) John Slatin (until June 2006 while at Accessibility Institute, University of Texas at Austin) This document is also available in these non-normative formats: Copyright © 2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved.

Status of This Document. Understanding WCAG 2.0. A guide to understanding and implementing Web Content Accessibility Guidelines 2.0 W3C Working Group Note 8 April 2014 This version: Latest version: Previous version: Editors: Michael Cooper, W3C Andrew Kirkpatrick, Adobe Systems Inc. Joshue O Connor, NCBI Centre for Inclusive Technology (CFIT) Previous Editors: Loretta Guarino Reid (until May 2013 while at Google, Inc.) Gregg Vanderheiden (until May 2013 while at Trace R&D Center, University of Wisconsin-Madison) Ben Caldwell (until September 2010 while at Trace R&D Center, University of Wisconsin-Madison) Wendy Chisholm (until July 2006 while at W3C) John Slatin (until June 2006 while at Accessibility Institute, University of Texas at Austin) This document is also available in these non-normative formats: Copyright © 2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Abstract. How to Meet WCAG 2.0. For moving, blinking, scrolling, or auto-updating information, all of the following are true: Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; andAuto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3. Web Content Accessibility Guidelines (WCAG) 2.0. This publication has been funded in part with Federal funds from the U.S. Department of Education, National Institute on Disability and Rehabilitation Research (NIDRR) under contract number ED05CO0039. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government. Additional information about participation in the Web Content Accessibility Guidelines Working Group (WCAG WG) can be found on the Working Group home page. Other previously active WCAG WG participants and other contributors to WCAG 2.0. C Link Checker. Unicorn - World Wide Web Consortium's Unified Validator. Web Accessibility National Transition Strategy - Australian Govt adoption/implementation of WCAG 2.0.

The Australian Government’s adoption and implementation of Web Content Accessibility Guidelines version 2.0 (WCAG 2.0) Foreword The Web Accessibility National Transition Strategy sets a course for improved web services, paving the way for a more accessible and usable web environment that will more fully engage with, and allow participation from, all people within our society. Accessibility has been a government priority for a number of years. With the release of the Web Content Accessibility Guidelines version 2.0 (WCAG 2.0), developed by the World Wide Web Consortium (W3C), the Australian Government is poised to improve the provision of information and services online. WCAG 2.0 sets an improved level of accessibility, to cater to the needs of a constantly evolving and increasingly dynamic web environment. Indeed, the implementation of W3C guidelines for Australian Government websites is not new; WCAG is the internationally recognised benchmark for website accessibility.

Full Publication. QuirksMode - for all your browser quirks. World Wide Web Consortium - Web Standards. Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) Abstract This technical report describes the similarities and differences between the requirements in Web Content Accessibility Guidelines (WCAG) and Mobile Web Best Practices 1.0 (MWBP). Introductory information and links to related documents are in Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices. Status of This Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. This document was developed jointly by the Mobile Web Best Practices Working Group of the Mobile Web Initiative (MWI) and the Education & Outreach Working Group (EOWG) of the Web Accessibility Initiative (WAI).

The Working Groups believe this document is complete and do not anticipate any substantive changes. Please send comments on this document to public-bpwg-comments@w3.org (with public archive) by 16 June 2009. Audience Introduction Priorities and Levels [WAI/Mobile] Language tags in HTML and XML. Intended audience: XHTML/HTML coders (using editors or scripting), script developers (PHP, JSP, etc.), schema developers (DTDs, XML Schema, RelaxNG, etc.), XSLT developers, Web project managers, standards implementers, and anyone who needs an overview of how language tags are constructed using BCP47.

Updated Overview Terminology In this article we refer to the value of a language attribute such as fr-CA as a language tag. Language tags are used to indicate the language of text or other items in HTML and XML documents. In both cases, language information is inherited by elements inside the one where the declaration was made, unless one of those elements declares a different language (in the same way). RFCs are what the IETF calls its specifications. Language tag syntax is defined by the IETF's BCP 47. You used to find subtags by consulting the lists of codes in various ISO standards, but now you can find all subtags in the IANA Language Subtag Registry.

Note! Examples: The script subtag. XML Schema validator.