All Guidelines

Number	Guideline	Category	Tools
1	Informative and grouped images must contain alternative text describing the purpose or meaning of the image(s).	Images	See notes
2	Decorative images must have empty alternative text or be otherwise hidden from assistive technology.	Images	See notes Browser extension Siteimprove
3	Functional images must have alternative text describing the input's purpose.	Images	Browser extension Manual
4	Complex images (graphs, maps, charts) must have a text description of all relevant information.	Images	See notes
5	CAPTCHAs must be identified with alternative text	Forms and Inputs	Screen reader
6	CAPTCHAs which require user input offer at least two different modalities (e.g. visual and auditory)	Forms and Inputs	Screen reader Keyboard
7	Adjacent text and images which navigate to the same destination should be presented and announced as one link.	Content	Siteimprove
8	Audio-only content must supply a basic text transcript. The location must be referenced in the accessible name of the audio content.	Multimedia	See notes
9	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.	Multimedia	See notes
10	Multimedia content must have caption support for audio. Captions must be accurate, must include dialogue, the individual speaking, and any relevant audio information.	Multimedia	See notes
11	Multimedia content must supply a text transcript OR an audio description.	Multimedia	See notes
12	Live multimedia content must be captioned. Captions must be accurate, must include dialogue, the individual speaking, and any relevant audio information.	Multimedia	See notes
13	Multimedia content must supply an audio description, which accurately informs the user of any important visual information not already conveyed through audio.	Multimedia	See notes
14	Landmarks present on the page are used to organize the correct type of content.	Structure	Browser extension Screen reader
15	Wherever text appearance (i.e., bold, italics, underline, size) is used to convey information, that information must also be presented in text alone.	Structure	Siteimprove
16	Headings must follow appropriate relative hierarchy to other headings on the same page.	Structure	Browser extension
17	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.	Structure	Siteimprove Manual
18	Form inputs must have labels which are readable (programmatically determinable) by assistive technology.	Forms and Inputs	Siteimprove
19	Form input groupings (i.e., related radio buttons, related checkboxes, related text inputs like First/Last name) are grouped semantically.	Forms and Inputs	Siteimprove
20	Data tables may only be used to present tabular data. Data tables must include table headers, which are associated with the correct table cells. Descriptive text for data tables must be programmatically associated.	Content	Siteimprove
21	Layout tables must not include table headers, captions, or summaries. They should be marked with role="presentation".	Content	Siteimprove
22	All elements with semantic roles contain all required parent and child elements. (e.g., a "list" must contain "listitem").	Structure	Siteimprove
23	Element IDs do not repeat more than once per page.	Structure	Siteimprove Browser extension
24	All content is available to (readable by) assistive technology.	Content	Keyboard Screen reader
25	The order in which content is presented in DOM must be logical.	Structure	Screen reader Browser extension
26	Whitespace is not utilized to create text spacing within a word. Whitespace is not utilized to create columns or tables visually in plain text.	Content	Screen reader Siteimprove
27	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 allowed)	Content	Manual Siteimprove
28	Content is viewable in portrait and landscape device orientations, and the user is not prompted to switch orientation unless a specific orientation is essential.	Resizing	Manual See notes
29	The purpose of any form input about the user is identified in code when the purpose is defined in HTML.	Forms and Inputs	Manual Siteimprove See notes
30	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.	Color	Siteimprove Manual See notes
31	Color may not exclusively identify content or distinguish differences in any content (e.g. Red items are invalid, Green items are valid)	Color	Manual
32	Auto-playing audio that lasts longer than 3 seconds must be pausable OR have an independent volume control.	Multimedia	Manual See notes
33	Large-scale (24px or 19px bold) text must have a color contrast ratio of 3:1. Logos, inactive components, and pure decoration excluded.	Color	Color contrast analyzer Siteimprove Browser extension
34	Non Large-scale text must have a color contrast ratio of 4.5:1. Logos, inactive components, and pure decoration excluded.	Color	Color contrast analyzer Siteimprove Browser extension
35	Text can be resized up to 200% without page content disappearing or losing functionality	Resizing	See notes
36	Text can be resized up to 200% without text clipping through other elements.	Resizing	See notes
37	Images of text are not used when the same presentation can be made with native HTML/CSS. Logos and branding are excluded.	Images	Manual
38	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)	Resizing	Manual
39	Active user interface components must meet a 3:1 color contrast ratio. (This includes buttons, inputs, custom focus indicators, dropdowns, checkboxes, and radio buttons.)	Color	Color contrast analyzer
40	Graphical objects that describe important content must meet a 3:1 color contrast ratio; except flags, real-life imagery, branding, reference screencaps, and heatmaps.	Color	Color contrast analyzer
41	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.	Resizing	See notes
42	Content generated by hover or focus can be dismissed without moving hover or focus.	Keyboard	Keyboard
43	Content generated by hover or focus of an element can be hovered over without the content disappearing.	Keyboard	Keyboard
44	Content generated by hover or focus of an element does not disappear until dismissed, is no longer valid, or hover or focus is removed.	Keyboard	Keyboard
45	All interactive elements must be able to be navigated to and interacted with using a Keyboard only.	Keyboard	Keyboard
46	Timing of keystrokes must not be required for interacting with any functionality.	Keyboard	Keyboard
47	Functionality available when hovering with a cursor must be available to keyboard input.	Keyboard	Keyboard
48	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.	Keyboard	Keyboard
49	If any keyboard shortcut only requires letter, number, punctuation, or symbol characters, an option exists to turn it off, remap to include CTRL or ALT modifiers, OR be active on focus only.	Keyboard	Keyboard
50	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 has a time limit of 20 hours or more.	Motion	Manual
51	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.	Motion	Manual
52	Any automatically updating content that starts automatically and is part of other content must include a pause, stop, or hide mechanism.	Motion	Manual
53	No content may flash more than 3 times per any 1-second period.	Motion	Manual
54	Content which repeats on multiple webpages has a mechanism of skipping over it.	Keyboard	Keyboard Screen reader
55	All pages have a title, which details the topic or purpose of the page. Titles should be organized from most-specific to least-specific.	Content	Siteimprove Manual
56	Focus order must follow a logical sequence. Tabindex values must not interfere with the proper tab sequence of the page.	Keyboard	Keyboard
57	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.	Keyboard	Keyboard Screen reader
58	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).	Content	Siteimprove Manual
59	Two or more mechanisms of finding a webpage are available, unless the page is accessed as part of a step in a process.	Structure	Manual
60	Headings that exist describe the topic or purpose of the content following after.	Content	Manual Browser extension
61	Labels describe the purpose of the inputs they are associated with.	Forms and Inputs	Manual
62	Every focusable element has a focus indicator present.	Keyboard	Manual Keyboard
63	Elements that currently have focus may never be hidden by other elements (such as a sticky header).	Keyboard
64	All functionality that uses multipoint, or path-based gestures can be operated with a single pointer without a path-based gesture, unless essential.	Interaction	Manual See notes
65	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 completing the function on the down event is essential.	Interaction	Manual See notes
66	For user interface components with labels that include text or images of text, the accessible name contains the text that is presented visually.	Forms and Inputs	Siteimprove
67	Any functionality which is activated by device motion can be performed with a User interface component that does not require motion.	Interaction	Manual See notes
68	Any functionality which is activated by device motion can be disabled.	Interaction	Manual See notes
69	Any functionality that can be achieved by dragging (click and hold then move) must be operable without the need for dragging (unless essential).	Interaction
70	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.	Interaction
71	The default language of each page must be defined in the html tag.	Structure	Siteimprove Screen reader
72	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.	Structure	Manual
73	When a user interface component gains focus, it may not trigger a change of context. (Submission of a form, new window launch, immediate change of focus, changing content on the page where such that the purpose is different)	Keyboard	Manual Keyboard
74	When the setting or value of a User Interface component is changed, that does not trigger a change of context unless the user is informed of the behavior beforehand.	Interaction	Manual Keyboard
75	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)	Structure	Manual
76	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)	Structure	Manual Screen reader
77	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.	Structure	Manual
78	Whenever an input error is detected through validation, the user is informed of the error, and what was incorrect in the input.	Forms and Inputs	Manual Screen reader
79	Visible labels or instructions are available for all inputs and input groupings.	Forms and Inputs	Manual
80	Labels describe any required fields or required formatting requirements. (e.g. If a MM/DD/YYYY format is required)	Forms and Inputs	Manual
81	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.	Forms and Inputs	Manual
82	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.	Forms and Inputs	Manual
83	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.	Forms and Inputs	Manual
84	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.	Forms and Inputs	Manual
85	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.	Forms and Inputs	Manual
86	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.	Forms and Inputs
87	All elements have appropriate accessible names and roles assigned.	Structure	Screen reader Manual
88	Iframes which present user-readable content require a title or description.	Multimedia	Siteimprove
89	All custom functionality utilizes the appropriate ARIA features for states, properties, and values. (e.g. aria-expanded, aria-haspopup)	Structure	Screen reader Manual
90	Status messages which change without a page reload notify users of assistive technologies without requiring the user to send focus to the message.	Motion	Screen reader Manual