Web Content Accessibility Guidelines (WCAG) 2.1: Difference between revisions
From LINKS Community Center
Dinu (talk | contribs) No edit summary |
Dinu (talk | contribs) No edit summary |
||
(12 intermediate revisions by 3 users not shown) | |||
Line 3: | Line 3: | ||
|Language=English | |Language=English | ||
|Year Published=2018 | |Year Published=2018 | ||
|Status=Published | |Status=Published | ||
|Covers Thematic=Legal, | |Covers Thematic=Legal/Standards, Vulnerable groups | ||
| | |Audience Experience Level=Intermediate | ||
|Source Website=https://www.w3.org/TR/WCAG21/ | |||
|Synopsis=These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general | |||
The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy makers, purchasing agents, teachers, and students. | |||
In order to meet the varying needs of this audience, several '''layers of guidance''' are provided including overall principles, general guidelines, testable success criteria and a rich collection of sufficient techniques, advisory techniques, and documented common failures with examples, resource links and code. | |||
*'''Principles''' | |||
** At the top are four principles that provide the foundation for Web accessibility: | |||
***perceivable | |||
***operable | |||
***understandable, | |||
***robust. | |||
*'''Guidelines''' | |||
**Under the principles are guidelines. | |||
**The 13 guidelines provide the basic goals that authors should work toward in order to make content more accessible to users with different disabilities. | |||
**The guidelines are not testable, but provide the framework and overall objectives to help authors understand the success criteria and better implement the techniques. | |||
*'''Success Criteria''' | |||
**For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements. | |||
**In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest). | |||
**Additional information on WCAG levels can be found in Understanding Levels of Conformance. | |||
*'''Sufficient and Advisory Techniques''' | |||
**For each of the guidelines and success criteria in the WCAG 2.0 document itself, the working group has also documented a wide variety of techniques. | |||
***The techniques are informative and fall into two categories: | |||
***those that are sufficient for meeting the success criteria and | |||
***those that are advisory. | |||
**The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines. | |||
**Some advisory techniques address accessibility barriers that are not covered by the testable success criteria. | |||
***Where common failures are known, these are also documented | |||
|Is Archived=No | |Is Archived=No | ||
|Disaster Management Phase=Before, During, After | |||
}} |
Latest revision as of 14:13, 14 August 2023
Created: 30 August 2022
Last edited: 14 August 2023
Last edited: 14 August 2023
Quick Facts
Publishing Organisation:
W3CYear:
2018Languages:
EnglishStatus:
PublishedCovers Thematic
Target audience
Audience experience level
Disaster Management Phase
Synopsis
These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy makers, purchasing agents, teachers, and students.
In order to meet the varying needs of this audience, several layers of guidance are provided including overall principles, general guidelines, testable success criteria and a rich collection of sufficient techniques, advisory techniques, and documented common failures with examples, resource links and code.
- Principles
- At the top are four principles that provide the foundation for Web accessibility:
- perceivable
- operable
- understandable,
- robust.
- At the top are four principles that provide the foundation for Web accessibility:
- Guidelines
- Under the principles are guidelines.
- The 13 guidelines provide the basic goals that authors should work toward in order to make content more accessible to users with different disabilities.
- The guidelines are not testable, but provide the framework and overall objectives to help authors understand the success criteria and better implement the techniques.
- Success Criteria
- For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements.
- In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest).
- Additional information on WCAG levels can be found in Understanding Levels of Conformance.
- Sufficient and Advisory Techniques
- For each of the guidelines and success criteria in the WCAG 2.0 document itself, the working group has also documented a wide variety of techniques.
- The techniques are informative and fall into two categories:
- those that are sufficient for meeting the success criteria and
- those that are advisory.
- The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines.
- Some advisory techniques address accessibility barriers that are not covered by the testable success criteria.
- Where common failures are known, these are also documented
- For each of the guidelines and success criteria in the WCAG 2.0 document itself, the working group has also documented a wide variety of techniques.
Linked to
- Technologies
- Use Cases
-
None. See all Technologies.
- None. See all Use Cases.