User Tools

Site Tools


accessibility:requirements

Accessibility Requirements

The Web Content Accessibility Guidelines(WCAG) are a set of international standards for accessible web interfaces. The Authoring Tool Accessibility Guidelines (ATAG) apply to software used to produce web content, like content management systems and WYSIWYG editors.

Generally, laws require web-based software to meet WCAG level AA standards for the most recent version of the guidelines, currently version 2.1 (released in 2018). Level AAA applies only to specific types of content in certain contexts, like long documents. https://www.w3.org/TR/WCAG21/#cc1:The standard itself states, “It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content.”

Some procurement standards may also specify ATAG compliance.

Note that https://www.w3.org/TR/coga-usable/:the guidelines on cognitive accessibility are still in draft, and are due to become part of WCAG in the next major release.

Understanding WCAG and ATAG

The full WCAG guidelines are very detailed and technical; they were written to be used by both browser vendors and legislative groups. If you are new to accessibility, it's better to start with a more human-readable checklist:

If you want something more formal, the Section 508 Trusted Tester Conformance Test Process might be right for you.

While ATAG may still be included in your local laws on accessibility, its guidelines are slowly being incorporated into WCAG. (When ATAG and WCAG were originally written, content management systems were exclusively for enterprise work, and it made sense to have a separate set of guidelines for editing interfaces.) Generally speaking, WCAG is the standard to pay attention to.

Always use the most recent version of WCAG, regardless of the version that is specified in your local laws. Legislation is often several years behind reality, and WCAG 2.x versions are written to be backward compatible.

The four principles of accessible web interfaces, POUR, map to the four major sections of WCAG numbering:

“Some people think about Perceivable = visual design, Operable = interaction design, Understandable = content design, Robust=largely dev. This is very rough mapping, though it might help with how you think about it.” – Jennifer X. Zhang, Microsoft

accessibility/requirements.txt · Last modified: 2023/07/10 15:41 by scl

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.