Accessibility Guidelines

The W3C is inviting people to submit ideas, suggestions or comments to a (publically-archived) mailing list. In addition, code can be contributed directly on Github. The tutorials on the Web Accessibility Tutorials page will provide guidance on creating websites that meet WCAG 2.0 standards. They provide assistance to people in a variety of roles:

  • Developers: boiler plate solution for many common issues
  • Designers: creating elements and composites that lend themselves to accessible code
  • Trainers: access to compelling examples to aid in accessible web design education
  • Content Authors: concepts and techniques for creating accessible content
  • Project Managers: principle for planning accessible websites.

While additional tutorials are coming, current tutorials cover the following topics:

  • Images
  • Tables
  • Forms
  • Sliders/Carousels

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 Working Group Notes) are updated periodically to reflect current practices and technologies. Previously they were updated about once a year. The WCAG Working Group now plans to update them more frequently.

The existing Techniques and Understanding documents remain in place as W3C Notes while these separate draft updates are under review and the WCAG Working Group addresses comments.

The following draft updates are available for review as Editors' Drafts:

If you are interested in actively contributing to the development of additional WCAG 2.0 techniques and support material through the WCAG Working Group, please see: Participating in WAI and contact Michael Cooper.

The website for Safeway’s grocery delivery will undergo accessibility and usability improvements. They will use the Web Content Accessibility Guidelines, WCAG 2.0 Level AA as the standard for this effort.

Safeway worked on this initiative in structured negotiations with individual customers with visual impairments in California and Washington. The Law Offices of Lainey Feingold and Linda Dardarian of the Oakland, California civil rights firm Goldstein, Borgen, Dardarian & Ho represented the Safeway shoppers.

Authoring Tool Accessibility Guidelines Working Group (AUWG) is inviting developers of authoring tools who would be interested in sharing their experience implementing the Authoring Tool Accessibility Guidelines (ATAG) 2.0 and commenting on a Working Draft of the Note Implementing ATAG 2.0.

The ATAG defines how authoring tools should help developers looking to produce web content that conforms to the Web Content Accessibility Guidelines (WCAG) 2.0. It also defines how to produce authoring tools that are accessible, so that people with disabilities can use them effectively.

Authoring tools include:

  • Content Management Systems (CMA)
  • Learning Management Systems (LMS)
  • HTML editors
  • Blogs
  • Wikis
  • Social media
  • Development environments

Developers interested in participating can contact AUWG by December 7th, 2013

""
As Americans continue to rely on the web to perform everyday functions like shopping, banking and travel, web accessibility rises to the surface as a growing concern. In a major effort to make online communications accessible, DOT has implemented new rules as part of their continuing implementation of the Air Carrier Access Act of 1986.

On November 19 and 20 in Pune India the state Directorate of Information Technology (DIT), in association with Mahaonline Limited (MoL) will hold a workshop on eAccessibility. The DIT is inviting developer communities and software companies primarily working on government of Maharashtra websites that are high-traffic, high impact and citizen-centric. The goal is to teach them about web accessibility in an effort to make their websites and applications compliant with Web Content Accessibility Guide-lines (WCAG) 2.0 Level A.

Tracy Gray and Alise Brann are the authors of a new book, published by Brooks Publishing, on emerging trends in autism services.

Grey, leader of the Center for Technology Implementation at AIR, explains, “The convergence of mainstream technology and assistive technology is a critical milestone in promoting accessibility and independence for users with disabilities. We have been tracking trends in educational technology and assistive technology for the past decade and they indicate a shift toward portable, networked, customizable, and multitasking tech solutions with touch interfaces that mirror consumer technology.”

Read more on the book “Technology Tools for Students with Autism”

The World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) has published a document on Contacting Organization about Inaccessible Websites. The document gives three steps to report websites with accessibility issues:

  1. Identify key contacts
  2. Describe the problem
  3. Follow up as needed

The document stresses that website owners have many priorities for changes and improvements on their site and the more they hear about accessibility from users, the more likely it will become a priority. It further emphasizes considering what approach will get the best results stating that, “The tone of your emails, phone calls, and other communications will impact how people react and respond.” It suggests that assuming that the organization doesn’t know about the accessibility barriers on their website is the best first approach.

The Web Accessibility Initiative (WAI) has published the completed Guidance on Applying WCAG 2.0 to Non-Web Information and Communication Technologies (WCAG2ICT) as an informative W3C Working Group Note. The new guide addresses the interpretation and application of the WCAG 2.0 standards to non-web documents and software. WCAG2ICT was made possible through the collaborative effort to support harmonized accessibility solutions across a wide range of technologies.

WCAG2ICT is directed towards ICT managers, ICT developers, policy makers, and other wanting to understand how WCAG 2.0 can be applied to non-web document and software. WCAG2ICT specifically provides:

  • Overall context for applying WCAG 2.0 to non-web documents and software.
  • Guidance on applying the WCAG principles, guidelines, and Levels A and AA success criteria to non-web documents and software.
  • Key Terms related to applying WCAG 2.0 to non-web documents and software.
  • Comments on the definitions in the WCAG 2.0 Glossary.
  • Comments on conformance.
  • Background information on some topics.

WCAG2ICT also includes material from the WCAG 2.0 standard to provide context, along with specific guidance related to non-web ICT, formatted as follows:

  • WCAG 2.0 principles, guidelines, and success criteria — the exact text from the WCAG 2.0 standard. These are visually styled in pale yellow boxes and usually prefaced with "Principle...", "From Guideline...", or "From Success Criterion…"
  • Excerpted text from the "Intent" sections of Understanding WCAG 2.0, an informative supporting document. These are visually styled in pale yellow boxes and prefaced with "Intent from Understanding Success Criterion..."
  • Guidance on applying each success criteria to non-web documents and software. These are visually styled in pale blue boxes with a heading on a dark blue background that starts with "Additional Guidance..."

More details on the WCAG2ICT can be found in the WCAG2ICT overview on the W3C website.

Pages

Subscribe to RSS - Accessibility Guidelines