A Quick Guide to WCAG 2.1 quick-guide-to-wcag

Adobe Experience Manager (AEM) as a Cloud Service has been developed to maximize compliance with the Web Content Accessibility Guidelines.

The Web Content Accessibility Guidelines (WCAG) version 2.1 are a set of internationally recognized guidelines developed by the World Wide Web Consortium (W3C) under their Web Accessibility Initiative (WAI).

WCAG 2.1 consists of a set of technology independent guidelines and success criteria to help make web content accessible to, and usable by, persons with disabilities. They provide advice to web content authors, designers and developers on ensuring that the resources they produce are as accessible as possible to as many people as possible, regardless of any disability they have; for example, visual impairment, hearing loss, learning difficulties, age related limitations, amongst others.

For example, describing an image (or any other non-text content) by using the alt attribute in HTML greatly benefits people who are blind or partially sighted. The textual description in the alt attribute can either be converted into speech output or transmitted to electronic refreshable braille displays.

Also, WCAG 2.1 can result in advantages for other beneficiaries, including people who may be considered situationally disabled. People who, because of circumstances such as browsing technology, network connection speed or browsing environment, may experience barriers similar to people with disabilities.

Using Adobe Experience Manager, content authors and/or website owners can create web content that meets relevant WCAG 2.1 Level A and Level AA success criteria.

Therefore, understanding the aims of WCAG 2.1 and how the guidelines are structured is an important part of understanding web accessibility and how the guidelines can help in creating accessible web content.

The intention of WCAG 2.1 is to provide guidelines that:

These aims have significantly influenced the structure of WCAG 2.1.

Structure structure

WCAG 2.1 is structured in a way that introduces concepts of accessible web content creation in a progressively detailed manner. This may give the impression that WCAG 2.1 is a very complex set of interlinked documents, but the aim is to (progressively) provide more detailed information as and when authors need it - rather than providing it all in one very large document.

WCAG 2.1 consists of four key principles for accessible design, sometimes referred to by the acronym POUR. These are:

To elaborate:

Supporting Resources supporting-resources

In addition to the core WCAG 2.1 components of Principles, Guidelines and Success Criteria, there are a series of supporting documents. Some of them provide specific advice on how to meet aspects of the guidelines, others are more general references helping web authors, designers and developers of all abilities understand and use WCAG 2.1 as effectively as possible.

While WCAG 2.1 itself is a stable document, and will not change, most of these supporting resources are dynamic documents; they will change and grow over time, as new technologies emerge, and new examples are found of how web accessibility can be achieved.

WCAG 2.1 Resources wcag-resources

This list is not intended to be exhaustive, it provides an introduction to the resources available:

What is New in WCAG 2.1 what-is-new

The guidelines provide information about what is new in WCAG 2.1:

Techniques for WCAG 2.1 techniques-for-wcag

Techniques for WCAG 2.1 are available on the Techniques for WCAG 2.1 page.

Techniques form the level below success criteria in the WCAG 2.1 hierarchy. They are classed by WAI as informative, not normative. In other words, a specific technique does not have to be followed in order for a resource to conform with WCAG 2.1.

Because techniques are much more specific than success criteria, they usually refer to a particular technology or content type (for example, HTML, or video), or situation (for example, e-commerce or e-learning application). You can think of techniques as proven examples of how specific guidelines and success criteria can be met, so they are helpful aids to authors and developers working in particular contexts.

Techniques can be accessed:

Each technique has a unique number, which relates to its collection. For example, one of the ARIA techniques is Technique ARIA2: Identifying a required field with the aria-required property.

Techniques may be Sufficient, Advisory, or a Failure:

Details for techniques include a description, applicability, examples, resources for further information and details of how authors can test for successful application of the technique.

The list of techniques is not complete and WAI is constantly updating the list with new examples, reflecting developments in web technology, design approaches, and research findings. So it is well worth regularly checking the list of techniques for new additions.

Understanding WCAG 2.1 understanding-wcag

This refers to a series of documents, which provide advice helping readers to appreciate the purpose of specific guidelines and success criteria. You can download an introduction, plus links to more detailed information.

Each individual guideline and success criterion also has its own ‘Understanding’ page, providing information on:

Each success criterion’s individual “understanding” page provides information on:

An example can be found at: Understanding Success Criterion 1.1.1 (“Non-text content”).

How to Meet WCAG 2.1 how-to-meet-wcag

The ‘How to Meet’ section is available on the How To Meet WCAG 2.1 page. This section provides an alternative presentation of WCAG, allowing readers to refine the content of the guidelines to those most relevant to their own interests and/or circumstances. Readers can filter the success criteria techniques they would like to view by specifying particular web content technologies such as Cascading Style Sheets or scripting, or specifying a particular priority level(s).

Without filtering, this resource provides all success criteria grouped by guideline. For each success criterion, the following is provided: