ABCDEFGHIJKLMN
1
Site NameSite URL (below)Assessment Date (below)Assessed By (below)Primary Browser and OSOther Notes/Procedure
2
3
IDCategoryCriteriaDescriptionPassWarningFailN/ACaused by (Target Element)Observed functionality (Description)Test MethodRecommendation for RemediationImage Example LinkCE Issue
4
1Images1.1.1 Non-text Content (A)Informative and grouped images must contain alternative text describing the purpose or meaning of the image(s).
5
2Images1.1.1 Non-text Content (A)Decorative images must have empty alternative text or be otherwise hidden from assistive technology.
6
3Images1.1.1 Non-text Content (A)Functional images must have alternative text describing the input's purpose.
7
4Images1.1.1 Non-text Content (A)Complex images (graphs, maps, charts) must have a text description of all relevant information.
8
5Forms and Inputs1.1.1 Non-text Content (A)CAPTCHAs must be identified with alternative text.
9
6Forms and Inputs1.1.1 Non-text Content (A)CAPTCHAs which require user input offer at least two different modalities (e.g., visual and auditory).
10
7Content1.1.1 Non-text Content (A)Adjacent text and images which navigate to the same destination should be presented and announced as one link.
11
8Multimedia1.2.1 Audio-only and Video-only (Prerecorded) (A)Audio-only content must supply a text transcript. The location must be referenced in the accessible name of the audio content.
12
9Multimedia1.2.1 Audio-only and Video-only (Prerecorded) (A)Video-only content supplies either a descriptive text transcript or audio description. The location must be referenced in the accessible name of the video content.
13
10Multimedia1.2.2 Captions (Prerecorded) (A)Multimedia content must have caption support for audio. Captions must be accurate, must include dialogue, the individual speaking, and any relevant audio information.
14
11Multimedia1.2.3 Audio Description or Media Alternative (Prerecorded) (A)Multimedia content must supply a text transcript OR an audio description.
15
12Multimedia1.2.4 Captions (Live) (AA)Live multimedia content must be captioned. Captions must be accurate, must include dialogue, the individual speaking, and any relevant audio information.
16
13Multimedia1.2.5 Audio Description (Prerecorded) (AA)Multimedia content must supply an audio description, which accurately informs the user of any important visual information not already conveyed through audio.
17
14Structure1.3.1 Info and Relationships (A)Landmarks present on the page are used to organize the correct type of content. If landmarks are given names, they need to be uniquely named.
18
15Structure1.3.1 Info and Relationships (A)Wherever text appearance (i.e., bold, italics, size) is used to convey information, that information must also be presented in text alone.
19
16Structure1.3.1 Info and Relationships (A)Headings must have an appropriate relative hierarchy to other headings on the same page.
20
17Structure1.3.1 Info and Relationships (A)Page structure is implemented with HTML. Visual appearance is implemented with CSS. Meaningful HTML is not used to solely achieve a visual effect or appearance.
21
18Forms and Inputs1.3.1 Info and Relationships (A)Form inputs must have labels which are readable (programmatically determinable) by assistive technology.
22
19Forms and Inputs1.3.1 Info and Relationships (A)Form input groupings (i.e., related radio buttons, related checkboxes, related text inputs like First/Last name) are grouped semantically.
23
20Content1.3.1 Info and Relationships (A)Data tables are used to present tabular data. Data tables must include table headers, which are associated with the correct table cells. Descriptions for tables must be programmatically associated.
24
21Content1.3.1 Info and Relationships (A)Layout tables must not include table headers, captions, or summaries. They should be marked with role="presentation".
25
22Structure1.3.1 Info and Relationships (A)All elements use the proper semantic roles, and contain all required parent and child elements. (e.g., a "list" must contain "listitem").
26
23Structure1.3.1 Info and Relationships (A)Element IDs do not repeat more than once per page.
27
24Content1.3.1 Info and Relationships (A)All content is available to (readable by) assistive technology.
28
25Structure1.3.2 Meaningful Sequence (A)The order in which content is presented in DOM must be logical.
29
26Content1.3.2 Meaningful Sequence (A)Whitespace is not utilized to create text spacing within a word. Whitespace is not utilized to create columns or tables visually in plain text.
30
27Content1.3.3 Sensory Characteristics (A)Instructions for operating web-based content and cues for identifying content does not rely exclusively on color, shape, size, position, or sound. (Above/Below references are allowed.)
31
28Resizing1.3.4 Orientation (AA)Content is viewable in portrait and landscape device orientations, and the user is not prompted to switch orientation unless a specific orientation is essential.
32
29Forms and Inputs1.3.5 Identify Input Purpose (AA)The purpose of any form input about the user is identified in code when the purpose is defined in HTML (https://www.w3.org/TR/WCAG22/#input-purposes)
33
30Color1.4.1 Use of Color (A)Color may not exclusively distinguish between plain text and interactive text or distinguish one type of content from another without a 3:1 color contrast difference.
34
31Color1.4.1 Use of Color (A)Color may not exclusively identify content or distinguish differences in any content (e.g., red items are invalid, green items are valid).
35
32Multimedia1.4.2 Audio Control (A)Auto-playing audio that lasts longer than 3 seconds must be pausable OR have an independent volume control.
36
33Color1.4.3 Contrast (Minimum) (AA)Large-scale (24px or 19px bold) text must have a color contrast ratio of 3:1. Logos, inactive components, and pure decoration are excluded.
37
34Color1.4.3 Contrast (Minimum) (AA)Non Large-scale text must have a color contrast ratio of 4.5:1. Logos, inactive components, and pure decoration are excluded.
38
35Resizing1.4.4 Resize Text (AA)Text can be resized up to 200% without page content disappearing or losing functionality.
39
36Resizing1.4.4 Resize Text (AA)Text can be resized up to 200% without text clipping through other elements.
40
37Images1.4.5 Images of Text (AA)Images of text are not used when the same presentation can be made with native HTML/CSS. Logos and branding are excluded.
41
38Resizing1.4.10 Reflow (AA)Content may only scroll in one dimension (horizontal or vertical) at a width and height equivalent of 320x256 pixels or larger. Excluded is content where a two-dimensional layout is necessary (video, data tables, maps, diagrams)
42
39Color1.4.11 Non-text Contrast (AA)Active user interface components must meet a 3:1 color contrast ratio. (This includes buttons, inputs, custom focus indicators, dropdowns, checkboxes, and radio buttons.)
43
40Color1.4.11 Non-text Contrast (AA)Graphical objects which describe important content must meet a 3:1 color contrast ratio; except flags, real life imagery, branding, reference screencaps, and heatmaps.
44
41Resizing1.4.12 Text Spacing (AA)No content or functionality may be lost when text is set to: line spacing of 1.5x font size, letter spacing at 0.12x font size, word spacing at 0.16x font size, and paragraph spacing 2x the font size.
45
42Keyboard1.4.13 Content on Hover or Focus (AA)Content generated by hover or focus can be dismissed without moving hover or focus.
46
43Keyboard1.4.13 Content on Hover or Focus (AA)Content generated by hover or focus of an element can be hovered over without the content disappearing.
47
44Keyboard1.4.13 Content on Hover or Focus (AA)Content generated by hover or focus of an element does not disappear until dismissed, is no longer valid, or hover or focus is removed.
48
45Keyboard2.1.1 Keyboard (A)All interactive elements must be able to be navigated to and interacted with using a keyboard only.
49
46Keyboard2.1.1 Keyboard (A)Timing of keystrokes must not be required for interacting with any functionality.
50
47Keyboard2.1.1 Keyboard (A)Functionality available when hovering with a cursor must be available to keyboard input.
51
48Keyboard2.1.2 No Keyboard Trap (A)Focus that enters any element must be able to leave that element. If the method requires more than ESC, Arrow Keys, or Tab, the user must be informed of the method.
52
49Keyboard2.1.4 Character Key Shortcuts (A)If any keyboard shortcut only requires letter, number, punctuation, or symbol characters, an option exists to turn it off, OR to remap it to include CTRL or ALT modifiers, OR it is only active on focus.
53
50Motion2.2.1 Timing Adjustable (A)Any time limit may be disabled, extended (with a 20-second warning), or adjusted; unless it is part of a current real-life event, it is essential, or it has a time limit of 20 hours or more.
54
51Motion2.2.2 Pause, Stop, Hide (A)Any moving, blinking, or scrolling information that starts automatically, lasts over 5 seconds, and is part of other content must include a pause, stop, or hide mechanism.
55
52Motion2.2.2 Pause, Stop, Hide (A)Any automatically updating content that starts automatically and is part of other content must include a pause, stop, or hide mechanism.
56
53Motion2.3.1 Three Flashes or Below Threshold (A)No content may flash more than 3 times per any 1-second period.
57
54Keyboard2.4.1 Bypass Blocks (A)Content which repeats on multiple webpages has a mechanism to skip over it.
58
55Content2.4.2 Page Titled (A)All pages have a title, which details the topic or purpose of the page. Titles should be organized from most-specific to least-specific.
59
56Keyboard2.4.3 Focus Order (A)Focus order must follow a logical sequence. Tabindex values must not interfere with the proper tab sequence of the page.
60
57Keyboard2.4.3 Focus Order (A)Dialog content must gain focus immediately or as the next press of TAB once activated. Dismissing dialog content returns focus to the trigger or to the next element in DOM after the trigger.
61
58Content2.4.4 Link Purpose (In Context) (A)Link destination is described by link text on its own or by link text programmatically associated with other text on the page (except where the destination is ambiguous to all users).
62
59Structure2.4.5 Multiple Ways (AA)Two or more mechanisms of finding a webpage are available, unless the page is accessed as part of a step in a process.
63
60Content2.4.6 Headings and Labels (AA)Headings that exist describe the topic or purpose of the content following after.
64
61Forms and Inputs2.4.6 Headings and Labels (AA)Each label describes the purpose of its associated input.
65
62Keyboard2.4.7 Focus Visible (A)Every focusable element has a focus indicator.
66
63Keyboard2.4.11 Focus Not Obscured (Minimum) (AA)Elements that currently have focus may never be hidden by other elements (such as a sticky header).
67
64Interaction2.5.1 Pointer Gestures (A)All functionality that uses multipoint or path-based gestures can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
68
65Interaction2.5.2 Pointer Cancellation (A)Functionality operated with a single pointer must: not fire on the down event; fire on the up-event along with a way to abort or undo; reverse the function on the up-event, or complete an essetial function on the down event.
69
66Forms and Inputs2.5.3 Label in Name (A)For user interface components with labels that include text or images of text, the accessible name contains the text that is presented visually.
70
67Interaction2.5.4 Motion Actuation (A)Any functionality activated by device motion can be performed with a user interface component that does not require motion.
71
68Interaction2.5.4 Motion Actuation (A)Any functionality activated by device motion can be disabled.
72
69Interaction2.5.7 Dragging Movements (AA)Any functionality that can be achieved by dragging (click and hold then move) must be operable without the need for dragging.
73
70Interaction2.5.8 Target Size (Minimum) (AA)All elements must have a clickable target size of at least 24x24 pixels unless the element is inline, controlled by the browser, or the "target offset" to all adjacent clickable elements is at least 24px.
74
71Structure3.1.1 Language of Page (A)The default language of each page must be defined in the html tag.
75
72Structure3.1.2 Language of Parts (AA)Text in a different language than the page default must be identified in HTML; aside from proper names, technical terms, words without a defined language, and words that are part of the vernacular of the immediately surrounding text.
76
73Keyboard3.2.1 On Focus (A)When a user interface component gains focus, it may not trigger a change of context. (e.g., on focus must not submit a form, launch a new window, cause an immediate change of focus, or change the purpose of any page content.)
77
74Interaction3.2.2 On Input (A)If a change of context is triggered by a change in a setting or value of a user interface component (for example, changing the option of a select box), the user must be warned beforehand.
78
75Structure3.2.3 Consistent Navigation (AA)Navigations which are utilized on multiple pages keep the same relative order on all pages, unless the user initiates the change. (Items can be removed or added, but they must maintain the same order relative to each other.)
79
76Structure3.2.4 Consistent Identification (AA)Any components with similar functionality used on multiple pages must be labeled identically and function identically. (e.g. a header Search field must be labeled the same on all pages)
80
77Structure3.2.6 Consistent Help (A)Help mechanisms such as contact details, messaging, chat, or self-help options must be in the same relative order on all pages where the information is present.
81
78Forms and Inputs3.3.1 Error Identification (A)Whenever an input error is detected through validation, the user is informed of the error, and what was incorrect in the input.
82
79Forms and Inputs3.3.2 Labels or Instructions (A)Visible labels or instructions are available for all inputs and input groupings.
83
80Forms and Inputs3.3.2 Labels or Instructions (A)Labels describe any required fields or required formatting requirements. (e.g. If a MM/DD/YYYY format is required)
84
81Forms and Inputs3.3.3 Error Suggestion (AA)If an input error was detected due to a blank input on a required field, the user is informed of the fields which were left blank in the error message.
85
82Forms and Inputs3.3.3 Error Suggestion (AA)If an input error was detected due to an input that did not follow required formatting, the user is informed of the proper formatting in the error message.
86
83Forms and Inputs3.3.3 Error Suggestion (AA)If an input error was detected that was outside of the allowable range of values, the user is informed of the proper range in the error message.
87
84Forms and Inputs3.3.4 Error Prevention (Legal, Financial, Data) (AA)Any legal or financial data input must be reversible, validated for input errors, or include a mechanism for reviewing, confirming, or correcting information before submission.
88
85Forms and Inputs3.3.7 Redundant Entry (A)Users are not required to refill the same information in the same process unless it is available as a selection, is essential, is ensuring security, or the original information is no longer valid.
89
86Forms and Inputs3.3.8 Accessible Authentication (AA)Login processes must not solely rely on cognitive tests. All steps in a login process must support some method that does not rely on memory or knowledge.
90
87Structure4.1.2 Name, Role, Value (A)All elements have appropriate accessible names and roles assigned.
91
88Multimedia4.1.2 Name, Role, Value (A)Video and audio content or iframes which present user-readable content require a title or description.
92
89Structure4.1.2 Name, Role, Value (A)All custom functionality utilizes the appropriate ARIA features for states, properties, and values. (e.g. aria-expanded, aria-haspopup)
93
90Motion4.1.3 Status Messages (AA)Status messages which change without a page reload notify users of assistive technologies without requiring the user to send focus to the message.
94
UXUser ExperienceNon-WCAG User Experience CalloutsAdd your own description here for any UX failures found.