ABCDEGHIJKLMNOPQRSTUVWXY
1
GuidelineSuccess CriterionLevelDescriptionRelates to
2
Principle: Perceivable
Can people read the content?
3
Text Alternatives - Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.1.1.1Non-text ContentAInformative images should have descriptive alternative (alt) text.Images
4
Time-based Media - Provide alternatives for time-based media.1.2.1Audio-only and Video-only (Prerecorded)AAny audio-only content should also be conveyed in text. Any video content with no audio track should also be described in text, but could also be described with audio.Video, Audio
5
1.2.2Captions (Prerecorded)AThe audio in videos should be captioned.Video
6
1.2.3Audio Description or Media Alternative (Prerecorded)AActions, descriptions, and other important non-audio content in videos should be described in captions or a separate audio track.Video
7
1.2.4Captions (Live)AALive videos that include audio should be captioned.Video
8
1.2.5Audio Description (Prerecorded)AAActions, descriptions, and other important non-audio content in videos should be described in captions or a separate audio track.Video, Audio
9
1.2.6Sign Language (Prerecorded)AAASign language interpretation should be provided for audio and video content.Video, Audio
10
1.2.7Extended Audio Description (Prerecorded)AAAIn videos, there may be visuals that require interpretation to gather context (i.e. charts, graphics). If there is not a description of the visual or a pause long enough for an audio description, then this extended audio requires the video be temporarily paused so that the audio description can be provided.Video
11
1.2.8Media Alternative (Prerecorded)AAAAll information from the video and audio is provided in text form. This text-based content can be read like a book; there are full descriptions of the visual information, including the setting and the speakers. Additionally, all non-speech sounds are included.Video
12
1.2.9Audio-only (Live)AAALive audio events (i.e. online conference, speeches, live podcasts) have a text alternative. The text alternative includes audio descriptions of non-spoken audio. This can be achieved through a trained human operator who types the transcript with a small delay. Note: Untrained operators (i.e. live transcription services) do not meet this crtierion.Audio
13
Adaptable - Create content that can be presented in different ways (for example simpler layout) without losing information or structure.1.3.1Info and RelationshipsAHeadings and labels are used to provide clarity around how content is related. For example, an asterisk and red text indicates form fields that are required. Additionally, interactions are coded in HTML or ARIA as needed (for example the for attribute on a form label, or aria-describedby on an input that has hint text).Text (namely instructions)
14
1.3.2Meaningful SequenceAThe visual presentation of the content matches what’s read out by a screen reader.All content
15
1.3.3Sensory CharacteristicsANothing is referred to just by its color, size, position, shape, and so on.All content
16
1.3.4OrientationAARotating a device from portrait to landscape doesn’t stop everything being perfectly readable and usable.All content
17
1.3.5Identify Input PurposeAAThe purpose of form fields can be identified by the browser, so that auto-complete suggestions can be offered in a dropdown.Interactives
18
1.3.6Identify PurposeAAAButtons, links, and fields have semantics or metadata what provide the context. The UI component alone is not used to convey meaning (i.e. a letter icon used to represent email)Interactives
19
Distinguishable - Make it easier for users to see and hear content including separating foreground from background.1.4.1Use of ColorAColor shouldn’t be the only thing used to convey meaning.All content
20
1.4.2Audio ControlAAuto playing audio that lasts more than 3 seconds can be turned down or stopped.Audio
21
1.4.3Contrast (Minimum)AAText has a contrast ratio of 4.5 to 1. Large text can be a 3 to 1 ratio if it’s over 24px, or bold and over 19px.

Usable components like form fields and buttons, and graphics like pie charts and line graphs should have a contrast ratio of 3 to 1.		Text, Images
22
1.4.4Resize TextAAThe content is fully responsive. The content adjusts and is readable and usable:

When the zoom is set to 200% in the browser’s settings
At viewport sizes from 320px and up
When custom styles are added to increase the spacing of letters, words, lines, and/or paragraphs		All content
23
1.4.5Images of TextAAText is actual text; not images of text.Images
24
1.4.6Contrast (Enhanced)AAAThe visual presentation of text and images of text has a contrast ratio of at least 7:1. Except for:

Large scale text have a contrast ratio of at least 4:5:1
Decorative images
Text that is a part of a logo or brand name		Text, Images
25
1.4.7Low or No Background AudioAAAIf background audio (i.e. music or nature sounds) is present, it is at at least 20 decibels lower than the foreground speech content. Alternatively, the background audio can also be turned off.Video, Audio
26
1.4.8Visual PresentationAAABlocks of text myst meet the following presentation standards:

User can select the foreground and background colors
Width is no more than 80 characters
Text is not justified, but aligned to a margin
Line spacing is at least a space and a half within paragraphs
Paragraph spacing is at least 1.5 times larger than the line spacing
Text can be resized without assistive technology up to 200%		Text
27
1.4.9Images of Text (No Exception)AAAImages of text are only used for pure decoration. The only situation in which images of text are informational are within brand logos. Images
28
1.4.10ReflowAAContent does not require scrolling in two dimensions. Note: There are some instances in which two dimension scrolling is required for context, such as maps, diagrams, data tables, and gamesAll content
29
1.4.11Non-text ContrastAAFor non-text elements, there must be a constrast of at least 3:1 against adjacent colors. This applies to UI components (buttons) and graphical objects (icons)Interactives, Images
30
1.4.12Text SpacingAAText spacing meets the following criteria:

Line height (line spacing) to at least 1.5 times the font size;
Spacing following paragraphs to at least 2 times the font size;
Letter spacing (tracking) to at least 0.12 times the font size;
Word spacing to at least 0.16 times the font size.		Text
31
1.4.13Content on Hover or FocusAATooltips can be dismissed, usually via the esc key, the text in the tooltip can be selected, and they don’t time out on their own.Interactives
32
Principle: Operable
Can people use the content?
33
Keyboard Accessible - Make all functionality available from a keyboard.2.1.1KeyboardAA user should be able to navigate using the keyboard alone.All content
34
2.1.2No Keyboard TrapAThere shouldn’t be a situation where you enter a modal with the keyboard and can’t get back to where you were.All content
35
2.1.3Keyboard (No Exception)AAAAll functionality can be accessed through a keyboard interface without requiring specific timingAll content
36
2.1.4Character Key ShortcutsAKeyboard shortcuts should use modifier keys, like Ctrl, Command, or Alt/Option. A user should be able to turn the keyboard shortcuts off, remap shortcuts, or activate only when the component has focus.All content
37
Enough Time - Provide users enough time to read and use content.2.2.1Timing AdjustableATime limits should be avoided unless they’re able to be extended or turned off.All content
38
2.2.2Pause, Stop, HideAAutomatically moving/animating content that lasts more than 5 seconds should be able to be stopped or hidden.All content
39
2.2.3No TimingAAAA user is never timed for any action.All content
40
2.2.4InterruptionsAAAA user can turn off updates and notifications, unless they are related to emegencies or errors.All content
41
2.2.5Re-authenticatingAAAWhen an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.All content
42
2.2.6TimeoutsAAAUsers are warned about the duration of their session and the risks of data loss if the user does not take any actions.All content
43
Seizures and Physical Reactions - Do not design content in a way that is known to cause seizures or physical reactions.2.3.1Three Flashes or Below ThresholdANothing flashes, blinks, or flickers more than three times in one second. Or the flash is below the general thresholds.Videos, GIFs, Animations, Images
44
2.3.2Three FlashesAAANothing flashes, blinks, or flickers more than three times in one second.Videos, GIFs, Animations, Images
45
2.3.3Animation from InteractionsAAAAnimated content can be disabled, unless the animation is essential to the functionality or information.Animations
46
Navigable - Provide ways to help users navigate, find content, and determine where they are.2.4.1Bypass BlocksA‘Skip links’ are available for keyboard users to jump past navigation or repeated content.Links, Interactives
47
2.4.2Page TitledAHas a unique <title> that describes what’s on that page.Text
48
2.4.3Focus OrderAWhen a keyboard user tabs through, the order goes from top to bottom and left to right, as you would read the page.All content
49
2.4.4Link Purpose (In Context)AIt is clear where a link will take you from either:
The link text itself
The information in the sentence leading up to the link		Links
50
2.4.5Multiple WaysAAHeader navigation is not the only way to get around a website or eLearning; there’s another way, such as on-page links, a sitemap, or a site-wide search.All content
51
2.4.6Headings and LabelsAAHeadings are descriptive of the content that they contain, form labels clearly describe what information is required, and buttons inform the user what will happen when they’re pressed.Text
52
2.4.7Focus VisibleAAThere’s visible keyboard focus styling to indicate which element you’re currently focused on.All content
53
2.4.8LocationAAAThere is a method for a user to orient themself (i.e. breadcrumbs)All content
54
2.4.9Link Purpose (Link Only)AAAA user can determine the purpose of a link from the link text alone. This can be achieved in the link text or by including an icon (i.e. include a PDF icon or write PDF: [TITLE].)Links
55
2.4.10Section HeadingsAAASection headings are used to organize content. The headings are native to ensure users can jump the focus from heading to heading.Text
56
2.4.11Focus Not Obscured (Minimum)AAAWhen a component receives a keyboard focus, the component is mostly visible. (i.e. the focus outline around a button is mostly visible)All content
57
2.4.12Focus Not Obscured (Enhanced)AAAWhen a component receives a keyboard focus, the component is entirely visible. (i.e. the focus outline around a button is totally visible)All content
58
2.4.13Focus AppearanceAAAWhen a keyboard focus is visible, the area of the focus indicator meets all the following:

Outlines the focused area in 2 pixel thick perimeter
Has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.		All content
59
Input Modalities - Make it easier for users to operate functionality through various inputs beyond keyboard.2.5.1Pointer GesturesAAll actions that are carried out using a gesture (swiping, pinching, and so on) or drawing, can also be done with a button or buttons.All content
60
2.5.2Pointer CancellationAActions (like pressing a button) aren’t triggered on mouse-down; rather on mouse-up.All content
61
2.5.3Label in NameAThe visible text of a form field, button, or link matches the text in the underlying code.All content
62
2.5.4Motion ActuationAThere is no reliance on device motion, like shaking or tilting, to carry out an action.All content
63
2.5.5Target Size (Enhanced)AAAAny element that can be selected (a.k.a target) must be at least 44 by 44 pixels.Interactives
64
2.5.6Concurrent Input MechanismsAAAUsers can switch between different methods of input (keyboard navigation or mouse click) when interacting with content.All content
65
2.5.7Dragging MovementsAADon't rely on dragging as a user action or provide an alternative that uses keyboard navigation.Interactives
66
2.5.8Target Size (Minimum)AAAny element that can be selected (a.k.a target) must be at least 24 by 24 pixels.All content
67
Principle: Understandable
Can people understand the content?
68
Readable - Make text content readable and understandable.3.1.1Language of PageAThere’s a lang attribute on the <html> element that matches the language of the page.All content
69
3.1.2Language of PartsAAAny parts of the page that are in a different language to the page itself are marked up with the appropriate lang value. Names and phrases derived from other languages, like “Déjà vu” in English, don’t need this.All content
70
3.1.3Unusual WordsAAASpecialized words or phrases (non literal words, jargon, idioms, adages) are avoided whenever possible. If required, there is a method for communicating the definition.All content
71
3.1.4AbbreviationsAAAAbbreviations can be interepreted. Oftentimes they are spelled out entirely on their first appearance, then referenced as the acronymAll content
72
3.1.5Reading LevelAAAContent should be at a 9th grade reading level (after removing proper names and titles).All content
73
3.1.6PronunciationAAAComplex or ambiguous words or phrases include prounciation. This does not apply if the context of the sentence clarifies the word's meaning (i.e. desert=abandon versus desert=arid region)All content
74
Predictable - Make Web pages appear and operate in predictable ways.3.2.1On FocusANothing unexpected changes when something on the page receives keyboard focus, like a <button>All content
75
3.2.2On InputANothing unexpected changes when the value of a form field, like an <option> in a <select>, is chosenInteractives
76
3.2.3Consistent NavigationAANavigation is consistent throughout the experience.All content
77
3.2.4Consistent IdentificationAAThings that carry out a particular function should always look and work the same. This is material honesty. For example, an image is not used as a button. All content
78
3.2.5Change on RequestAAAChanges or actions are completed only after a user's approval. For example, a form should not submit until the user selects "Done" or "Submit"All content
79
3.2.6Consistent HelpAUser can always find help when navigating content or completing tasks. Help can look like the following:

- Human contact details such as a phone number, email address, hours of operation.
- Human contact mechanism such as a messaging system, chat client, contact form, social media channel.
- Self-help option such as an up-to-date Frequently Asked Questions, How Do I page, Support page.
- A fully automated contact mechanism such as a chatbot.		All content
80
Input Assistance - Help users avoid and correct mistakes.3.3.1Error IdentificationAError/validation messages should be communicated in text, and should provide suggestions to help the user successfully proceed.All content
81
3.3.2Labels or InstructionsAHelp is offered to prevent triggering a form error; the form label may be enough, but hint text may also be required.All content
82
3.3.3Error SuggestionAAIf an error is detected and the correction is known, the suggestion is provided to the user in a text-based format. For example mispelling "@gmail.com" will provide the help text "Did you mean @gmail.com"All content
83
3.3.4Error Prevention (Legal, Financial, Data)AAImportant forms like a legal agreement or submitting financial information offer the opportunity to check the information entered before sending.All content
84
3.3.5HelpAAAInstructions are provided in a text-based format so that the intended action is clear. This is especially important when the label is not sufficient to describe all functionalities.All content
85
3.3.6Error Prevention (All)AAAThe user must be able to check or confirm their responses before submitting a form. They must also be able to reverse the submission and make edits after submission.All content
86
3.3.7Redundant EntryAInformation previously enterered can be either auto-populated or available for the user to select.

Except when:
re-entering the information is essential,
the information is required to ensure the security of the content, or
previously entered information is no longer valid.		All content
87
3.3.8Accessible Authentication (Minimum)AAPasswords or CAPTCHA tests are not required for any step in an authentication process unless one of the following is provided
An alternative method for logging in (SSO, touchID)
A support mechanism for entering the password (copy paste or keychain) or completing the CAPTCHA test		All content
88
3.3.9Accessible Authentication (Enhanced)AAAPasswords or CAPTCHA tests are not required for any step in an authentication process unless one of the following is provided
An alternative method for logging in (SSO, touchID)
A support mechanism for entering the password (copy paste or keychain) or completing the CAPTCHA test		All content
89
Principle: Robust
Can machines (browsers, screen readers, etc.) read the code?
90
Compatible - Maximize compatibility with current and future user agents, including assistive technologies.4.1.2Name, Role, ValueAThe semantic meaning of every interactive element (form controls, links, headings, landmarks, tables, and so on) is correct, and each has an accessible name.All content
91
4.1.3Status MessagesAAMessages like form errors and success pop-ups are communicated to assistive technology like screen readers.Interactives
92
93
94
95
96
97
98
99
100