Web Content Accessibility Guidelines 1.0
W3C Recommendation 5-May-1999 This version: (plain text, PostScript, PDF, gzip tar file of HTML, zip archive of HTML) Latest version: Previous version: Editors: Wendy Chisholm, Trace R & D Center, University of Wisconsin -- Madison Gregg Vanderheiden, Trace R & D Center, University of Wisconsin -- Madison Ian Jacobs, W3C Copyright © 1999 W3C (MIT, INRIA, Keio), All Rights Reserved. Abstract These guidelines explain how to make Web content accessible to people with disabilities. This is a reference document for accessibility principles and design ideas. This document is meant to be stable and therefore does not provide specific information about browser support for different technologies as that information changes rapidly. This document includes an appendix that organizes all of the checkpoints by topic and priority. Status of this document 1. 2. 3. 4. 5. Note.
Understanding Conformance | Understanding WCAG 2.0
All WCAG 2.0 Success Criteria are written as testable criteria for objectively determining if content satisfies them. Testing the Success Criteria would involve a combination of automated testing and human evaluation. The content should be tested by those who understand how people with different types of disabilities use the Web. Testing and testable in the context refer to functional testing, that is verifying that the content functions as expected, or in this case, that it satisfies the Success Criteria. What does conformance mean? Conformance to a standard means that you meet or satisfy the 'requirements' of the standard. Note: This means that if there is no content to which a success criterion applies, the success criterion is satisfied. Most standards only have one level of conformance. Understanding Conformance Requirements There are five requirements that must be met in order for content to be classified as 'conforming' to WCAG 2.0. Understanding Requirement 1 1. 2. 3. 5.
WCAG 2.0 at a Glance
WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities Site Navigation W3C Home Web Accessibility Initiative (WAI) Home Discover new resources for people with disabilities, policy makers, managers, and you! Translations WCAG 2 at a Glance This page provides a paraphrased summary of Web Content Accessibility Guidelines (WCAG) 2.0. Please see the following key resources for learning and using WCAG 2.0: Perceivable Provide text alternatives for non-text content. Operable Make all functionality available from a keyboard. Understandable Robust Maximize compatibility with current and future user tools. Print Version This page is formatted for printing (without the navigation) as PDF files for A4 and 8.5" x 11" paper: Document Information Status: Updated 6 December 2011 (preface wording updated 22 February 2012, first published July 2008) Editors: Shawn Lawton Henry and Wayne Dick. Copyright © 2016 W3C ® (MIT, ERCIM, Keio, Beihang) Usage policies apply.
WCAG Overview
Introduction Web Content Accessibility Guidelines (WCAG) is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a single shared standard for web content accessibility that meets the needs of individuals, organizations, and governments internationally. The WCAG documents explain how to make web content more accessible to people with disabilities. Web "content" generally refers to the information in a web page or web application, including: natural information such as text, images, and sounds code or markup that defines structure, presentation, etc. Who WCAG is for WCAG is primarily intended for: Web content developers (page authors, site designers, etc.) Related resources are intended to meet the needs of many different people, including policy makers, managers, researchers, and others. WCAG is a technical standard, not an introduction to accessibility. What is in WCAG 2.0 Technical document format Who develops WCAG
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
Screen Reader-Accessible Dropdown Menus | Tessa Explains How to Do Things
I’m currently working a contract as a web designer and developer for a university, where web accessibility is vitally important for all web pages. I used to think I had a pretty good idea of how to make a web site accessible, until I started actually testing sites with a screen reader (JAWS). It’s not easy to navigate the web using your keyboard and your ears, and most web sites make the task unnecessarily complicated and frustrating. The easiest way to make your website accessible to screen reader users is by simply following best practices for semantic markup, but even this will only take you part of the way. The university I work for uses drop down menus on almost every page to display important information, but when I tested many of these pages using JAWS (the most popular screen reader), I found I couldn’t access any submenus, because they were hidden using visibility:hidden. Accessible Dropdowns The whole story: View Demo Step 1: Semantic HMTL Part 2: CSS Pretty simple, right? mmm...
