WCAG 2.2 (Accessibility) roles responsibility table

Principle

Guideline

Success criteria no.

Level

From ver.

Success criteria name

UX

UI

Dev

PTE

Perceivable

1.1 - Text Alternatives
_{Provide text alternatives for any non-text content}

1.1.1

A

2.0

Non-text content

• _{Images, image buttons, and image map hot spots have appropriate, equivalent alternative text.}

• _{Images that do not convey content, are decorative, or contain content that is already conveyed in text are given empty alternative text (alt="") or implemented as CSS backgrounds. All linked images have descriptive alternative text.}

• _{Equivalent alternatives to complex images are provided in context or on a separate linked page.}

• _{Form buttons have a descriptive value.}

• _{Inputs have associated text labels.}

• _{Embedded multimedia is identified via accessible text.}

• _{Frames and iframes are appropriately titled.}

No

No

Yes

Yes

Perceivable

1.2 - Time-based Media
_{Provide alternatives for time-based media.}

1.2.1

A

2.0

Audio-only and Video-only (Prerecorded)

• _{A descriptive transcript of relevant content is provided for non-live audio-only (audio podcasts, MP3 files, etc.).}

• _{A descriptive transcript or audio description of relevant content is provided for non-live video-only, unless the video is decorative.}

No

No

Yes

No

Perceivable

1.2 - Time-based Media
_{Provide alternatives for time-based media.}

1.2.2

A

2.0

Captions (prerecorded)
_{Synchronized captions are provided for non-live video (YouTube videos, etc.).}

No

No

Yes

No

Perceivable

1.2 - Time-based Media
_{Provide alternatives for time-based media.}

1.2.3

A

2.0

Audio Description or Media Alternative (Prerecorded)
_{A descriptive transcript or audio description is provided for non-live video.
NOTE: Only required if there is relevant visual content that is not presented in the audio.}

No

No

Yes

Yes

Perceivable

1.2 - Time-based Media
_{Provide alternatives for time-based media.}

1.2.4

AA

2.0

Captions (Live)
_{Synchronized captions are provided for live media that contains audio (audio-only broadcasts, web casts, video conferences, etc.)}

No

No

Yes

No

Perceivable

1.2 - Time-based Media
_{Provide alternatives for time-based media.}

1.2.5

AA

2.0

Audio Description (Prerecorded)
_{A descriptive transcript or audio description is provided for non-live video.
NOTE: Only required if there is relevant visual content that is not presented in the audio.}

No

No

Yes

No

Perceivable

1.3 - Adaptable
_{Create content that can be presented in different ways (for example simpler layout) without losing information or structure.}

1.3.1

A

2.0

Info and Relationships

• _{Semantic markup is appropriately used to designate headings, regions/landmarks, lists, emphasized or special text, etc.}

• _{Tables are used for tabular data and data cells are associated with their headers. Data table captions, if present, are associated to data tables.}

• _{Text labels are associated with form inputs. Related form controls are grouped with fieldset/legend. ARIA labelling may be used when standard HTML is insufficient.}

No

No

Yes

No

Perceivable

1.3 - Adaptable
_{Create content that can be presented in different ways (for example simpler layout) without losing information or structure.}

1.3.2

A

2.0

Miningful sequence
_{The reading and navigation order (determined by code order) is logical and intuitive.}

No

No

Yes

No

Perceivable

1.3 - Adaptable
_{Create content that can be presented in different ways (for example simpler layout) without losing information or structure.}

1.3.3

A

2.0

Sensory Characteristics

• _{Instructions do not rely upon shape, size, or visual location (e.g., "Click the square icon to continue" or "Instructions are in the right-hand column").}

• _{Instructions do not rely upon sound (e.g., "A beeping sound indicates you may continue.").}

No

No

No

Yes

Perceivable

1.3 - Adaptable
_{Create content that can be presented in different ways (for example simpler layout) without losing information or structure.}

1.3.4

AA

2.1

Orientation
_{Orientation of web content is not restricted to only portrait or landscape, unless a specific orientation is necessary.}

Yes

No

Yes

No

Perceivable

1.3 - Adaptable
_{Create content that can be presented in different ways (for example simpler layout) without losing information or structure.}

1.3.5

AA

2.1

Identify Input Purpose
_{Input fields that collect certain types of user information have an appropriate autocomplete attribute defined.}

No

No

Yes

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.1

A

2.0

Use of color

• _{Color is not used as the sole method of conveying content or distinguishing visual elements.}

Open

• _{Color alone is not used to distinguish links from surrounding text unless the contrast ratio between the link and the surrounding text is at least 3:1 and an additional distinction (e.g., it becomes underlined) is provided when the link is hovered over and receives keyboard focus. (}WebAIM: Contrast Checker ).

Open

Open

Yes

Yes

No

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.2

A

2.0

Audio Control
_{A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.}

Yes

No

No

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.3

AA

2.0

Contrast

• _{Text and images of text have a contrast ratio of at least 4.5:1.}

• _{Large text - at least 18 point (typically 24px) or 14 point (typically 18.66px) and bold - has a contrast ratio of at least 3:1. (}WebAIM: Contrast Checker ).

No

Yes

No

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.4

AA

2.0

Resize text
_{The page is readable and functional when the page is zoomed to 200%.
NOTE: 1.4.10 (below) introduces additional requirements for zoomed content.}

No

No

Yes

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.5

AA

2.0

Images of text
_{If the same visual presentation can be made using text alone, an image is not used to present that text.}

No

Yes

No

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.10

AA

2.1

Reflow

• _{No loss of content or functionality occurs and horizontal scrolling is avoided when content is presented at a width of 320 pixels. This requires responsive design for most web sites. This is best tested by setting the browser window to 1280 pixels wide and then zooming the page content to 400%.}

• _{Content that requires horizontal scrolling, such as data tables, complex images (such as maps and charts), toolbars, etc. are exempted.}

Yes

No

Yes

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.11

AA

2.1

Non-text contrast

• _{A contrast ratio of at least 3:1 is present for differentiating graphical objects (such as icons and components of charts or graphs) and author-customized interface components (such as buttons, form controls, and focus indicators/outlines).}

• _{At least 3:1 contrast is maintained in the various states (focus, hover, active, etc.) of author-customized interactive components. (}WebAIM: Contrast Checker ).

No

Yes

No

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.12

AA

2.1

Text Spacing

• _{No loss of content or functionality occurs when the user adapts paragraph spacing to 2 times the font size, text line height/spacing to 1.5 times the font size, word spacing to .16 times the font size, and letter spacing to .12 times the font size.}

• _{This is best supported by avoiding pixel height definitions for elements that contain text.}

No

No

Yes

No

Perceivable

1.4 - Distinguishable
_{Make it easier for users to see and hear content including separating foreground from background.}

1.4.13

AA

2.1

Content on Hover or Focus
_{When additional content is presented on hover or keyboard focus:}

• _{The newly revealed content can be dismissed (generally via the Esc key) without moving the pointer or keyboard focus, unless the content presents an input error or does not obscure or interfere with other page content.}

• _{The pointer can be moved to the new content without the content disappearing.}

• _{The new content must remain visible until the pointer or keyboard focus is moved away from the triggering control, the new content is dismissed, or the new content is no longer relevant.}

Yes

No

Yes

No

Operable

2.1 - Keyboard Accessible
_{Make all functionality available from a keyboard.}

2.1.1

A

2.0

Keyboard

• _{All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).}

• _{Page-specified shortcut keys and access keys do not conflict with existing browser and screen reader shortcuts.}

Yes

No

Yes

No

Operable

2.1 - Keyboard Accessible
_{Make all functionality available from a keyboard.}

2.1.2

A

2.0

No Keyboard trap
_{Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.}

No

No

Yes

No

Operable

2.1 - Keyboard Accessible
_{Make all functionality available from a keyboard.}

2.1.4

A

2.1

Character Key Shortcuts
_{If a keyboard shortcut uses printable character keys, then the user must be able to disable the key command, change the defined key to a non-printable key (Ctrl, Alt, etc.), or only activate the shortcut when an associated interface component or button is focused.}

Yes

No

Yes

No

Operable

2.2 - Enough Time
_{Provide users enough time to read and use content.}

2.2.1

A

2.0

Timing Adjustable
_{If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.}

Yes

No

No

No

Operable

2.2 - Enough Time
_{Provide users enough time to read and use content.}

2.2.2

A

2.0

Pause, Stop, Hide

• _{Automatically moving, blinking, or scrolling content (such as carousels, marquees, or animations) that lasts longer than 5 seconds can be paused, stopped, or hidden by the user.}

• _{Automatically updating content (e.g., a dynamically-updating news ticker, chat messages, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates.}

Yes

No

No

No

Operable

2.3 - Seizures and Physical Reactions
_{Do not design content in a way that is known to cause seizures.}

2.3.1

A

2.0

Three Flashes or Below Threshold
_{No page content flashes more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red. (See general flash and red flash thresholds:} https://www.w3.org/TR/WCAG22/#dfn-general-flash-and-red-flash-thresholds _).

Yes

Yes

No

No

Operable

2.4 - Navigable
_{Provide ways to help users navigate, find content, and determine where they are.}

2.4.1

A

2.0

Bypass Blocks

• _{A link is provided to skip navigation and other page elements that are repeated across web pages.}

• _{While proper use of headings or regions/landmarks is sufficient to meet this success criterion, because keyboard navigation by headings or regions is not supported in most browsers, WebAIM recommends a "skip" link in addition to headings and regions.}

Yes

No

Yes

No

Operable

2.4 - Navigable
_{Provide ways to help users navigate, find content, and determine where they are.}

2.4.2

A

2.0

Page Titled
_{The web page has a descriptive and informative page title.}

No

No

Yes

No

Operable

2.4 - Navigable
_{Provide ways to help users navigate, find content, and determine where they are.}

2.4.3

A

2.0

Focus Order
_{The navigation order of links, form controls, etc. is logical and intuitive.}

Yes

No

No

No

Operable

2.4 - Navigable
_{Provide ways to help users navigate, find content, and determine where they are.}

2.4.4

A

2.0

Link Purpose (In Context)

_{The purpose of each link (or image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding text, list item, previous heading, or table headers).}

Yes

No

Yes

No

Operable

2.4 - Navigable
_{Provide ways to help users navigate, find content, and determine where they are.}

2.4.5

AA

2.0

Multiple Ways
_{Multiple ways are available to find other web pages on the site - at least two of: a list of related pages, table of contents, site map, site search, or list of all available web pages.}

Yes

No

No

No

Operable

2.4 - Navigable
_{Provide ways to help users navigate, find content, and determine where they are.}

2.4.6

AA

2.0

Headings and Labels
_{Page headings and labels for form and interactive controls are informative. Avoid duplicating heading and label text unless the structure provides adequate differentiation between them.}

Yes

No

No

No

Operable

2.4 - Navigable
_{Provide ways to help users navigate, find content, and determine where they are.}

2.4.7

AA

2.0

Focus Visible
_{There is a visible indicator for page elements when they receive keyboard focus.}

Open

Open

No

Yes

No

No

Operable 

2.4 - Navigable
_{Provide ways to help users navigate, find content, and determine where they are.}

2.4.11 

AA

2.2

Focus not obscured (minimun)
_{Don't obscure the element that has focus (eg with sticky headers/footers or modals).
Ensure when an item gets keyboard focus, it is at least partially visible.}

Open

Yes

No

No

No

Operable

2.5 - Input Modalities
_{Make it easier for users to operate functionality through various inputs beyond keyboard.}

2.5.1

A

2.1

Pointer Gestures
_{If multipoint or path-based gestures (such as pinching, swiping, or dragging across the screen) are not essential to the functionality, then the functionality can also be performed with a single point activation (such as activating a button).}

Yes

No

No

No

Operable

2.5 - Input Modalities
_{Make it easier for users to operate functionality through various inputs beyond keyboard.}

2.5.2

A

2.1

Pointer Cancellation
_{To help avoid inadvertent activation of controls, avoid non-essential down-event (e.g., onmousedown) activation when clicking, tapping, or long pressing the screen. For complex interactions (such as drag and drop), onmousedown can be used if an associated onmouseup (or similar) event can be aborted or reversed.}

No

No

Yes

No

Operable

2.5 - Input Modalities
_{Make it easier for users to operate functionality through various inputs beyond keyboard.}

2.5.3

A

2.1

Label in Name
_{If an interface component (link, button, etc.) presents text (or images of text), the accessible name (label, alternative text, aria-label, etc.) for that component must include the visible text.}

No

No

Yes

No

Operable

2.5 - Input Modalities
_{Make it easier for users to operate functionality through various inputs beyond keyboard.}

2.5.4

A