Please wait

Loading...

Acquia Help

Filter by product:

Acquia Optimize common questions

Introduction¶

This article gives information about the accessibility checks that the scan performs.

The four principles of web accessibility for website content as specified in W3C are:

"Perceivable - Information and user interface components must be presentable to users in ways they can perceive.
This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses).
Operable - User interface components and navigation must be operable.
This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform).
Understandable - Information and the operation of user interface must be understandable.
This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding).
Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible).

If any of these are not true, users with disabilities will not be able to use the Web.”

For more information, see the external guide:

Understanding the four principles of Accessibility.

We prioritize the results of the accessibility checks and places any issues in the following categories:

Error
The issue is in direct conflict with the standard and needs to be fixed.
Warning
The issue is most likely in conflict with the standard, do a manual review and fix the issue.
Review
The issue cannot be programatically determined as an error or warning and requires human review . Do a manual review of the issue to determine if any fix can be done.

For more information, see the user guide article:

Priority, Severity, Difficulty, and Likelihood.

Checklist¶

This section gives instructions on how to find the list of issues in the tool.

Select Checklist (insect icon) from the menu on the left side of the page. This page shows a list of all checks that are done for the selected category.

Select the compliance level to filter for on the Accessibility Checklist page:
- Level A
- Level AA
- Level AAA
- Ignored
- Passed.
  If needed, use the filter to filter the list for:
- Responsibility
- Labels
- Accessibility Error Type.
The results are shown in a table with the following headers:
- Check: This column shows the name and description of the check that is done.
- Responsibility: This column shows the designated team or teams that are normally responsible for fixing this type of error. This column is automatically filled in. The areas of responsibility are:
  - UX Design
  - Front End Development
  - Content Authoring
  - Visual Design.
- Related to Success Criteria: This column shows a list of the compliance success criteria category.
- Help Center: Click to navigate to the Help Center to see the details about the issue and some suggestions on how to fix it.
  For more information, see the user guide article:
  Accessibility Help Center.
- Action Button: This column has a button. Click the button for more options:
- Ignore this check: Issues that are set to Ignore are permanently omitted from future scans and compliance scores.
- Domain Compliance: This column shows the percentage of compliance on this domain.
- Pages: This column lists the number of pages that have the error. Click to navigate to the error page to view:
  - The URL for all of the pages where the error occurs.
  - Suggestions on how to fix the errors.
  - Information about the designated team or competence that is needed to fix this type of error.

WCAG 2.0 A¶

This section lists the checks that are done by the scan for this success criteria selection.

Check id	Check name	Description	Type	Success Criteria
58	All <code>input</code> elements with a <code>type</code> attribute value of "image" have an <code>alt</code> attribute.	<code>input</code> element with <code>type</code> of "image" must have an <code>alt</code> attribute.	error	1.1.1 Non-text Content WCAG 2.0 A
59	Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" identifies the purpose or function of the image.	<code>input</code> element with <code>type</code> of "image" must have Alt text that identifies the purpose or function of the image.	review	1.1.1 Non-text Content WCAG 2.0 A
64	All <code>area</code> elements have an <code>alt</code> attribute.	<code>area</code> elements must contain a <code>alt</code> attribute.	error	1.1.1 Non-text Content WCAG 2.0 A
65	Alt text for all <code>area</code> elements identifies the link destination.	Alt text for <code>area</code> element must describe the link destination.	review	1.1.1 Non-text Content WCAG 2.0 A
193	Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" contains all non-decorative text in the image.	This error is generated for all <code>input</code> elements that have a <code>type</code> of "image".	review	1.1.1 Non-text Content WCAG 2.0 A
194	Alt text for all <code>area</code> elements contains all non-decorative text in the image area.	This error is generated for all <code>area</code> elements.	review	1.1.1 Non-text Content WCAG 2.0 A
375	SVG element with explicit role has non-empty accessible name	This rule checks that each SVG image element that is explicitly included in the accessibility tree has a non-empty accessible name.	error	1.1.1 Non-text Content WCAG 2.0 A
376	Image has non-empty accessible name	This rule checks that each image either has a non-empty accessible name or is marked up as decorative.	error	1.1.1 Non-text Content WCAG 2.0 A
377	<code>object</code> element rendering non-text content has non-empty accessible name	This rule checks that each object element rendering non-text content has a non-empty accessible name.	error	1.1.1 Non-text Content WCAG 2.0 A
378	Image not in the accessibility tree is decorative	This rule checks that visible img svg and canvas elements that are ignored by assistive technologies are decorative.	warning	1.1.1 Non-text Content WCAG 2.0 A
379	Image accessible name is descriptive	This rule checks that the accessible names of images serve an equivalent purpose to the image.	warning	1.1.1 Non-text Content WCAG 2.0 A
380	Image button has non-empty accessible name	This rule checks that each image button element has a non-empty accessible name.	error	1.1.1 Non-text Content WCAG 2.0 A
17	Sound file must have a text transcript.	<code>a</code> (anchor) element cannot contain an <code>href</code> attribute value that ends with any of the following (all case insensitive): .wav .snd .mp3 .iff .svx .sam .smp .vce .vox .pcm .aif.	review	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
20	Links to multimedia require a text transcript.	<code>a</code> (anchor) element must not contain an <code>href</code> attribute value that ends with (case insensitive): .wmv .mpg .mov .ram .aif.	warning	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
66	<code>area</code> link to sound file must have text transcript.	<code>area</code> elements must not contain <code>href</code> attribute values that end with (all case insensitive) .wav .snd .mp3 .iff .svx .sam .smp .vce .vox .pcm .aif	warning	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
393	Video element visual-only content has accessible alternative.	This rule checks that video elements without audio have an alternative available.	warning	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
394	Audio element content has text alternative	This rule checks that audio elements have a text alternative available.	warning	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
395	Video element auditory content has accessible alternative	This rule checks that video elements have an alternative for information conveyed through audio.	warning	1.2.2 Captions (Prerecorded) WCAG 2.0 A
396	<code>object</code> link to multimedia file require equivalent alternatives (e.g. captions or auditory descriptions of the visual track).	If <code>object</code> element contains a <code>type</code> attribute value of "video" then this error will be generated.	review	1.2.3 Audio Description or Media Alternative (Prerecorded) WCAG 2.0 A
397	Video element visual content has accessible alternative	This rule checks that video elements with audio have an alternative for the video content as audio or as text.	warning	1.2.3 Audio Description or Media Alternative (Prerecorded) WCAG 2.0 A
28	A "skip to content" link appears on all pages with blocks of material prior to the main document.	Provide a mechanism to bypass blocks of material that are repeated on multiple Web units.	review	2.4.1 Bypass Blocks WCAG 2.0 A
31	All <code>frames</code> have a <code>title</code> attribute.	Each <code>frame</code> element must have a <code>title</code> attribute.	error	2.4.1 Bypass Blocks WCAG 2.0 A
32	All <code>frame</code> <code>titles</code> identify the purpose or function of the <code>frame</code>.	<code>frame</code> <code>title</code> must describe the purpose or function of the <code>frame</code>.	review	2.4.1 Bypass Blocks WCAG 2.0 A
84	ASCII art should have a skipover link.	ASCII art must have a link immediately preceding it that jumps over the ASCII art. [Editor’s Note - describe how to detect ASCII art. How to detect if a skipover link is already present?]	warning	2.4.1 Bypass Blocks WCAG 2.0 A
262	All groups of links with a related purpose are marked.	When links are grouped into logical sets (for example in a navigation bar or main menu that appears on every page in a site) they should be marked up as a unit.	review	2.4.1 Bypass Blocks WCAG 2.0 A
414	Aria required owned elements	This rule checks that an element with an explicit semantic role has at least one of its required owned elements.	error	1.3.1 Info and Relationships WCAG 2.0 A
415	Table header cell has assigned cells	This rule checks that each table header has assigned cells in a table element.	error	1.3.1 Info and Relationships WCAG 2.0 A
417	Element needs to have the right semantic role	Elements you can click touch or navigate to need to have the right semantic role	warning	1.3.1 Info and Relationships WCAG 2.0 A
421	Heading has non-empty accessible name	This rule checks that each heading element in the document has an accessible name which is not empty.	error	1.3.1 Info and Relationships WCAG 2.0 A
47	All <code>h6</code> elements are not used for formatting.	<code>h6</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
82	All <code>p</code> elements are not used as headers.	All <code>p</code> element content must not be marked with either <code>b</code> <code>i</code> <code>u</code> <code>strong</code> <code>font</code> <code>em</code>.	warning	1.3.1 Info and Relationships WCAG 2.0 A
112	All data <code>table</code> summaries contain text.	<code>table</code> element cannot contain an empty <code>summary</code> attribute if it"s a data <code>table</code>.	error	1.3.1 Info and Relationships WCAG 2.0 A
114	All layout <code>tables</code> have an empty <code>summary</code> attribute or no <code>summary</code> attribute.	The <code>table</code> element <code>summary</code> attribute for all layout tables contains no printable characters or is absent.	error	1.3.1 Info and Relationships WCAG 2.0 A
42	All <code>h1</code> elements are not used for formatting.	<code>h1</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
43	All <code>h2</code> elements are not used for formatting.	<code>h2</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
44	All <code>h3</code> elements are not used for formatting.	<code>h3</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
45	All <code>h4</code> elements are not used for formatting.	<code>h4</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
115	All layout tables do not contain <code>caption</code> elements.	<code>table</code> element content cannot contain a <code>caption</code> element if it"s a layout <code>table</code>.	error	1.3.1 Info and Relationships WCAG 2.0 A
154	<code>pre</code> element should not be used to create tabular layout.	This error is generated for each <code>pre</code> element.	review	1.3.1 Info and Relationships WCAG 2.0 A
203	All data table summaries describe navigation and structure of the table.	The <code>table</code> summary can"t be garbage text.	review	1.3.1 Info and Relationships WCAG 2.0 A
241	Table markup is used for all tabular information.	The objective of this technique is to present tabular information in a way that preserves relationships within the information even when users cannot see the table or the presentation format is changed.	review	1.3.1 Info and Relationships WCAG 2.0 A
242	Table captions identify the table.	If the table has a caption then the caption must identify the table.	review	1.3.1 Info and Relationships WCAG 2.0 A
243	Table summaries do not duplicate the table captions.	The summary and the caption must be different. Caption identifies the table. Summary describes the table contents.	error	1.3.1 Info and Relationships WCAG 2.0 A
245	Data tables that contain more than one row/column of headers use the <code>id</code> and <code>headers</code> attributes to identify cells.	id and headers attributes allow screen readers to speak the headers associated with each data cell when the relationships are too complex to be identified using the th element alone or the th element with the scope attribute.	error	1.3.1 Info and Relationships WCAG 2.0 A
248	All visual lists are marked.	Create lists of related items using list elements appropriate for their purposes.	review	1.3.1 Info and Relationships WCAG 2.0 A
407	ARIA attribute is defined in WAI-ARIA	This rule checks that each aria- attribute specified is defined in ARIA 1.2.	error	1.3.1 Info and Relationships WCAG 2.0 A
408	Aria state or property has valid value	This rule checks that each ARIA state or property has a valid value type.	error	1.3.1 Info and Relationships WCAG 2.0 A
409	ARIA required context role	This rule checks that an element with an explicit semantic role exists inside its required context.	error	1.3.1 Info and Relationships WCAG 2.0 A
410	ARIA required ID references exist	This rule checks that every ID reference required by WAI-ARIA exists	error	1.3.1 Info and Relationships WCAG 2.0 A
411	Use a quote element to mark up quotations.	Review that the quotations in your text are within relevant quote elements to ensure that users of assistive technology can easily identify quotations.	warning	1.3.1 Info and Relationships WCAG 2.0 A
412	Non-decorative content in pseudo classes	The “::before” and “::after” pseudo classes contains non-decorative content.	error	1.3.1 Info and Relationships WCAG 2.0 A
413	Headers attribute specified on a cell refers to cells in the same table element	This rule checks that all headers attributes in cells of a given table refers to ids of cells within that same table.	error	1.3.1 Info and Relationships WCAG 2.0 A
46	All <code>h5</code> elements are not used for formatting.	<code>h5</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
210	All <code>select</code> elements have a label that describes the purpose or function of the control.	All <code>select</code> elements have a label that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
211	All <code>input</code> elements <code>type</code> of "text" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "text" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
217	All <code>input</code> elements <code>type</code> of "password" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "password" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
218	All <code>input</code> elements <code>type</code> of "text" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "text" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
219	All <code>input</code> elements <code>type</code> of "checkbox" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "checkbox" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
220	All <code>input</code> elements <code>type</code> of "radio" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "radio" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
246	All <code>form</code> fields that are required are indicated to the user as required.	Ensure that the label for any interactive component within Web content makes the purpose of the component clear.	review	3.3.2 Labels or Instructions WCAG 2.0 A
392	Each label associated with an <code>input</code> element contains text.	Label must contain some text.	error	3.3.2 Labels or Instructions WCAG 2.0 A
133	All layout <code>tables</code> make sense when linearized.	This error is generated for all layout <code>tables</code>. If the <code>table</code> contains <code>th</code> elements then it is a data <code>table</code>. If the <code>table</code> does not contain <code>th</code> elements then it is a layout <code>table</code>.	review	1.3.2 Meaningful Sequence WCAG 2.0 A
398	HTML layout tables should make sense when linearized	If layout tables are used it is important that the content makes sense when linearized	warning	1.3.2 Meaningful Sequence WCAG 2.0 A
399	Using white space characters to control spacing within a word	White space characters such as space tab line break or carriage return are not used to format individual words visually.	error	1.3.2 Meaningful Sequence WCAG 2.0 A
400	Using white space characters to create multiple columns or to format tables in plain text content	White space characters such as space tab line break or carriage return are not used to create columns or format tables in plain text.	error	1.3.2 Meaningful Sequence WCAG 2.0 A
416	Changing the meaning of content by positioning information with CSS.	CSS rather than structural markup is used to modify the visual layout of the content and the modified layout changes the meaning of the content.	review	1.3.2 Meaningful Sequence WCAG 2.0 A
250	Sensory Characteristics.	Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.	review	1.3.3 Sensory Characteristics WCAG 2.0 A
275	Loading the web page does not cause a new window to open.	Pages do not disorient users by opening up one or more new windows as soon as a page is loaded.	review	3.2.1 On Focus WCAG 2.0 A
68	<code>area</code> should not open a new window without warning.	<code>area</code> element <code>target</code> attribute values must contain any one of (case insensitive) _self _top _parent.	warning	3.2.2 On Input WCAG 2.0 A
92	All <code>select</code> elements do not cause an extreme change in context.	<code>select</code> element cannot contain <code>onchange</code> attribute.	warning	3.2.2 On Input WCAG 2.0 A
267	All form submission error messages identify any empty required fields.	Helps the user to visualize how content has been structured and how to navigate back to previous Web units and may identify the current location within a series of Web units.	review	3.3.1 Error Identification WCAG 2.0 A
96	All <code>textarea</code> elements have a label that is positioned close to control.	<code>textarea</code> element must have an associated <code>label</code> element that is positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
122	All <code>input</code> elements <code>type</code> of "password" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "password" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
123	All <code>input</code> elements <code>type</code> of "checkbox" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "checkbox" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
124	All <code>input</code> elements <code>type</code> of "file" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "file" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
125	All <code>input</code> elements <code>type</code> of "radio" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "radio" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
187	Each <code>input</code> element has only one associated <code>label</code>.	<code>input</code> element must have only one associated <code>label</code> element.	error	3.3.2 Labels or Instructions WCAG 2.0 A
205	All <code>input</code> elements <code>type</code> of "file" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "file" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
209	All <code>select</code> elements have a label that is positioned close to the control.	All <code>select</code> elements have a label that is positioned close to the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A

WCAG 2.0 AA¶

Checks in this section include all checks from the previous category:

WCAG 2.0 A.

Check id	Check name	Description	Type	Success Criteria
263	Repeated blocks of content appear in the same <code>frame</code> within the <code>frameset</code>.	Framesets can be used to group blocks of repeated material.	review	3.2.3 Consistent Navigation WCAG 2.0 AA
401	Captions (Live)	Live video has captions.	warning	1.2.4 Captions (Live) WCAG 2.0 AA
276	Repeated components appear in the same relative order each time they appear.	Maintain consistent layout or presentation between Web units by presenting components that are repeated in these Web units in the same relative order each time they appear. Other components can be inserted between them but their relative order is not changed.	review	3.2.3 Consistent Navigation WCAG 2.0 AA
81	List items must not be used to format text.	OL element should not contain only one LI element.	warning	3.2.4 Consistent Identification WCAG 2.0 AA
100	<code>blockquote</code> must not be used for indentation.	This error is generated if any <code>blockquote</code> element is missing a <code>cite</code> attribute.	review	3.2.4 Consistent Identification WCAG 2.0 AA
268	All form submission error messages provide assistance in correcting the error.	Information about the nature and location of the input error is provided in text to enable the users to identify the problem.	review	3.3.3 Error Suggestion WCAG 2.0 AA
269	Form submission data is presented to the user before final acceptance for all irreversible transactions.	Provide users with a way to ensure their input is correct before completing an irreversible transaction.	review	3.3.4 Error Prevention (Legal Financial Data) WCAG 2.0 AA

WCAG 2.0 AAA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA.

Check id	Check name	Description	Type	Success Criteria
272	Information deleted using a web page can be recovered.	Help users with disabilities avoid serious consequences as the result of a mistake when performing an action that cannot be reversed.	review	3.3.6 Error Prevention (All) WCAG 2.0 AAA
18	Anchor should not open a new window without warning.	<code>a</code> (anchor) element must not contain a <code>target</code> attribute unless the <code>target</code> attribute value is either _self _top or _parent.	warning	3.2.5 Change on Request WCAG 2.0 AAA
274	Change of context occurs only by user activation unless a warning is provided.	Provide a method for activating things that is predictable by the user.	review	3.2.5 Change on Request WCAG 2.0 AAA
420	Sign Language (Prerecorded)	Sign language interpretation is provided for all prerecorded audio content in synchronized media.	warning	1.2.6 Sign Language (Prerecorded) WCAG 2.0 AAA
419	Extended Audio Description	Where it pauses in the foreground, audio is insufficient to allow audio descriptions to convey the sense of the extended audio description in the video and it should be provided for all pre-recorded video content in synchronized media.	warning	1.2.7 Extended Audio Description (Prerecorded) WCAG 2.0 AAA
418	Media Alternative (Prerecorded)	An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.	warning	1.2.8 Media Alternative (Prerecorded) WCAG 2.0 AAA
402	Audio-only (Live)	Live audio has a media alternative.	warning	1.2.9 Audio-only (Live) WCAG 2.0 AAA
385	Scrollable content can be reached with sequential focus navigation	This rule checks that scrollable elements or their descendants can be reached with sequential focus navigation so that they can be scrolled by keyboard	error	2.1.3 Keyboard (No Exception) WCAG 2.0 AAA
261	Each section of content is marked with a <code>header</code> element.	Using the heading elements h and h1 - h6 to markup the beginning of each section in the content can assist in navigation.	review	2.4.10 Section Headings WCAG 2.0 AAA

WCAG 2.1 A¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA.

Check id	Check name	Description	Type	Success Criteria

352	Links inside text are distinguishable.	Determines if links inside text are sufficiently distinguished from the text	error	1.4.1 Use of Color WCAG 2.1 A
358	Audio Control.	If Multimedia with audible content plays for more than 3 seconds controls must be readily available (for visually impaired people) to shut it down.	warning	1.4.2 Audio Control WCAG 2.1 A
381	Use of Color	Color is not used as the only visual means of conveying information indicating an action prompting a response or distinguishing a visual element.	review	1.4.1 Use of Color WCAG 2.1 A
404	Links inside text are sufficiently distinguishable	This rule looks for links that have adjacent text and compares it to various criteria to determine if it is sufficiently distinguishable from the text.	error	1.4.1 Use of Color WCAG 2.1 A
322	Keyboard shortcuts are implemented in a changeable and safe manner	If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters) punctuation number or symbol characters then at least one of the following is true: \nTurn off \nA mechanism is available to turn the shortcut off; \nRemap \nA mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl Alt etc); \nActive only on focus \nThe keyboard shortcut for a user interface component is only active when that component has focus.	review	2.1.4 Character Key Shortcuts WCAG 2.1 A
311	Content can be operated using simple inputs on a wide range of pointing devices.	All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture unless a multipoint or path-based gesture is essential.	review	2.5.1 Pointer Gestures WCAG 2.1 A
321	Functionality that can be operated using a single pointer is implemented in a safe manner.	For functionality that can be operated using a single pointer at least one of the following is true: No Down-Event The down-event of the pointer is not used to execute any part of the function; Abort or Undo Completion of the function is on the up-event and a mechanism is available to abort the function before completion or to undo the function after completion; Up Reversal The up-event reverses any outcome of the preceding down-event; Essential Completing the function on the down-event is essential.	review	2.5.2 Pointer Cancellation WCAG 2.1 A
323	User interface components with labels that include text or images of text has the text that is presented visually contained in the name.	For user interface components with labels that include text or images of text the name contains the text that is presented visually.	review	2.5.3 Label in Name WCAG 2.1 A
326	Functionality that can be operated by device motion or user motion can also be operated by user interface.	Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation except when: \nSupported Interface \nThe motion is used to operate functionality through an accessibility supported interface; \nEssential \nThe motion is essential for the function and doing so would invalidate the activity.	review	2.5.4 Motion Actuation WCAG 2.1 A
328	Functionality that can be operated by device motion or user motion can be disabled to prevent accidental actuation.	Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation except when: \nSupported Interface \nThe motion is used to operate functionality through an accessibility supported interface; \nEssential \nThe motion is essential for the function and doing so would invalidate the activity.	review	2.5.4 Motion Actuation WCAG 2.1 A
382	All functionality of the content is operable through a keyboard interface	Review that all functionality can be operated by keyboard.	review	2.1.1 Keyboard WCAG 2.1 A
383	Scrollable content can be reached with sequential focus navigation	This rule checks that scrollable elements or their descendants can be reached with sequential focus navigation so that they can be scrolled by keyboard	error	2.1.1 Keyboard WCAG 2.1 A
384	Iframe with interactive elements is not excluded from tab-order	This rule checks that iframe elements which contain an interactive (tabbable) element are not excluded from sequential focus navigation.	error	2.1.1 Keyboard WCAG 2.1 A
386	Keyboard Trap	Review that the keyboard focus is not trapped by any component on the web page.	review	2.1.2 No Keyboard Trap WCAG 2.1 A
422	Meta element has no refresh delay	This rule checks that the first valid meta refresh element on the page is either an instant redirect or has a very long delay (20 hours).	error	2.2.1 Timing Adjustable WCAG 2.1 A
27	<code>blink</code> element is not used.	This error is generated for all <code>blink</code> elements.	error	2.2.2 Pause Stop Hide WCAG 2.1 A
69	<code>marquee</code> element is not used.	This error will be generated for each <code>marquee</code> element.	error	2.2.2 Pause Stop Hide WCAG 2.1 A
71	Auto-redirect must not be used.	<code>meta</code> elements that contain a <code>http-equiv</code> attribute with a value of "refresh" cannot contain a <code>content</code> attribute with a value of (start case insensitive) "http://".	error	2.2.2 Pause Stop Hide WCAG 2.1 A
387	HTML page has non-empty title	This rule checks that a non-embedded HTML page has a non-empty title.	error	2.4.2 Page Titled WCAG 2.1 A
388	HTML page title is descriptive	This rule checks that the first title in an HTML web page describes the topic or purpose of that page.	review	2.4.2 Page Titled WCAG 2.1 A
10	Image is not a flickering GIF.	All <code>img</code> elements that contain a <code>src</code> attribute value that ends with ".gif" (case insensitive) and have a width and height larger than 25 are offered up for review.	review	2.3.1 Three Flashes or Below Threshold WCAG 2.1 A
280	The tab order specified by <code>tabindex</code> attributes follows a logical order.	Provide a logical tab order when the default tab order does not suffice.	review	2.4.3 Focus Order WCAG 2.1 A
173	Suspicious link text.	<code>a</code> (anchor) element cannot contain any of the following text (English): "click here" "more".	warning	2.4.4 Link Purpose (In Context) WCAG 2.1 A
48	Document has required <code>lang</code> attribute(s).	<code>html</code> element must contain a <code>lang</code> attribute.	error	3.1.1 Language of Page WCAG 2.1 A
49	Document has valid language code.	<code>html</code> element must have a <code>lang</code> attribute value of valid 2 or 3 letter language code according to ISO specification 639.	error	3.1.1 Language of Page WCAG 2.1 A
273	Reading order direction is marked using the html element"s <code>dir</code> attribute if the document"s primary language is read right to left.	The dir attribute allows assistive technology to render the content of the page in its intended order.	error	3.1.1 Language of Page WCAG 2.1 A
366	Element with role attribute has required states and properties	This rule checks that elements that have an explicit role also specify all required states and properties.	error	4.1.2 Name Role Value WCAG 2.1 A
367	Form field has non-empty accessible name	This rule checks that each form field element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
368	Menuitem has non-empty accessible name	This rule checks that each menu item element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
369	Element with aria-hidden has no content in sequential focus navigation	This rule checks that no content marked with aria-hidden=true is part of the accessibility tree.	error	4.1.2 Name Role Value WCAG 2.1 A
370	iframe elements with identical accessible names have equivalent purpose	This rule checks that iFrames with the same accessible name have essentially the same purpose and function.	warning	4.1.2 Name Role Value WCAG 2.1 A
371	Link has non-empty accessible name	This rule checks that each link element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
372	Iframe element has non-empty accessible name	This rule checks that each iFrame element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
373	Element with presentational children has no focusable content	This rule checks that each element which should be treated as having only presentational children has no focusable children.	error	4.1.2 Name Role Value WCAG 2.1 A
374	Button has non-empty accessible name	This rule checks that each button element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
405	ARIA state or property is permitted	This rule checks that WAI-ARIA states or properties are allowed for the element they are specified on.	error	4.1.2 Name Role Value WCAG 2.1 A
406	Role attribute has valid value	This rule checks that each role attribute has a valid value.	error	4.1.2 Name Role Value WCAG 2.1 A

WCAG 2.1 AA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A.

Check id	Check name	Description	Type	Success Criteria
184	Sites must have a site map.	Each site must have a site map.	review	2.4.5 Multiple Ways WCAG 2.1 AA
390	Heading is descriptive	This rule checks that headings describe the topic or purpose of the content.	review	2.4.6 Headings and Labels WCAG 2.1 AA
391	Each label describes its associated <code>input</code> element.	Each label must describe its associated <code>input</code> element.	review	2.4.6 Headings and Labels WCAG 2.1 AA
304	Selected link text color must contrast sufficiently with its background color.	The visual presentation of selected link text must have a contrast ratio of at least 4.5:1 except for large-scale text which must have a contrast ratio of at least 3:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.3 Contrast (Minimum) WCAG 2.1 AA
354	Link text color must contrast sufficiently with its background color.	The visual presentation of link text must have a contrast ratio of at least 4.5:1 except for large-scale text which must have a contrast ratio of at least 3:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	error	1.4.3 Contrast (Minimum) WCAG 2.1 AA
364	Text has minimum contrast	This rule checks that the highest possible contrast of every text character with its background meets the minimal contrast requirement.	error	1.4.3 Contrast (Minimum) WCAG 2.1 AA
313	Content is not restricted to a single display orientation.	Orientation Content does not restrict its view and operation to a single display orientation such as portrait or landscape unless a specific display orientation is essential.	review	1.3.4 Orientation WCAG 2.1 AA
316	The purpose of each input field collecting information about the user can be programmatically determined.	The purpose of each input field collecting information about the user can be programmatically determined when: The input field serves a purpose identified in the Input Purposes for User Interface Components section; and The content is implemented using technologies with support for identifying the expected meaning for form input data.	review	1.3.5 Identify Input Purpose WCAG 2.1 AA
251	The luminosity contrast ratio between text and background color in all images is at least 4.5:1.	Make sure that users can read text that is presented over a background.	review	1.4.3 Contrast (Minimum) WCAG 2.1 AA
302	Visited link text color must contrast sufficiently with its background color.	The visual presentation of visited link text must have a contrast ratio of at least 4.5:1 except for large-scale text which must have a contrast ratio of at least 3:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.3 Contrast (Minimum) WCAG 2.1 AA
303	Active link text color must contrast sufficiently with its background color.	The visual presentation of active link text must have a contrast ratio of at least 4.5:1 except for large-scale text which must have a contrast ratio of at least 3:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.3 Contrast (Minimum) WCAG 2.1 AA
315	Scrolling in more than one direction is not necessary for small displays and zoomed content.	Content can be presented without loss of information or functionality and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require a two-dimensional layout for usage or meaning.	review	1.4.10 Reflow WCAG 2.1 AA
350	Scrolling in more than one direction is not necessary for display on mobile phones.	Content should not be wider than the width of a given client (i.e. a mobile phone (simulated)).	warning	1.4.10 Reflow WCAG 2.1 AA
312	The visual presentation of UI and graphics components have a contrast ratio of at least 3:1 against adjacent color(s).	The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components: Visual information required to identify user interface components and states except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; Graphical Objects: Parts of graphics required to understand the content except when a particular presentation of graphics is essential to the information being conveyed.	review	1.4.11 Non-text Contrast WCAG 2.1 AA
317	No loss of content or functionality occurs when changing certain text style properties.	In content implemented using markup languages that support the following text style properties no loss of content or functionality occurs by setting all of the following and by changing no other style property: 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. Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.	review	1.4.12 Text Spacing WCAG 2.1 AA
318	Additional content that appears and disappears in coordination with keyboard focus or pointer hover does not obstruct operation.	Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden the following are true: Dismissable A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus unless the additional content communicates an input error or does not obscure or replace other content; Hoverable If pointer hover can trigger the additional content then the pointer can be moved over the additional content without the additional content disappearing; Persistent The additional content remains visible until the hover or focus trigger is removed the user dismisses it or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.	review	1.4.13 Content on Hover or Focus WCAG 2.1 AA
116	<code>b</code> (bold) element is not used.	This error will be generated for all B elements.	error	1.4.4 Resize text WCAG 2.1 AA
117	<code>i</code> (italic) element is not used.	This error will be generated for all <code>i</code> elements.	error	1.4.4 Resize text WCAG 2.1 AA
176	<code>basefont</code> must not be used.	This error is generated for all <code>basefont</code> elements.	error	1.4.4 Resize text WCAG 2.1 AA
177	<code>font</code> must not be used.	This error is generated for all <code>font</code> elements.	error	1.4.4 Resize text WCAG 2.1 AA
351	Ensure pinch-to-zoom is enabled.	Ensure pinch-to-zoom is enabled.	error	1.4.4 Resize text WCAG 2.1 AA
327	Status messages can be programmatically determined through role or properties.	In content implemented using markup languages status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.	review	4.1.3 Status Messages WCAG 2.1 AA
389	Element in sequential focus order has visible focus	Review if the keyboard focus indicator is visible.	warning	2.4.7 Focus Visible WCAG 2.1 AA

WCAG 2.1 AAA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A
WCAG 2.1 AA.

Check id	Check name	Description	Type	Success Criteria
266	The document contains a breadcrumb trail if it is part of a collection.	Helps the user to visualize how content has been structured and how to navigate back to previous Web units and may identify the current location within a series of Web units.	review	2.4.8 Location WCAG 2.1 AAA
314	The purpose of User Interface Components icons and regions can be programmatically determined.	In content implemented using markup languages the purpose of User Interface Components icons and regions can be programmatically determined.	review	1.3.6 Identify Purpose WCAG 2.1 AAA
319	Users are warned of the duration of any user inactivity that could cause data loss.	Users are warned of the duration of any user inactivity that could cause data loss unless the data is preserved for more than 20 hours when the user does not take any actions.	review	2.2.6 Timeouts WCAG 2.1 AAA
320	Motion animation triggered by interaction can be disabled unless the animation is essential to the functionality or the information being conveyed.	Motion animation triggered by interaction can be disabled unless the animation is essential to the functionality or the information being conveyed.	review	2.3.3 Animation from Interactions WCAG 2.1 AAA
324	The size of the target for pointer inputs is at least 44 by 44 CSS pixels.	The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: \nEquivalent \nThe target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; \nInline \nThe target is in a sentence or block of text; \nUser Agent Control \nThe size of the target is determined by the user agent and is not modified by the author; \nEssential \nA particular presentation of the target is essential to the information being conveyed.	review	2.5.5 Target Size WCAG 2.1 AAA
362	Pointer-interactive elements such as linked icons must be easy to target (Enhanced)	All interactive targets (pointer targets) must take up a minimum of 44x44 CSS pixels of space unless additional criteria are met.	warning	2.5.5 Target Size (Enhanced) WCAG 2.1 AAA
325	Web content does not restrict use of input modalities available on a platform.	Web content does not restrict use of input modalities available on a platform except where the restriction is essential required to ensure the security of the content or required to respect user settings.	review	2.5.6 Concurrent Input Mechanisms WCAG 2.1 AAA
253	The luminosity contrast ratio between text and background color in all images is at least 7:1.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
307	Visited link text color must provide high contrast with its background color.	The visual presentation of visited link text must have a contrast ratio of at least 7:1 except for large-scale text which must have a contrast ratio of at least 4.5:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
308	Active link text color must provide high contrast with its background color.	The visual presentation of active link text must have a contrast ratio of at least 7:1 except for large-scale text which must have a contrast ratio of at least 4.5:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
309	Selected link text color must provide high contrast with its background color.	The visual presentation of selected link text must have a contrast ratio of at least 7:1 except for large-scale text which must have a contrast ratio of at least 4.5:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
356	The contrast between the color of link text and its background is not sufficient to meet WCAG 2.0 Level AAA.	The visual presentation of link text must have a contrast ratio of at least 7:1 except for large-scale text which must have a contrast ratio of at least 4.5:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	error	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
365	Text has enhanced contrast	This rule checks that the highest possible contrast of every text character with its background meets the enhanced contrast requirement.	error	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
179	Provide a reference to a glossary.	If <code>body</code> element content is greater than 10 characters (English) this error will be generated.	review	3.1.3 Unusual Words WCAG 2.1 AAA
98	Abbreviations must be marked with <code>abbr</code> element.	If <code>body</code> element content is greater than 10 characters (English) this error will be generated.	review	3.1.4 Abbreviations WCAG 2.1 AAA
99	Acronyms must be marked with <code>acronym</code> element.	If <code>body</code> element content is greater than 10 characters (English) then this error will be generated.	review	3.1.4 Abbreviations WCAG 2.1 AAA

WCAG 2.2 A¶

There are no new checks for this category.

Checks that may be added in this section will include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A
WCAG 2.1 AA
WCAG 2.1 AAA.

WCAG 2.2 AA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A
WCAG 2.1 AA
WCAG 2.1 AAA
WCAG 2.2 A.

Check id

Check name

Description

Type

Success Criteria

360

Interface components receiving focus are not entirely hidden.

when an interface component receives focus, there must be no author-created content that blocks the view of the component entirely.

review

2.4.11 Focus Not Obscured (Minimum)

WCAG 2.2 AA

345

Any dragging movements required for functionality must have a proper alternative.

If dragging movements are needed (for example to change a slider) an alternative dragging method such as clicking or tapping should be provided.

review

2.5.7 Dragging Movements

WCAG 2.2 AA

WCAG 2.2 AAA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A
WCAG 2.1 AA
WCAG 2.1 AAA
WCAG 2.2 A
WCAG 2.2 AA.

Check id	Check name	Description	Type	Success Criteria
361	No part of interface components receiving focus is hidden.	when an interface component receives focus, there must be no author-created content that blocks the view of the component in any way.	review	2.4.12 Focus Not Obscured (Enhanced) WCAG 2.2 AAA
363	Focus Appearance meets the criteria for conformance.	When receiving keyboard focus; user Interface components must have a minimum focus indication area that contrasts sufficiently with both the colors of the unfocused state and the adjacent colors or meet a criterion for exemption	review	2.4.13 Focus Appearance WCAG 2.2 AAA
359	Authentication Form is accessible for cognitively challenged people (enhanced criterion).	A cognitive function test is not required for any step in an authentication process unless that step provides an alternative accessible to cognitively challenged individuals (stricter options)	warning	3.3.9 Accessible Authentication (Enhanced) WCAG 2.2 AAA

Additional Resources¶

For more information, visit our:

Accessibility Help Center.

For more information, see the external guide:

Understanding the four principles of Accessibility.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Acquia Optimize Support

Introduction¶

This article gives information about the accessibility checks that the scan performs.

The four principles of web accessibility for website content as specified in W3C are:

"Perceivable - Information and user interface components must be presentable to users in ways they can perceive.
This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses).
Operable - User interface components and navigation must be operable.
This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform).
Understandable - Information and the operation of user interface must be understandable.
This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding).
Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible).

If any of these are not true, users with disabilities will not be able to use the Web.”

For more information, see the external guide:

Understanding the four principles of Accessibility.

We prioritize the results of the accessibility checks and places any issues in the following categories:

Error
The issue is in direct conflict with the standard and needs to be fixed.
Warning
The issue is most likely in conflict with the standard, do a manual review and fix the issue.
Review
The issue cannot be programatically determined as an error or warning and requires human review . Do a manual review of the issue to determine if any fix can be done.

For more information, see the user guide article:

Priority, Severity, Difficulty, and Likelihood.

Checklist¶

This section gives instructions on how to find the list of issues in the tool.

Select Checklist (insect icon) from the menu on the left side of the page. This page shows a list of all checks that are done for the selected category.

Select the compliance level to filter for on the Accessibility Checklist page:
- Level A
- Level AA
- Level AAA
- Ignored
- Passed.
  If needed, use the filter to filter the list for:
- Responsibility
- Labels
- Accessibility Error Type.
The results are shown in a table with the following headers:
- Check: This column shows the name and description of the check that is done.
- Responsibility: This column shows the designated team or teams that are normally responsible for fixing this type of error. This column is automatically filled in. The areas of responsibility are:
  - UX Design
  - Front End Development
  - Content Authoring
  - Visual Design.
- Related to Success Criteria: This column shows a list of the compliance success criteria category.
- Help Center: Click to navigate to the Help Center to see the details about the issue and some suggestions on how to fix it.
  For more information, see the user guide article:
  Accessibility Help Center.
- Action Button: This column has a button. Click the button for more options:
- Ignore this check: Issues that are set to Ignore are permanently omitted from future scans and compliance scores.
- Domain Compliance: This column shows the percentage of compliance on this domain.
- Pages: This column lists the number of pages that have the error. Click to navigate to the error page to view:
  - The URL for all of the pages where the error occurs.
  - Suggestions on how to fix the errors.
  - Information about the designated team or competence that is needed to fix this type of error.

WCAG 2.0 A¶

This section lists the checks that are done by the scan for this success criteria selection.

Check id	Check name	Description	Type	Success Criteria
58	All <code>input</code> elements with a <code>type</code> attribute value of "image" have an <code>alt</code> attribute.	<code>input</code> element with <code>type</code> of "image" must have an <code>alt</code> attribute.	error	1.1.1 Non-text Content WCAG 2.0 A
59	Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" identifies the purpose or function of the image.	<code>input</code> element with <code>type</code> of "image" must have Alt text that identifies the purpose or function of the image.	review	1.1.1 Non-text Content WCAG 2.0 A
64	All <code>area</code> elements have an <code>alt</code> attribute.	<code>area</code> elements must contain a <code>alt</code> attribute.	error	1.1.1 Non-text Content WCAG 2.0 A
65	Alt text for all <code>area</code> elements identifies the link destination.	Alt text for <code>area</code> element must describe the link destination.	review	1.1.1 Non-text Content WCAG 2.0 A
193	Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" contains all non-decorative text in the image.	This error is generated for all <code>input</code> elements that have a <code>type</code> of "image".	review	1.1.1 Non-text Content WCAG 2.0 A
194	Alt text for all <code>area</code> elements contains all non-decorative text in the image area.	This error is generated for all <code>area</code> elements.	review	1.1.1 Non-text Content WCAG 2.0 A
375	SVG element with explicit role has non-empty accessible name	This rule checks that each SVG image element that is explicitly included in the accessibility tree has a non-empty accessible name.	error	1.1.1 Non-text Content WCAG 2.0 A
376	Image has non-empty accessible name	This rule checks that each image either has a non-empty accessible name or is marked up as decorative.	error	1.1.1 Non-text Content WCAG 2.0 A
377	<code>object</code> element rendering non-text content has non-empty accessible name	This rule checks that each object element rendering non-text content has a non-empty accessible name.	error	1.1.1 Non-text Content WCAG 2.0 A
378	Image not in the accessibility tree is decorative	This rule checks that visible img svg and canvas elements that are ignored by assistive technologies are decorative.	warning	1.1.1 Non-text Content WCAG 2.0 A
379	Image accessible name is descriptive	This rule checks that the accessible names of images serve an equivalent purpose to the image.	warning	1.1.1 Non-text Content WCAG 2.0 A
380	Image button has non-empty accessible name	This rule checks that each image button element has a non-empty accessible name.	error	1.1.1 Non-text Content WCAG 2.0 A
17	Sound file must have a text transcript.	<code>a</code> (anchor) element cannot contain an <code>href</code> attribute value that ends with any of the following (all case insensitive): .wav .snd .mp3 .iff .svx .sam .smp .vce .vox .pcm .aif.	review	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
20	Links to multimedia require a text transcript.	<code>a</code> (anchor) element must not contain an <code>href</code> attribute value that ends with (case insensitive): .wmv .mpg .mov .ram .aif.	warning	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
66	<code>area</code> link to sound file must have text transcript.	<code>area</code> elements must not contain <code>href</code> attribute values that end with (all case insensitive) .wav .snd .mp3 .iff .svx .sam .smp .vce .vox .pcm .aif	warning	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
393	Video element visual-only content has accessible alternative.	This rule checks that video elements without audio have an alternative available.	warning	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
394	Audio element content has text alternative	This rule checks that audio elements have a text alternative available.	warning	1.2.1 Audio-only and Video-only (Prerecorded) WCAG 2.0 A
395	Video element auditory content has accessible alternative	This rule checks that video elements have an alternative for information conveyed through audio.	warning	1.2.2 Captions (Prerecorded) WCAG 2.0 A
396	<code>object</code> link to multimedia file require equivalent alternatives (e.g. captions or auditory descriptions of the visual track).	If <code>object</code> element contains a <code>type</code> attribute value of "video" then this error will be generated.	review	1.2.3 Audio Description or Media Alternative (Prerecorded) WCAG 2.0 A
397	Video element visual content has accessible alternative	This rule checks that video elements with audio have an alternative for the video content as audio or as text.	warning	1.2.3 Audio Description or Media Alternative (Prerecorded) WCAG 2.0 A
28	A "skip to content" link appears on all pages with blocks of material prior to the main document.	Provide a mechanism to bypass blocks of material that are repeated on multiple Web units.	review	2.4.1 Bypass Blocks WCAG 2.0 A
31	All <code>frames</code> have a <code>title</code> attribute.	Each <code>frame</code> element must have a <code>title</code> attribute.	error	2.4.1 Bypass Blocks WCAG 2.0 A
32	All <code>frame</code> <code>titles</code> identify the purpose or function of the <code>frame</code>.	<code>frame</code> <code>title</code> must describe the purpose or function of the <code>frame</code>.	review	2.4.1 Bypass Blocks WCAG 2.0 A
84	ASCII art should have a skipover link.	ASCII art must have a link immediately preceding it that jumps over the ASCII art. [Editor’s Note - describe how to detect ASCII art. How to detect if a skipover link is already present?]	warning	2.4.1 Bypass Blocks WCAG 2.0 A
262	All groups of links with a related purpose are marked.	When links are grouped into logical sets (for example in a navigation bar or main menu that appears on every page in a site) they should be marked up as a unit.	review	2.4.1 Bypass Blocks WCAG 2.0 A
414	Aria required owned elements	This rule checks that an element with an explicit semantic role has at least one of its required owned elements.	error	1.3.1 Info and Relationships WCAG 2.0 A
415	Table header cell has assigned cells	This rule checks that each table header has assigned cells in a table element.	error	1.3.1 Info and Relationships WCAG 2.0 A
417	Element needs to have the right semantic role	Elements you can click touch or navigate to need to have the right semantic role	warning	1.3.1 Info and Relationships WCAG 2.0 A
421	Heading has non-empty accessible name	This rule checks that each heading element in the document has an accessible name which is not empty.	error	1.3.1 Info and Relationships WCAG 2.0 A
47	All <code>h6</code> elements are not used for formatting.	<code>h6</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
82	All <code>p</code> elements are not used as headers.	All <code>p</code> element content must not be marked with either <code>b</code> <code>i</code> <code>u</code> <code>strong</code> <code>font</code> <code>em</code>.	warning	1.3.1 Info and Relationships WCAG 2.0 A
112	All data <code>table</code> summaries contain text.	<code>table</code> element cannot contain an empty <code>summary</code> attribute if it"s a data <code>table</code>.	error	1.3.1 Info and Relationships WCAG 2.0 A
114	All layout <code>tables</code> have an empty <code>summary</code> attribute or no <code>summary</code> attribute.	The <code>table</code> element <code>summary</code> attribute for all layout tables contains no printable characters or is absent.	error	1.3.1 Info and Relationships WCAG 2.0 A
42	All <code>h1</code> elements are not used for formatting.	<code>h1</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
43	All <code>h2</code> elements are not used for formatting.	<code>h2</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
44	All <code>h3</code> elements are not used for formatting.	<code>h3</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
45	All <code>h4</code> elements are not used for formatting.	<code>h4</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
115	All layout tables do not contain <code>caption</code> elements.	<code>table</code> element content cannot contain a <code>caption</code> element if it"s a layout <code>table</code>.	error	1.3.1 Info and Relationships WCAG 2.0 A
154	<code>pre</code> element should not be used to create tabular layout.	This error is generated for each <code>pre</code> element.	review	1.3.1 Info and Relationships WCAG 2.0 A
203	All data table summaries describe navigation and structure of the table.	The <code>table</code> summary can"t be garbage text.	review	1.3.1 Info and Relationships WCAG 2.0 A
241	Table markup is used for all tabular information.	The objective of this technique is to present tabular information in a way that preserves relationships within the information even when users cannot see the table or the presentation format is changed.	review	1.3.1 Info and Relationships WCAG 2.0 A
242	Table captions identify the table.	If the table has a caption then the caption must identify the table.	review	1.3.1 Info and Relationships WCAG 2.0 A
243	Table summaries do not duplicate the table captions.	The summary and the caption must be different. Caption identifies the table. Summary describes the table contents.	error	1.3.1 Info and Relationships WCAG 2.0 A
245	Data tables that contain more than one row/column of headers use the <code>id</code> and <code>headers</code> attributes to identify cells.	id and headers attributes allow screen readers to speak the headers associated with each data cell when the relationships are too complex to be identified using the th element alone or the th element with the scope attribute.	error	1.3.1 Info and Relationships WCAG 2.0 A
248	All visual lists are marked.	Create lists of related items using list elements appropriate for their purposes.	review	1.3.1 Info and Relationships WCAG 2.0 A
407	ARIA attribute is defined in WAI-ARIA	This rule checks that each aria- attribute specified is defined in ARIA 1.2.	error	1.3.1 Info and Relationships WCAG 2.0 A
408	Aria state or property has valid value	This rule checks that each ARIA state or property has a valid value type.	error	1.3.1 Info and Relationships WCAG 2.0 A
409	ARIA required context role	This rule checks that an element with an explicit semantic role exists inside its required context.	error	1.3.1 Info and Relationships WCAG 2.0 A
410	ARIA required ID references exist	This rule checks that every ID reference required by WAI-ARIA exists	error	1.3.1 Info and Relationships WCAG 2.0 A
411	Use a quote element to mark up quotations.	Review that the quotations in your text are within relevant quote elements to ensure that users of assistive technology can easily identify quotations.	warning	1.3.1 Info and Relationships WCAG 2.0 A
412	Non-decorative content in pseudo classes	The “::before” and “::after” pseudo classes contains non-decorative content.	error	1.3.1 Info and Relationships WCAG 2.0 A
413	Headers attribute specified on a cell refers to cells in the same table element	This rule checks that all headers attributes in cells of a given table refers to ids of cells within that same table.	error	1.3.1 Info and Relationships WCAG 2.0 A
46	All <code>h5</code> elements are not used for formatting.	<code>h5</code> may be used for formatting. Use the proper markup.	review	1.3.1 Info and Relationships WCAG 2.0 A
210	All <code>select</code> elements have a label that describes the purpose or function of the control.	All <code>select</code> elements have a label that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
211	All <code>input</code> elements <code>type</code> of "text" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "text" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
217	All <code>input</code> elements <code>type</code> of "password" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "password" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
218	All <code>input</code> elements <code>type</code> of "text" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "text" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
219	All <code>input</code> elements <code>type</code> of "checkbox" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "checkbox" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
220	All <code>input</code> elements <code>type</code> of "radio" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "radio" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
246	All <code>form</code> fields that are required are indicated to the user as required.	Ensure that the label for any interactive component within Web content makes the purpose of the component clear.	review	3.3.2 Labels or Instructions WCAG 2.0 A
392	Each label associated with an <code>input</code> element contains text.	Label must contain some text.	error	3.3.2 Labels or Instructions WCAG 2.0 A
133	All layout <code>tables</code> make sense when linearized.	This error is generated for all layout <code>tables</code>. If the <code>table</code> contains <code>th</code> elements then it is a data <code>table</code>. If the <code>table</code> does not contain <code>th</code> elements then it is a layout <code>table</code>.	review	1.3.2 Meaningful Sequence WCAG 2.0 A
398	HTML layout tables should make sense when linearized	If layout tables are used it is important that the content makes sense when linearized	warning	1.3.2 Meaningful Sequence WCAG 2.0 A
399	Using white space characters to control spacing within a word	White space characters such as space tab line break or carriage return are not used to format individual words visually.	error	1.3.2 Meaningful Sequence WCAG 2.0 A
400	Using white space characters to create multiple columns or to format tables in plain text content	White space characters such as space tab line break or carriage return are not used to create columns or format tables in plain text.	error	1.3.2 Meaningful Sequence WCAG 2.0 A
416	Changing the meaning of content by positioning information with CSS.	CSS rather than structural markup is used to modify the visual layout of the content and the modified layout changes the meaning of the content.	review	1.3.2 Meaningful Sequence WCAG 2.0 A
250	Sensory Characteristics.	Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.	review	1.3.3 Sensory Characteristics WCAG 2.0 A
275	Loading the web page does not cause a new window to open.	Pages do not disorient users by opening up one or more new windows as soon as a page is loaded.	review	3.2.1 On Focus WCAG 2.0 A
68	<code>area</code> should not open a new window without warning.	<code>area</code> element <code>target</code> attribute values must contain any one of (case insensitive) _self _top _parent.	warning	3.2.2 On Input WCAG 2.0 A
92	All <code>select</code> elements do not cause an extreme change in context.	<code>select</code> element cannot contain <code>onchange</code> attribute.	warning	3.2.2 On Input WCAG 2.0 A
267	All form submission error messages identify any empty required fields.	Helps the user to visualize how content has been structured and how to navigate back to previous Web units and may identify the current location within a series of Web units.	review	3.3.1 Error Identification WCAG 2.0 A
96	All <code>textarea</code> elements have a label that is positioned close to control.	<code>textarea</code> element must have an associated <code>label</code> element that is positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
122	All <code>input</code> elements <code>type</code> of "password" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "password" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
123	All <code>input</code> elements <code>type</code> of "checkbox" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "checkbox" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
124	All <code>input</code> elements <code>type</code> of "file" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "file" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
125	All <code>input</code> elements <code>type</code> of "radio" have a label that is positioned close to the control.	<code>input</code> element with a <code>type</code> attribute value of "radio" must have an associated <code>label</code> element positioned close to it.	review	3.3.2 Labels or Instructions WCAG 2.0 A
187	Each <code>input</code> element has only one associated <code>label</code>.	<code>input</code> element must have only one associated <code>label</code> element.	error	3.3.2 Labels or Instructions WCAG 2.0 A
205	All <code>input</code> elements <code>type</code> of "file" have a <code>label</code> that describes the purpose or function of the control.	All <code>input</code> elements <code>type</code> of "file" have a <code>label</code> that describes the purpose or function of the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A
209	All <code>select</code> elements have a label that is positioned close to the control.	All <code>select</code> elements have a label that is positioned close to the control.	review	3.3.2 Labels or Instructions WCAG 2.0 A

WCAG 2.0 AA¶

Checks in this section include all checks from the previous category:

WCAG 2.0 A.

Check id	Check name	Description	Type	Success Criteria
263	Repeated blocks of content appear in the same <code>frame</code> within the <code>frameset</code>.	Framesets can be used to group blocks of repeated material.	review	3.2.3 Consistent Navigation WCAG 2.0 AA
401	Captions (Live)	Live video has captions.	warning	1.2.4 Captions (Live) WCAG 2.0 AA
276	Repeated components appear in the same relative order each time they appear.	Maintain consistent layout or presentation between Web units by presenting components that are repeated in these Web units in the same relative order each time they appear. Other components can be inserted between them but their relative order is not changed.	review	3.2.3 Consistent Navigation WCAG 2.0 AA
81	List items must not be used to format text.	OL element should not contain only one LI element.	warning	3.2.4 Consistent Identification WCAG 2.0 AA
100	<code>blockquote</code> must not be used for indentation.	This error is generated if any <code>blockquote</code> element is missing a <code>cite</code> attribute.	review	3.2.4 Consistent Identification WCAG 2.0 AA
268	All form submission error messages provide assistance in correcting the error.	Information about the nature and location of the input error is provided in text to enable the users to identify the problem.	review	3.3.3 Error Suggestion WCAG 2.0 AA
269	Form submission data is presented to the user before final acceptance for all irreversible transactions.	Provide users with a way to ensure their input is correct before completing an irreversible transaction.	review	3.3.4 Error Prevention (Legal Financial Data) WCAG 2.0 AA

WCAG 2.0 AAA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA.

Check id	Check name	Description	Type	Success Criteria
272	Information deleted using a web page can be recovered.	Help users with disabilities avoid serious consequences as the result of a mistake when performing an action that cannot be reversed.	review	3.3.6 Error Prevention (All) WCAG 2.0 AAA
18	Anchor should not open a new window without warning.	<code>a</code> (anchor) element must not contain a <code>target</code> attribute unless the <code>target</code> attribute value is either _self _top or _parent.	warning	3.2.5 Change on Request WCAG 2.0 AAA
274	Change of context occurs only by user activation unless a warning is provided.	Provide a method for activating things that is predictable by the user.	review	3.2.5 Change on Request WCAG 2.0 AAA
420	Sign Language (Prerecorded)	Sign language interpretation is provided for all prerecorded audio content in synchronized media.	warning	1.2.6 Sign Language (Prerecorded) WCAG 2.0 AAA
419	Extended Audio Description	Where it pauses in the foreground, audio is insufficient to allow audio descriptions to convey the sense of the extended audio description in the video and it should be provided for all pre-recorded video content in synchronized media.	warning	1.2.7 Extended Audio Description (Prerecorded) WCAG 2.0 AAA
418	Media Alternative (Prerecorded)	An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.	warning	1.2.8 Media Alternative (Prerecorded) WCAG 2.0 AAA
402	Audio-only (Live)	Live audio has a media alternative.	warning	1.2.9 Audio-only (Live) WCAG 2.0 AAA
385	Scrollable content can be reached with sequential focus navigation	This rule checks that scrollable elements or their descendants can be reached with sequential focus navigation so that they can be scrolled by keyboard	error	2.1.3 Keyboard (No Exception) WCAG 2.0 AAA
261	Each section of content is marked with a <code>header</code> element.	Using the heading elements h and h1 - h6 to markup the beginning of each section in the content can assist in navigation.	review	2.4.10 Section Headings WCAG 2.0 AAA

WCAG 2.1 A¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA.

Check id	Check name	Description	Type	Success Criteria

352	Links inside text are distinguishable.	Determines if links inside text are sufficiently distinguished from the text	error	1.4.1 Use of Color WCAG 2.1 A
358	Audio Control.	If Multimedia with audible content plays for more than 3 seconds controls must be readily available (for visually impaired people) to shut it down.	warning	1.4.2 Audio Control WCAG 2.1 A
381	Use of Color	Color is not used as the only visual means of conveying information indicating an action prompting a response or distinguishing a visual element.	review	1.4.1 Use of Color WCAG 2.1 A
404	Links inside text are sufficiently distinguishable	This rule looks for links that have adjacent text and compares it to various criteria to determine if it is sufficiently distinguishable from the text.	error	1.4.1 Use of Color WCAG 2.1 A
322	Keyboard shortcuts are implemented in a changeable and safe manner	If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters) punctuation number or symbol characters then at least one of the following is true: \nTurn off \nA mechanism is available to turn the shortcut off; \nRemap \nA mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl Alt etc); \nActive only on focus \nThe keyboard shortcut for a user interface component is only active when that component has focus.	review	2.1.4 Character Key Shortcuts WCAG 2.1 A
311	Content can be operated using simple inputs on a wide range of pointing devices.	All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture unless a multipoint or path-based gesture is essential.	review	2.5.1 Pointer Gestures WCAG 2.1 A
321	Functionality that can be operated using a single pointer is implemented in a safe manner.	For functionality that can be operated using a single pointer at least one of the following is true: No Down-Event The down-event of the pointer is not used to execute any part of the function; Abort or Undo Completion of the function is on the up-event and a mechanism is available to abort the function before completion or to undo the function after completion; Up Reversal The up-event reverses any outcome of the preceding down-event; Essential Completing the function on the down-event is essential.	review	2.5.2 Pointer Cancellation WCAG 2.1 A
323	User interface components with labels that include text or images of text has the text that is presented visually contained in the name.	For user interface components with labels that include text or images of text the name contains the text that is presented visually.	review	2.5.3 Label in Name WCAG 2.1 A
326	Functionality that can be operated by device motion or user motion can also be operated by user interface.	Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation except when: \nSupported Interface \nThe motion is used to operate functionality through an accessibility supported interface; \nEssential \nThe motion is essential for the function and doing so would invalidate the activity.	review	2.5.4 Motion Actuation WCAG 2.1 A
328	Functionality that can be operated by device motion or user motion can be disabled to prevent accidental actuation.	Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation except when: \nSupported Interface \nThe motion is used to operate functionality through an accessibility supported interface; \nEssential \nThe motion is essential for the function and doing so would invalidate the activity.	review	2.5.4 Motion Actuation WCAG 2.1 A
382	All functionality of the content is operable through a keyboard interface	Review that all functionality can be operated by keyboard.	review	2.1.1 Keyboard WCAG 2.1 A
383	Scrollable content can be reached with sequential focus navigation	This rule checks that scrollable elements or their descendants can be reached with sequential focus navigation so that they can be scrolled by keyboard	error	2.1.1 Keyboard WCAG 2.1 A
384	Iframe with interactive elements is not excluded from tab-order	This rule checks that iframe elements which contain an interactive (tabbable) element are not excluded from sequential focus navigation.	error	2.1.1 Keyboard WCAG 2.1 A
386	Keyboard Trap	Review that the keyboard focus is not trapped by any component on the web page.	review	2.1.2 No Keyboard Trap WCAG 2.1 A
422	Meta element has no refresh delay	This rule checks that the first valid meta refresh element on the page is either an instant redirect or has a very long delay (20 hours).	error	2.2.1 Timing Adjustable WCAG 2.1 A
27	<code>blink</code> element is not used.	This error is generated for all <code>blink</code> elements.	error	2.2.2 Pause Stop Hide WCAG 2.1 A
69	<code>marquee</code> element is not used.	This error will be generated for each <code>marquee</code> element.	error	2.2.2 Pause Stop Hide WCAG 2.1 A
71	Auto-redirect must not be used.	<code>meta</code> elements that contain a <code>http-equiv</code> attribute with a value of "refresh" cannot contain a <code>content</code> attribute with a value of (start case insensitive) "http://".	error	2.2.2 Pause Stop Hide WCAG 2.1 A
387	HTML page has non-empty title	This rule checks that a non-embedded HTML page has a non-empty title.	error	2.4.2 Page Titled WCAG 2.1 A
388	HTML page title is descriptive	This rule checks that the first title in an HTML web page describes the topic or purpose of that page.	review	2.4.2 Page Titled WCAG 2.1 A
10	Image is not a flickering GIF.	All <code>img</code> elements that contain a <code>src</code> attribute value that ends with ".gif" (case insensitive) and have a width and height larger than 25 are offered up for review.	review	2.3.1 Three Flashes or Below Threshold WCAG 2.1 A
280	The tab order specified by <code>tabindex</code> attributes follows a logical order.	Provide a logical tab order when the default tab order does not suffice.	review	2.4.3 Focus Order WCAG 2.1 A
173	Suspicious link text.	<code>a</code> (anchor) element cannot contain any of the following text (English): "click here" "more".	warning	2.4.4 Link Purpose (In Context) WCAG 2.1 A
48	Document has required <code>lang</code> attribute(s).	<code>html</code> element must contain a <code>lang</code> attribute.	error	3.1.1 Language of Page WCAG 2.1 A
49	Document has valid language code.	<code>html</code> element must have a <code>lang</code> attribute value of valid 2 or 3 letter language code according to ISO specification 639.	error	3.1.1 Language of Page WCAG 2.1 A
273	Reading order direction is marked using the html element"s <code>dir</code> attribute if the document"s primary language is read right to left.	The dir attribute allows assistive technology to render the content of the page in its intended order.	error	3.1.1 Language of Page WCAG 2.1 A
366	Element with role attribute has required states and properties	This rule checks that elements that have an explicit role also specify all required states and properties.	error	4.1.2 Name Role Value WCAG 2.1 A
367	Form field has non-empty accessible name	This rule checks that each form field element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
368	Menuitem has non-empty accessible name	This rule checks that each menu item element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
369	Element with aria-hidden has no content in sequential focus navigation	This rule checks that no content marked with aria-hidden=true is part of the accessibility tree.	error	4.1.2 Name Role Value WCAG 2.1 A
370	iframe elements with identical accessible names have equivalent purpose	This rule checks that iFrames with the same accessible name have essentially the same purpose and function.	warning	4.1.2 Name Role Value WCAG 2.1 A
371	Link has non-empty accessible name	This rule checks that each link element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
372	Iframe element has non-empty accessible name	This rule checks that each iFrame element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
373	Element with presentational children has no focusable content	This rule checks that each element which should be treated as having only presentational children has no focusable children.	error	4.1.2 Name Role Value WCAG 2.1 A
374	Button has non-empty accessible name	This rule checks that each button element has a non-empty accessible name.	error	4.1.2 Name Role Value WCAG 2.1 A
405	ARIA state or property is permitted	This rule checks that WAI-ARIA states or properties are allowed for the element they are specified on.	error	4.1.2 Name Role Value WCAG 2.1 A
406	Role attribute has valid value	This rule checks that each role attribute has a valid value.	error	4.1.2 Name Role Value WCAG 2.1 A

WCAG 2.1 AA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A.

Check id	Check name	Description	Type	Success Criteria
184	Sites must have a site map.	Each site must have a site map.	review	2.4.5 Multiple Ways WCAG 2.1 AA
390	Heading is descriptive	This rule checks that headings describe the topic or purpose of the content.	review	2.4.6 Headings and Labels WCAG 2.1 AA
391	Each label describes its associated <code>input</code> element.	Each label must describe its associated <code>input</code> element.	review	2.4.6 Headings and Labels WCAG 2.1 AA
304	Selected link text color must contrast sufficiently with its background color.	The visual presentation of selected link text must have a contrast ratio of at least 4.5:1 except for large-scale text which must have a contrast ratio of at least 3:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.3 Contrast (Minimum) WCAG 2.1 AA
354	Link text color must contrast sufficiently with its background color.	The visual presentation of link text must have a contrast ratio of at least 4.5:1 except for large-scale text which must have a contrast ratio of at least 3:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	error	1.4.3 Contrast (Minimum) WCAG 2.1 AA
364	Text has minimum contrast	This rule checks that the highest possible contrast of every text character with its background meets the minimal contrast requirement.	error	1.4.3 Contrast (Minimum) WCAG 2.1 AA
313	Content is not restricted to a single display orientation.	Orientation Content does not restrict its view and operation to a single display orientation such as portrait or landscape unless a specific display orientation is essential.	review	1.3.4 Orientation WCAG 2.1 AA
316	The purpose of each input field collecting information about the user can be programmatically determined.	The purpose of each input field collecting information about the user can be programmatically determined when: The input field serves a purpose identified in the Input Purposes for User Interface Components section; and The content is implemented using technologies with support for identifying the expected meaning for form input data.	review	1.3.5 Identify Input Purpose WCAG 2.1 AA
251	The luminosity contrast ratio between text and background color in all images is at least 4.5:1.	Make sure that users can read text that is presented over a background.	review	1.4.3 Contrast (Minimum) WCAG 2.1 AA
302	Visited link text color must contrast sufficiently with its background color.	The visual presentation of visited link text must have a contrast ratio of at least 4.5:1 except for large-scale text which must have a contrast ratio of at least 3:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.3 Contrast (Minimum) WCAG 2.1 AA
303	Active link text color must contrast sufficiently with its background color.	The visual presentation of active link text must have a contrast ratio of at least 4.5:1 except for large-scale text which must have a contrast ratio of at least 3:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.3 Contrast (Minimum) WCAG 2.1 AA
315	Scrolling in more than one direction is not necessary for small displays and zoomed content.	Content can be presented without loss of information or functionality and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require a two-dimensional layout for usage or meaning.	review	1.4.10 Reflow WCAG 2.1 AA
350	Scrolling in more than one direction is not necessary for display on mobile phones.	Content should not be wider than the width of a given client (i.e. a mobile phone (simulated)).	warning	1.4.10 Reflow WCAG 2.1 AA
312	The visual presentation of UI and graphics components have a contrast ratio of at least 3:1 against adjacent color(s).	The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components: Visual information required to identify user interface components and states except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; Graphical Objects: Parts of graphics required to understand the content except when a particular presentation of graphics is essential to the information being conveyed.	review	1.4.11 Non-text Contrast WCAG 2.1 AA
317	No loss of content or functionality occurs when changing certain text style properties.	In content implemented using markup languages that support the following text style properties no loss of content or functionality occurs by setting all of the following and by changing no other style property: 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. Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.	review	1.4.12 Text Spacing WCAG 2.1 AA
318	Additional content that appears and disappears in coordination with keyboard focus or pointer hover does not obstruct operation.	Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden the following are true: Dismissable A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus unless the additional content communicates an input error or does not obscure or replace other content; Hoverable If pointer hover can trigger the additional content then the pointer can be moved over the additional content without the additional content disappearing; Persistent The additional content remains visible until the hover or focus trigger is removed the user dismisses it or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.	review	1.4.13 Content on Hover or Focus WCAG 2.1 AA
116	<code>b</code> (bold) element is not used.	This error will be generated for all B elements.	error	1.4.4 Resize text WCAG 2.1 AA
117	<code>i</code> (italic) element is not used.	This error will be generated for all <code>i</code> elements.	error	1.4.4 Resize text WCAG 2.1 AA
176	<code>basefont</code> must not be used.	This error is generated for all <code>basefont</code> elements.	error	1.4.4 Resize text WCAG 2.1 AA
177	<code>font</code> must not be used.	This error is generated for all <code>font</code> elements.	error	1.4.4 Resize text WCAG 2.1 AA
351	Ensure pinch-to-zoom is enabled.	Ensure pinch-to-zoom is enabled.	error	1.4.4 Resize text WCAG 2.1 AA
327	Status messages can be programmatically determined through role or properties.	In content implemented using markup languages status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.	review	4.1.3 Status Messages WCAG 2.1 AA
389	Element in sequential focus order has visible focus	Review if the keyboard focus indicator is visible.	warning	2.4.7 Focus Visible WCAG 2.1 AA

WCAG 2.1 AAA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A
WCAG 2.1 AA.

Check id	Check name	Description	Type	Success Criteria
266	The document contains a breadcrumb trail if it is part of a collection.	Helps the user to visualize how content has been structured and how to navigate back to previous Web units and may identify the current location within a series of Web units.	review	2.4.8 Location WCAG 2.1 AAA
314	The purpose of User Interface Components icons and regions can be programmatically determined.	In content implemented using markup languages the purpose of User Interface Components icons and regions can be programmatically determined.	review	1.3.6 Identify Purpose WCAG 2.1 AAA
319	Users are warned of the duration of any user inactivity that could cause data loss.	Users are warned of the duration of any user inactivity that could cause data loss unless the data is preserved for more than 20 hours when the user does not take any actions.	review	2.2.6 Timeouts WCAG 2.1 AAA
320	Motion animation triggered by interaction can be disabled unless the animation is essential to the functionality or the information being conveyed.	Motion animation triggered by interaction can be disabled unless the animation is essential to the functionality or the information being conveyed.	review	2.3.3 Animation from Interactions WCAG 2.1 AAA
324	The size of the target for pointer inputs is at least 44 by 44 CSS pixels.	The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: \nEquivalent \nThe target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; \nInline \nThe target is in a sentence or block of text; \nUser Agent Control \nThe size of the target is determined by the user agent and is not modified by the author; \nEssential \nA particular presentation of the target is essential to the information being conveyed.	review	2.5.5 Target Size WCAG 2.1 AAA
362	Pointer-interactive elements such as linked icons must be easy to target (Enhanced)	All interactive targets (pointer targets) must take up a minimum of 44x44 CSS pixels of space unless additional criteria are met.	warning	2.5.5 Target Size (Enhanced) WCAG 2.1 AAA
325	Web content does not restrict use of input modalities available on a platform.	Web content does not restrict use of input modalities available on a platform except where the restriction is essential required to ensure the security of the content or required to respect user settings.	review	2.5.6 Concurrent Input Mechanisms WCAG 2.1 AAA
253	The luminosity contrast ratio between text and background color in all images is at least 7:1.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
307	Visited link text color must provide high contrast with its background color.	The visual presentation of visited link text must have a contrast ratio of at least 7:1 except for large-scale text which must have a contrast ratio of at least 4.5:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
308	Active link text color must provide high contrast with its background color.	The visual presentation of active link text must have a contrast ratio of at least 7:1 except for large-scale text which must have a contrast ratio of at least 4.5:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
309	Selected link text color must provide high contrast with its background color.	The visual presentation of selected link text must have a contrast ratio of at least 7:1 except for large-scale text which must have a contrast ratio of at least 4.5:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	review	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
356	The contrast between the color of link text and its background is not sufficient to meet WCAG 2.0 Level AAA.	The visual presentation of link text must have a contrast ratio of at least 7:1 except for large-scale text which must have a contrast ratio of at least 4.5:1 as determined by a contrast algorithm specified by WCAG 2.0. Large scale text is considered to be at least 18-point (or 14 point when bold).	error	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
365	Text has enhanced contrast	This rule checks that the highest possible contrast of every text character with its background meets the enhanced contrast requirement.	error	1.4.6 Contrast (Enhanced) WCAG 2.1 AAA
179	Provide a reference to a glossary.	If <code>body</code> element content is greater than 10 characters (English) this error will be generated.	review	3.1.3 Unusual Words WCAG 2.1 AAA
98	Abbreviations must be marked with <code>abbr</code> element.	If <code>body</code> element content is greater than 10 characters (English) this error will be generated.	review	3.1.4 Abbreviations WCAG 2.1 AAA
99	Acronyms must be marked with <code>acronym</code> element.	If <code>body</code> element content is greater than 10 characters (English) then this error will be generated.	review	3.1.4 Abbreviations WCAG 2.1 AAA

WCAG 2.2 A¶

There are no new checks for this category.

Checks that may be added in this section will include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A
WCAG 2.1 AA
WCAG 2.1 AAA.

WCAG 2.2 AA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A
WCAG 2.1 AA
WCAG 2.1 AAA
WCAG 2.2 A.

Check id

Check name

Description

Type

Success Criteria

360

Interface components receiving focus are not entirely hidden.

when an interface component receives focus, there must be no author-created content that blocks the view of the component entirely.

review

2.4.11 Focus Not Obscured (Minimum)

WCAG 2.2 AA

345

Any dragging movements required for functionality must have a proper alternative.

If dragging movements are needed (for example to change a slider) an alternative dragging method such as clicking or tapping should be provided.

review

2.5.7 Dragging Movements

WCAG 2.2 AA

WCAG 2.2 AAA¶

Checks in this section include all checks from the previous categories:

WCAG 2.0 A
WCAG 2.0 AA
WCAG 2.0 AAA
WCAG 2.1 A
WCAG 2.1 AA
WCAG 2.1 AAA
WCAG 2.2 A
WCAG 2.2 AA.

Check id	Check name	Description	Type	Success Criteria
361	No part of interface components receiving focus is hidden.	when an interface component receives focus, there must be no author-created content that blocks the view of the component in any way.	review	2.4.12 Focus Not Obscured (Enhanced) WCAG 2.2 AAA
363	Focus Appearance meets the criteria for conformance.	When receiving keyboard focus; user Interface components must have a minimum focus indication area that contrasts sufficiently with both the colors of the unfocused state and the adjacent colors or meet a criterion for exemption	review	2.4.13 Focus Appearance WCAG 2.2 AAA
359	Authentication Form is accessible for cognitively challenged people (enhanced criterion).	A cognitive function test is not required for any step in an authentication process unless that step provides an alternative accessible to cognitively challenged individuals (stricter options)	warning	3.3.9 Accessible Authentication (Enhanced) WCAG 2.2 AAA

Additional Resources¶

For more information, visit our:

Accessibility Help Center.

For more information, see the external guide:

Understanding the four principles of Accessibility.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Acquia Optimize Support