Data


Principles
0
Principle
Description
1
1 Perceivable πŸ”
Web content is made available to the senses - sight, hearing, and/or touch
2
2 Operable πŸ”§
Interface forms, controls, and navigation are operable
3
3 Understandable πŸ—£οΈ
Information and the operation of user interface must be understandable.
4
4 Robust πŸ“–
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies
There are no rows in this table

Level
0
Level
1
A
2
AA
3
AAA
There are no rows in this table

Guidelines
0
Principle
Guideline
Description
1 Perceivable πŸ”
4
1.1 Text Alternatives
Provide text alternatives for any non-text content
1.2 Time-based Media
Provide alternatives for time-based media. NOTE: If the audio or video is designated as an alternative to web content (e.g., an audio or sign language version of a web page, for example), then the web content itself serves as the alternative.
1.3 Adaptable
Create content that can be presented in different ways (for example simpler layout) without losing information or structure
1.4 Distinguishable
Make it easier for users to see and hear content including separating foreground from background
2 Operable πŸ”§
5
2.1 Keyboard Accessible
Make all functionality available from a keyboard
2.2 Enough Time
Provide users enough time to read and use content
2.3 Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
3 Understandable πŸ—£οΈ
3
3.1 Readable
Make text content readable and understandable.
3.2 Predictable
Make web pages appear and operate in predictable ways.
3.3 Input Assistance
Help users avoid and correct mistakes.
4 Robust πŸ“–
1
4.1 Compatible
Maximize Compatibility with current and future user agents, including assistive technologies.

Conformance Levels
0
Level
Description
1
Supports
The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
2
Partially supports
Some functionality of the product does not meet the criterion.
3
Does not support
The majority of product functionality does not meet the criterion.
4
Not applicable
The criterion is not relevant to the product.
5
Not evaluated
The product has not been evaluated against the criterion. This can only be used in WCAG 2.0 Level AAA.
There are no rows in this table



Checklist
5
Principle
Level
Guideline
Success Criteria Lookup
Recommendation
Conformance
Auditor
1
1 Perceivable πŸ”
A
1.1 Text Alternatives
1.1.1 Non-text Content
Images, form image buttons, and image map hot spots have appropriate, equivalent
.
​
​
2
1 Perceivable πŸ”
A
1.1 Text Alternatives
1.1.1 Non-text Content
Images that do not convey content, are decorative, or contain content that is already conveyed in text are given null alt text (alt="") or implemented as CSS backgrounds. All linked images have descriptive alternative text.
​
​
3
1 Perceivable πŸ”
A
1.1 Text Alternatives
1.1.1 Non-text Content
Equivalent alternatives to complex images are provided in context or on a separate linked page.
​
​
4
1 Perceivable πŸ”
A
1.1 Text Alternatives
1.1.1 Non-text Content
Form buttons have a descriptive value.
​
​
5
1 Perceivable πŸ”
A
1.1 Text Alternatives
1.1.1 Non-text Content
Form inputs have associated
.
​
​
6
1 Perceivable πŸ”
A
1.1 Text Alternatives
1.1.1 Non-text Content
Embedded multimedia is identified via accessible text.
​
​
7
1 Perceivable πŸ”
A
1.1 Text Alternatives
1.1.1 Non-text Content
Frames and iFrames are appropriately
.
​
​
8
1 Perceivable πŸ”
A
1.2 Time-based Media
1.2.1 Prerecorded Audio-only and Video-only
A
of relevant content is provided for non-live audio-only (audio podcasts, MP3 files, etc.).
​
​
9
1 Perceivable πŸ”
A
1.2 Time-based Media
1.2.1 Prerecorded Audio-only and Video-only
A transcript or
of relevant content is provided for non-live video-only, unless the video is decorative.
​
​
10
1 Perceivable πŸ”
A
1.2 Time-based Media
1.2.2 Captions (prerecorded)
are provided for non-live video (YouTube videos, etc.).
​
​
11
1 Perceivable πŸ”
A
1.2 Time-based Media
1.2.5 Audio Description (prerecorded)
A 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.)
​
​
12
1 Perceivable πŸ”
AA
1.2 Time-based Media
1.2.4 Captions (Live)
Synchronized captions are provided for live media that contains audio (audio-only broadcasts, web casts, video conferences, etc.)
​
​
13
1 Perceivable πŸ”
AA
1.2 Time-based Media
1.2.5 Audio Description (Prerecorded)
Audio descriptions are provided for non-live video. (NOTE: Only required if there is relevant visual content that is not presented in the audio. Also, while not required at Level AA, for optimal accessibility WebAIM recommends transcripts in addition to audio descriptions.)
​
​
14
1 Perceivable πŸ”
AAA
1.2 Time-based Media
1.2.6 Sign Language (Prerecorded)
A sign language video is provided for media that contains audio.
​
​
15
1 Perceivable πŸ”
AAA
1.2 Time-based Media
1.2.7 Extended Audio Description (Prerecorded)
When audio description cannot be added to video due to audio timing (e.g., insufficient pauses in the audio), an alternative version of the video with pauses that allow audio descriptions is provided.
​
​
16
1 Perceivable πŸ”
AAA
1.2 Time-based Media
1.2.8 Media Alternative (Prerecorded)
A transcript is provided for pre-recorded media that has a video track. For optimal accessibility, WebAIM strongly recommends transcripts for all multimedia.
​
​
17
1 Perceivable πŸ”
AAA
1.2 Time-based Media
1.2.9 Audio-only (Live)
A descriptive text transcript (e.g., the script of the live audio) is provided for live content that has audio.
​
​
18
1 Perceivable πŸ”
A
1.3 Adaptable
1.3.1 Info and Relationships
is used to designate headings (<h1>), regions/landmarks, lists (<ul>, <ol>, and <dl>), emphasized or special text (<strong>, <code>, <abbr>, <blockquote>, for example), etc. Semantic markup is used appropriately.
​
​
19
1 Perceivable πŸ”
A
1.3 Adaptable
1.3.1 Info and Relationships
are used for tabular data and data cells are associated with their headers. Data table captions, if present, are associated to data tables.
​
​
20
1 Perceivable πŸ”
A
1.3 Adaptable
1.3.1 Info and Relationships
are associated with form input elements. Related form elements are grouped with fieldset/legend. ARIA labelling may be used when standard HTML is insufficient.
​
​
21
1 Perceivable πŸ”
A
1.3 Adaptable
1.3.2 Meaningful Sequence
The
(determined by code order) is logical and intuitive.
​
​
22
1 Perceivable πŸ”
A
1.3 Adaptable
1.3.3 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").
​
​
23
1 Perceivable πŸ”
A
1.3 Adaptable
1.3.3 Sensory Characteristics
Instructions do not rely upon sound (e.g., "A beeping sound indicates you may continue.").
​
​
24
1 Perceivable πŸ”
AA
1.3 Adaptable
1.3.4 Orientation
Orientation of web content is not restricted to only portrait or landscape, unless a specific orientation is necessary.
​
​
25
1 Perceivable πŸ”
AA
1.3 Adaptable
1.3.5 Identify Input Purpose
Input fields that collect
have an appropriate autocomplete attribute defined.
​
​
26
1 Perceivable πŸ”
AAA
1.3 Adaptable
1.3.6 Identify Purpose
HTML5 regions or ARIA landmarks are used to identify page regions.
​
​
27
1 Perceivable πŸ”
AAA
1.3 Adaptable
1.3.6 Identify Purpose
ARIA is used, where appropriate, to enhance HTML semantics to better identify the purpose of interface components.
​
​
28
1 Perceivable πŸ”
A
1.4 Distinguishable
1.4.1 Use of Color
Color is not used as the sole method of conveying content or distinguishing visual elements.
​
​
29
1 Perceivable πŸ”
A
1.4 Distinguishable
1.4.1 Use of Color
Color alone is not used to distinguish
from surrounding text unless the
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 focus.
​
​
30
1 Perceivable πŸ”
A
1.4 Distinguishable
1.4.2 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.
​
​
31
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.3 Contrast (Minimum)
Text and images of text have a contrast ratio of at least 4.5:1.
​
​
32
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.3 Contrast (Minimum)
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.
​
​
33
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.4 Resize text
The page is readable and functional when the page is zoomed to 200%. NOTE: 1.4.10 introduces a much higher requirement for zoomed content.
​
​
34
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.9 Images of Text (No Exception)
If the same visual presentation can be made using text alone, an image is not used to present that text.
​
​
35
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.10 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%.
​
​
36
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.10 Reflow
Content that requires horizontal scrolling, such as data tables, complex images (such as maps and charts), toolbars, etc. are exempted.
​
​
37
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.11 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).
​
​
38
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.11 Non-text Contrast
At least 3:1 contrast must be provided in the various states (focus, hover, active, etc.) of author-customized interactive components.
​
​
39
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.12 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.
​
​
40
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.12 Text Spacing
This is best supported by avoiding pixel height definitions for elements that contain text.
​
​
41
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.13 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.
​
​
42
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.13 Content on Hover or Focus
When additional content is presented on hover or keyboard focus, the pointer can be moved to the new content without the content disappearing.
​
​
43
1 Perceivable πŸ”
AA
1.4 Distinguishable
1.4.13 Content on Hover or Focus
When additional content is presented on hover or keyboard focus, 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.
​
​
44
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.6 Contrast (Enhanced)
Text and images of text have a contrast ratio of at least 7:1.
​
​
45
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.6 Contrast (Enhanced)
Large text - at least 18 point (typically 24px) or 14 point (typically 18.66px) bold - has a contrast ratio of at least 4.5:1.
​
​
46
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.7 Low or No Background Audio
Audio with speech has no or very low background noise so the speech is easily distinguished.
​
​
47
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.8 Visual Presentation
Blocks of text over one sentence in length are no more than 80 characters wide.
​
​
48
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.8 Visual Presentation
Blocks of text over one sentence in length are NOT fully justified (aligned to both the left and the right margins).
​
​
49
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.8 Visual Presentation
Blocks of text over one sentence in length have adequate line spacing (at least 1/2 the height of the text) and paragraph spacing (1.5 times line spacing).
​
​
50
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.8 Visual Presentation
Blocks of text over one sentence in length have a specified foreground and background color. These can be applied to specific elements or to the entire page using CSS (and thus inherited by all other elements).
​
​
51
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.8 Visual Presentation
Blocks of text over one sentence in length do NOT require horizontal scrolling when the text size is doubled.
​
​
52
1 Perceivable πŸ”
AAA
1.4 Distinguishable
1.4.9 Images of Text (No Exception)
Text is used within an image only for decoration (image does not convey content) OR when the information cannot be presented with text alone.
​
​
53
2 Operable πŸ”§
A
2.1 Keyboard Accessible
2.1.1 Keyboard
All page functionality is available using the
, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).
​
​
54
2 Operable πŸ”§
A
2.1 Keyboard Accessible
2.1.1 Keyboard
Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.
​
​
55
2 Operable πŸ”§
A
2.1 Keyboard Accessible
2.1.2 No Keyboard Trap
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.
​
​
56
2 Operable πŸ”§
AAA
2.1 Keyboard Accessible
2.1.3 Keyboard (No Exception)
All page functionality is available using the keyboard.
​
​
57
2 Operable πŸ”§
A
2.1 Keyboard Accessible
2.1.4 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.
​
​
58
2 Operable πŸ”§
A
2.2 Enough Time
2.2.1 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.
​
​
59
2 Operable πŸ”§
A
2.2 Enough Time
2.2.2 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.
​
​
60
2 Operable πŸ”§
A
2.2 Enough Time
2.2.2 Pause, Stop, Hide
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.
​
​
61
2 Operable πŸ”§
AAA
2.2 Enough Time
2.2.3 No Timing
The content and functionality have no time limits or constraints.
​
​
62
2 Operable πŸ”§
AAA
2.2 Enough Time
2.2.4 Interruptions
Interruptions (alerts, page updates, etc.) can be postponed or suppressed by the user.
​
​
63
2 Operable πŸ”§
AAA
2.2 Enough Time
2.2.5 Re-authenticating
If an authentication session expires, the user can re-authenticate and continue the activity without losing any data from the current page.
​
​
64
2 Operable πŸ”§
AAA
2.2 Enough Time
2.2.6 Timeouts
Users must be warned of any timeout that could result in data loss, unless the data is preserved for longer than 20 hours of user inactivity.
​
​
65
2 Operable πŸ”§
A
2.3 Seizures and Physical Reactions
2.3.1 Three Flashes or Below Threshold
No page content
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. (
)
​
​
66
2 Operable πŸ”§
AAA
2.3 Seizures and Physical Reactions
2.3.2 Three Flashes
No page content flashes more than 3 times per second.
​
​
67
2 Operable πŸ”§
AAA
2.3 Seizures and Physical Reactions
2.3.3 Animation from Interactions
Users can disable non-essential animation and movement that is triggered by user interaction.
​
​
68
2 Operable πŸ”§
A
2.4 Navigable
2.4.1 Bypass Blocks
A link is provided to skip navigation and other page elements that are repeated across web pages.
​
​
69
2 Operable πŸ”§
A
2.4 Navigable
2.4.1 Bypass Blocks
A proper heading structure and/or identification of page regions/landmarks may be considered a sufficient technique. Because navigating by headings or regions is not supported in most browsers, WebAIM recommends a "skip" link (in addition to headings and regions) to best support sighted keyboard users.
​
​
70
2 Operable πŸ”§
A
2.4 Navigable
2.4.2 Page Titled
The web page has a descriptive and informative page title.
​
​
71
2 Operable πŸ”§
A
2.4 Navigable
2.4.3 Focus Order
The navigation order of links, form elements, etc. is logical and intuitive.
​
​
72
2 Operable πŸ”§
A
2.4 Navigable
2.4.4 Link Purpose (In Context)
The purpose of each link (or form 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).
​
​
73
2 Operable πŸ”§
A
2.4 Navigable
2.4.4 Link Purpose (In Context)
Links (or form image buttons) with the same text that go to different locations are readily distinguishable.
​
​
74
2 Operable πŸ”§
AA
2.4 Navigable
2.4.5 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.
​
​
75
2 Operable πŸ”§
AA
2.4 Navigable
2.4.7 Focus Visible
Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., "More Details") or label text (e.g., "First Name") unless the structure provides adequate differentiation between them.
​
​
76
2 Operable πŸ”§
AAA
2.4 Navigable
2.4.8 Location
If a web page is part of a sequence of pages or within a complex site structure, an indication of the current page location is provided, for example, through breadcrumbs or specifying the current step in a sequence (e.g., "Step 2 of 5 - Shipping Address").
​
​
77
2 Operable πŸ”§
AAA
2.4 Navigable
2.4.9 Link Purpose (Link Only)
The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone.
​
​
78
2 Operable πŸ”§
AAA
2.4 Navigable
2.4.9 Link Purpose (Link Only)
There are no links (or form image buttons) with the same text that go to different locations.
​
​
79
2 Operable πŸ”§
AAA
2.4 Navigable
2.4.10 Section Headings
Beyond providing an overall document structure, individual sections of content are designated using headings, where appropriate.
​
​
80
2 Operable πŸ”§
A
2.5 Input Modalities
2.5.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).
​
​
81
2 Operable πŸ”§
A
2.5 Input Modalities
2.5.2 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. Use onclick, onmouseup, or similar instead. If onmouseup (or similar) is used, you must provide a mechanism to abort or undo the action performed.
​
​
82
2 Operable πŸ”§
A
2.5 Input Modalities
2.5.3 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.
​
​
83
2 Operable πŸ”§
A
2.5 Input Modalities
2.5.4 Motion Actuation
Functionality that is triggered by moving the device (such as shaking or panning a mobile device) or by user movement (such as waving to a camera) can be disabled and equivalent functionality is provided via standard controls like buttons.
​
​
84
2 Operable πŸ”§
AAA
2.5 Input Modalities
2.5.5 Target Size
Clickable targets are at least 44 by 44 pixels in size unless an alternative target of that size is provided, the target is inline (such as a link within a sentence), the target is not author-modified (such as a default checkbox), or the small target size is essential to the functionality.
​
​
85
2 Operable πŸ”§
AAA
2.5 Input Modalities
2.5.6 Concurrent Input Mechanisms
Content does not restrict input to a specific modality, such as touch-only or keyboard-only, but must support alternative inputs (such as using a keyboard on a mobile device).
​
​
86
3 Understandable πŸ—£οΈ
A
3.1 Readable
3.1.1 Language of Page
The language of the page is identified using the HTML lang attribute (e.g., <html lang="en">).
​
​
87
3 Understandable πŸ—£οΈ
AA
3.1 Readable
3.1.2 Language of Parts
The language of page content that is in a different language is identified using the lang attribute (e.g., <blockquote lang="es">).
​
​
88
3 Understandable πŸ—£οΈ
AAA
3.1 Readable
3.1.3 Unusual Words
that may be ambiguous, unfamiliar, or used in a very specific way are defined through adjacent text, a definition list, a glossary, or other suitable method.
​
​
89
3 Understandable πŸ—£οΈ
AAA
3.1 Readable
3.1.4 Abbreviations
The meaning of an unfamiliar abbreviation is provided by expanding it the first time it is used, using the <abbr> element, or linking to a definition or glossary.
​
​
90
3 Understandable πŸ—£οΈ
AAA
3.1 Readable
3.1.5 Reading Level
A more understandable alternative is provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.
​
​
91
3 Understandable πŸ—£οΈ
AAA
3.1 Readable
3.1.6 Pronunciation
If the pronunciation of a word is vital to understanding that word, its pronunciation is provided immediately following the word or via a link or glossary.
​
​
92
3 Understandable πŸ—£οΈ
A
3.2 Predictable
3.2.1 On Focus
When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.
​
​
93
3 Understandable πŸ—£οΈ
A
3.2 Predictable
3.2.2 On Input
When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.
​
​
94
3 Understandable πŸ—£οΈ
AA
3.2 Predictable
3.2.3 Consistent Navigation
Navigation links that are repeated on web pages do not change order when navigating through the site.
​
​
95
3 Understandable πŸ—£οΈ
AA
3.2 Predictable
3.2.4 Consistent Identification
Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way.
​
​
96
3 Understandable πŸ—£οΈ
AAA
3.2 Predictable
3.2.5 Change on Request
Substantial changes to the page, the spawning of pop-up windows, uncontrolled changes of keyboard focus, or any other change that could confuse or disorient the user must be initiated by the user. Alternatively, the user is provided an option to disable such changes.
​
​
97
3 Understandable πŸ—£οΈ
A
3.3 Input Assistance
3.3.1 Error Identification
Required form elements or form elements that require a specific format, value, or length provide this information within the element's label.
​
​
98
3 Understandable πŸ—£οΈ
A
3.3 Input Assistance
3.3.1 Error Identification
errors are efficient, intuitive, and accessible. The error is clearly identified, quick access to the problematic element is provided, and the user can easily fix the error and resubmit the form.
​
​
99
3 Understandable πŸ—£οΈ
A
3.3 Input Assistance
3.3.2 Labels or Instructions
Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.
​
​
100
3 Understandable πŸ—£οΈ
AA
3.3 Input Assistance
3.3.3 Error Suggestion
If an input error is detected (via client-side or server-side validation), suggestions are provided for fixing the input in a timely and accessible manner.
​
​
101
3 Understandable πŸ—£οΈ
AA
3.3 Input Assistance
3.3.4 Error Prevention (Legal, Financial, Data)
If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed.
​
​
102
3 Understandable πŸ—£οΈ
AAA
3.3 Input Assistance
3.3.5 Help
Instructions and cues are provided in context to help in form completion and submission.
​
​
103
3 Understandable πŸ—£οΈ
AAA
3.3 Input Assistance
3.3.6 Error Prevention (All)
If the user can submit information, the submission is reversible, verified, or confirmed.
​
​
104
4 Robust πŸ“–
A
4.1 Compatible
4.1.1 Parsing
Significant HTML/XHTML validation/parsing errors are avoided. Check at
​
​
105
4 Robust πŸ“–
A
4.1 Compatible
4.1.2 Name, Role, Value
Markup is used in a way that facilitates accessibility. This includes following the HTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately.
​
​
106
4 Robust πŸ“–
A
4.1 Compatible
4.1.2 Name, Role, Value
ARIA is used appropriately to enhance accessibility when HTML is not sufficient.
​
​
107
4 Robust πŸ“–
AA
4.1 Compatible
4.1.3 Status Messages
If an important status message is presented and focus is not set to that message, the message must be announced to screen reader users, typically via an ARIA alert or live region.
​
​
There are no rows in this table

Success Criteria
0
Categories
Guidelines
Success Criteria
Link
1 Perceivable πŸ”
29
2 Operable πŸ”§
30


Want to print your doc?
This is not the way.
Try clicking the β‹― next to your doc name or using a keyboard shortcut (
CtrlP
) instead.