WCAG 2.2 AA Guidelines

1.1 Text Alternatives

All non-text content presented to the user has a text alternative that serves the equivalent purpose, except for controls, input, time-based media, tests, sensory experiences, CAPTCHA, and decoration.

1.2 Time-based Media

For prerecorded audio-only and prerecorded video-only media, an alternative is provided that presents equivalent information.

1.2 Time-based Media

Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

1.2 Time-based Media

An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media.

1.2 Time-based Media

Captions are provided for all live audio content in synchronized media.

1.2 Time-based Media

Audio description is provided for all prerecorded video content in synchronized media.

1.3 Adaptable

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

1.3 Adaptable

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

1.3 Adaptable

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.

1.3 Adaptable

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific orientation is essential.

1.3 Adaptable

The purpose of each input field collecting information about the user can be programmatically determined when the input field serves a common purpose identified in the specification.

1.4 Distinguishable

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

1.4 Distinguishable

If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume.

1.4 Distinguishable

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large text (3:1), incidental text, and logotypes.

1.4 Distinguishable

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

1.4 Distinguishable

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text, except when customizable or essential.

1.4 Distinguishable

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions, at a width equivalent to 320 CSS pixels and a height equivalent to 256 CSS pixels.

1.4 Distinguishable

The visual presentation of user interface components and graphical objects has a contrast ratio of at least 3:1 against adjacent colors.

1.4 Distinguishable

No loss of content or functionality occurs when users override text spacing properties: line height to at least 1.5 times the font size, paragraph spacing to at least 2 times the font size, letter spacing to at least 0.12 times the font size, and word spacing to at least 0.16 times the font size.

1.4 Distinguishable

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the additional content is dismissible, hoverable, and persistent.

2.1 Keyboard Accessible

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement.

2.1 Keyboard Accessible

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and if it requires more than unmodified arrow or tab keys, the user is advised of the method.

2.1 Keyboard Accessible

If a keyboard shortcut is implemented using only letter, punctuation, number, or symbol characters, then the shortcut can be turned off, remapped, or is only active when the relevant interface component has focus.

2.2 Enough Time

For each time limit that is set by the content, the user can turn off, adjust, or extend the time limit, unless the time limit is essential, a real-time event, or longer than 20 hours.

2.2 Enough Time

For moving, blinking, scrolling, or auto-updating information, the user can pause, stop, or hide it, unless it is essential to an activity.

2.3 Seizures and Physical Reactions

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

2.4 Navigable

A mechanism is available to bypass blocks of content that are repeated on multiple web pages.

2.4 Navigable

Web pages have titles that describe topic or purpose.

2.4 Navigable

If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

2.4 Navigable

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

2.4 Navigable

More than one way is available to locate a web page within a set of web pages, except where the page is the result of, or a step in, a process.

2.4 Navigable

Headings and labels describe topic or purpose.

2.4 Navigable

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

2.4 Navigable

When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

2.5 Input Modalities

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

2.5 Input Modalities

For functionality that can be operated using a single pointer, at least one of the following is true: no down-event, abort or undo, up reversal, or essential.

2.5 Input Modalities

For user interface components with labels that include text or images of text, the accessible name contains the text that is presented visually.

2.5 Input Modalities

Functionality that can be operated by device motion or user motion can also be operated by user interface components, and responding to the motion can be disabled to prevent accidental actuation.

2.5 Input Modalities

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent.

2.5 Input Modalities

The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where an equivalent control meets the size, the target is inline, the user agent determines the size, or the presentation is essential.

3.1 Readable

The default human language of each web page can be programmatically determined.

3.1 Readable

The human language of each passage or phrase in the content can be programmatically determined, except for proper names, technical terms, words of indeterminate language, and words that have become part of the surrounding text.

3.2 Predictable

When any user interface component receives focus, it does not initiate a change of context.

3.2 Predictable

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

3.2 Predictable

Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

3.2 Predictable

Components that have the same functionality within a set of web pages are identified consistently.

3.2 Predictable

If a web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple web pages within a set of web pages, they occur in the same relative order: human contact details, human contact mechanism, self-help option, a fully automated contact mechanism.

3.3 Input Assistance

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

3.3 Input Assistance

Labels or instructions are provided when content requires user input.

3.3 Input Assistance

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

3.3 Input Assistance

For web pages that cause legal commitments or financial transactions, that modify or delete user-controllable data, or that submit user test responses, submissions are reversible, checked, or confirmed.

3.3 Input Assistance

Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated or available for the user to select, unless re-entering the information is essential or required for security.

3.3 Input Assistance

A cognitive function test is not required for any step in an authentication process unless that step provides at least one alternative that does not rely on a cognitive function test, or the test recognizes objects or user-supplied content.

4.1 Compatible

For all user interface components, the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

4.1 Compatible

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.