Accessibility checks

Docs

Blue teardrop shape with two overlapping white rectangles inside.

Web Governance

Introduction

This article provides 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, visit Understanding the four principles of Accessibility.

The scan prioritizes 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 programmatically 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, visit Issue priority.

Checklist

This section provides 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 displayed 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, visit Accessibility guide.
- 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 displays the percentage of compliance on this domain.
- Pages: This column displays 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 provides a list of the checks that are done by the scan for this success criteria selection.

Check id	Check name	Description	Type	Success Criteria
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 that renders 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.	This rule states that `<code>a</code>`, or anchor, elements do not contain an `<code>href</code>` attribute value that ends with any of the following, all are 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.	This rule states that `<code>a</code>`, or anchor, elements must not contain an <code>href</code> attribute value that ends with any of the following, all are 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.	This rule states that `<code>area</code>` elements must not contain `<code>href</code>` attribute values that end with the following, all are 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).	This rule generates an error if the `<code>object</code>` element contains a `<code>type</code>` attribute value of "video".	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
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
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.	The `<code>table</code>` element cannot contain an empty `<code>summary</code>` attribute if it is 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
115	All layout tables do not contain <code>caption</code> elements.	The `<code>table</code>` element content cannot contain a `<code>caption</code>` element if it is 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 cannot 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 header 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 contain 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
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

WCAG 2.0 AA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

WCAG 2.0 A.

Check id	Check name	Description	Type	Success Criteria
401	Captions (Live)	Live video has captions.	warning	1.2.4 Captions (Live) 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

WCAG 2.0 AAA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
420	Sign Language (Prerecorded)	Sign language interpretation is provided for all pre-recorded 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 pre-recorded synchronized media and for all pre-recorded 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
18	Anchor should not open a new window without warning.	a `<code>a</code>`, or 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
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

WCAG 2.1 A

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
447	Covers multimedia alternatives	All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.		1.1.1 Non-text content
446	All heading elements are not used for formatting	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.		1.3.1 Sensory Characteristics
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
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
423	Bypass Blocks	A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.		2.4.1 Bypass Blocks
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
460	Links with identical accessible names and same context serve equivalent purpose	The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.		2.4.4 Link Purpose (In Context)
470	Visible label is part of accessible name	For user interface components with labels that include text or images of text, the name contains the text that is presented visually.		2.5.3 Label in Name
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
451	HTML page lang attribute has valid language tag	The default human language of each Web page can be programmatically determined.		3.1.1 Language of Page
434	Document has required lang attribute(s)	The default human language of each Web page can be programmatically determined.		3.1.1 Language of Page
467	An input error is described to the user in text.	If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.		3.3.1 Error Identification
473	Labels or instructions are provided when content requires user input	Labels or instructions are provided when content requires user input.		3.3.2 Labels or Instructions
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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
430	Video has audio description	Audio description is provided for all prerecorded video content in synchronized media.		1.2.5 Audio Description (Prerecorded)
452	Orientation of the page is not restricted using CSS transform property	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.		1.3.4 Orientation
431	Ensure input fields with autocomplete attributes align with their intended purpose.	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	review	1.3.5 Identify Input Purpose
455	Autocomplete attribute has valid value	The purpose of each input field collecting information about the user can be programmatically determined when: The content is implemented using technologies with support for identifying the expected meaning for form input data.	review	1.3.5 Identify Input Purpose
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)
438	Link text color must contrast sufficiently with its background color.	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
440	Text has minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
442	Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
444	Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
478	No change of context when receiving focus	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (Minimum)
453	Meta viewport allows for zoom	Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.		1.4.4 Resize text
466	Images of text	If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable The image of text can be visually customized to the user's requirements; Essential A particular presentation of text is essential to the information being conveyed.		1.4.5 Images of text
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 such as 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 the adjacent color: 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
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
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
454	Element with lang attribute has valid language tag	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.		3.1.2 Language of Parts
472	The local language attribute matches the actual language	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.		3.1.2 Language of Parts
468	All form submission error messages provide assistance in correcting the error.	If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.		3.3.3 Error Suggestion
469	Form submission data is presented to the user before final acceptance for all irreversible transactions.	For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible Submissions are reversible. Checked Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.		3.3.4 Error Prevention (Legal, Financial, Data)
448	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.		4.1.3 Status Messages

WCAG 2.1 AAA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
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
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)
439	The contrast between the color of link text and its background is not sufficient to meet WCAG 2.0 Level AAA.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
441	Text has enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
443	Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
445	Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
479	Link text color in user induced states must meet enhanced contrast or better with its background colour.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
449	Low or no background audio	For pre-recorded, audio-only content that contains primarily speech in the foreground is not an audio CAPTCHA or audio logo is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: No Background The audio does not contain background sounds. Turn Off The background sounds can be turned off. 20 dB The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.		1.4.7 Low or No Background Audio
465	Text is justified	For the visual presentation of blocks of text, a mechanism is available to achieve the following: Text is not justified, that is, aligned to both the left and the right margins.		1.4.8 Visual Presentation
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
476	Links with identical accessible names have equivalent purpose	A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.		2.4.9 Link Purpose (Link Only)
477	Pointer-interactive elements, such as linked icons, must be easy to target (extended)	The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline The target is in a sentence or block of text; User Agent Control The size of the target is determined by the user agent and is not modified by the author; Essential A particular presentation of the target is essential to the information being conveyed.		2.5.5 Target Size
471	Abbreviations must be described	A mechanism for identifying the expanded form or meaning of abbreviations is available.		3.1.4 Abbreviations
475	Context-sensitive help is available for forms	Context-sensitive help is available.		3.3.5 Help

WCAG 2.2 A

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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, which are stricter options.	warning	3.3.9 Accessible Authentication (Enhanced) WCAG 2.2 AAA

Additional resources

For more information, visit Accessibility guide

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.

Introduction

This article provides 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, visit Understanding the four principles of Accessibility.

The scan prioritizes 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 programmatically 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, visit Issue priority.

Checklist

This section provides 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 displayed 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, visit Accessibility guide.
- 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 displays the percentage of compliance on this domain.
- Pages: This column displays 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 provides a list of the checks that are done by the scan for this success criteria selection.

Check id	Check name	Description	Type	Success Criteria
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 that renders 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.	This rule states that `<code>a</code>`, or anchor, elements do not contain an `<code>href</code>` attribute value that ends with any of the following, all are 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.	This rule states that `<code>a</code>`, or anchor, elements must not contain an <code>href</code> attribute value that ends with any of the following, all are 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.	This rule states that `<code>area</code>` elements must not contain `<code>href</code>` attribute values that end with the following, all are 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).	This rule generates an error if the `<code>object</code>` element contains a `<code>type</code>` attribute value of "video".	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
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
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.	The `<code>table</code>` element cannot contain an empty `<code>summary</code>` attribute if it is 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
115	All layout tables do not contain <code>caption</code> elements.	The `<code>table</code>` element content cannot contain a `<code>caption</code>` element if it is 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 cannot 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 header 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 contain 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
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

WCAG 2.0 AA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

WCAG 2.0 A.

Check id	Check name	Description	Type	Success Criteria
401	Captions (Live)	Live video has captions.	warning	1.2.4 Captions (Live) 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

WCAG 2.0 AAA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
420	Sign Language (Prerecorded)	Sign language interpretation is provided for all pre-recorded 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 pre-recorded synchronized media and for all pre-recorded 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
18	Anchor should not open a new window without warning.	a `<code>a</code>`, or 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
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

WCAG 2.1 A

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
447	Covers multimedia alternatives	All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.		1.1.1 Non-text content
446	All heading elements are not used for formatting	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.		1.3.1 Sensory Characteristics
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
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
423	Bypass Blocks	A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.		2.4.1 Bypass Blocks
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
460	Links with identical accessible names and same context serve equivalent purpose	The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.		2.4.4 Link Purpose (In Context)
470	Visible label is part of accessible name	For user interface components with labels that include text or images of text, the name contains the text that is presented visually.		2.5.3 Label in Name
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
451	HTML page lang attribute has valid language tag	The default human language of each Web page can be programmatically determined.		3.1.1 Language of Page
434	Document has required lang attribute(s)	The default human language of each Web page can be programmatically determined.		3.1.1 Language of Page
467	An input error is described to the user in text.	If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.		3.3.1 Error Identification
473	Labels or instructions are provided when content requires user input	Labels or instructions are provided when content requires user input.		3.3.2 Labels or Instructions
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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
430	Video has audio description	Audio description is provided for all prerecorded video content in synchronized media.		1.2.5 Audio Description (Prerecorded)
452	Orientation of the page is not restricted using CSS transform property	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.		1.3.4 Orientation
431	Ensure input fields with autocomplete attributes align with their intended purpose.	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	review	1.3.5 Identify Input Purpose
455	Autocomplete attribute has valid value	The purpose of each input field collecting information about the user can be programmatically determined when: The content is implemented using technologies with support for identifying the expected meaning for form input data.	review	1.3.5 Identify Input Purpose
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)
438	Link text color must contrast sufficiently with its background color.	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
440	Text has minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
442	Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
444	Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
478	No change of context when receiving focus	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (Minimum)
453	Meta viewport allows for zoom	Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.		1.4.4 Resize text
466	Images of text	If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable The image of text can be visually customized to the user's requirements; Essential A particular presentation of text is essential to the information being conveyed.		1.4.5 Images of text
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 such as 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 the adjacent color: 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
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
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
454	Element with lang attribute has valid language tag	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.		3.1.2 Language of Parts
472	The local language attribute matches the actual language	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.		3.1.2 Language of Parts
468	All form submission error messages provide assistance in correcting the error.	If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.		3.3.3 Error Suggestion
469	Form submission data is presented to the user before final acceptance for all irreversible transactions.	For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible Submissions are reversible. Checked Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.		3.3.4 Error Prevention (Legal, Financial, Data)
448	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.		4.1.3 Status Messages

WCAG 2.1 AAA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
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
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)
439	The contrast between the color of link text and its background is not sufficient to meet WCAG 2.0 Level AAA.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
441	Text has enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
443	Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
445	Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
479	Link text color in user induced states must meet enhanced contrast or better with its background colour.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
449	Low or no background audio	For pre-recorded, audio-only content that contains primarily speech in the foreground is not an audio CAPTCHA or audio logo is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: No Background The audio does not contain background sounds. Turn Off The background sounds can be turned off. 20 dB The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.		1.4.7 Low or No Background Audio
465	Text is justified	For the visual presentation of blocks of text, a mechanism is available to achieve the following: Text is not justified, that is, aligned to both the left and the right margins.		1.4.8 Visual Presentation
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
476	Links with identical accessible names have equivalent purpose	A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.		2.4.9 Link Purpose (Link Only)
477	Pointer-interactive elements, such as linked icons, must be easy to target (extended)	The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline The target is in a sentence or block of text; User Agent Control The size of the target is determined by the user agent and is not modified by the author; Essential A particular presentation of the target is essential to the information being conveyed.		2.5.5 Target Size
471	Abbreviations must be described	A mechanism for identifying the expanded form or meaning of abbreviations is available.		3.1.4 Abbreviations
475	Context-sensitive help is available for forms	Context-sensitive help is available.		3.3.5 Help

WCAG 2.2 A

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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, which are stricter options.	warning	3.3.9 Accessible Authentication (Enhanced) WCAG 2.2 AAA

Additional resources

For more information, visit Accessibility guide

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.

Introduction

This article provides 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, visit Understanding the four principles of Accessibility.

The scan prioritizes 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 programmatically 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, visit Issue priority.

Checklist

This section provides 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 displayed 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, visit Accessibility guide.
- 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 displays the percentage of compliance on this domain.
- Pages: This column displays 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 provides a list of the checks that are done by the scan for this success criteria selection.

Check id	Check name	Description	Type	Success Criteria
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 that renders 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.	This rule states that `<code>a</code>`, or anchor, elements do not contain an `<code>href</code>` attribute value that ends with any of the following, all are 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.	This rule states that `<code>a</code>`, or anchor, elements must not contain an <code>href</code> attribute value that ends with any of the following, all are 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.	This rule states that `<code>area</code>` elements must not contain `<code>href</code>` attribute values that end with the following, all are 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).	This rule generates an error if the `<code>object</code>` element contains a `<code>type</code>` attribute value of "video".	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
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
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.	The `<code>table</code>` element cannot contain an empty `<code>summary</code>` attribute if it is 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
115	All layout tables do not contain <code>caption</code> elements.	The `<code>table</code>` element content cannot contain a `<code>caption</code>` element if it is 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 cannot 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 header 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 contain 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
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

WCAG 2.0 AA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

WCAG 2.0 A.

Check id	Check name	Description	Type	Success Criteria
401	Captions (Live)	Live video has captions.	warning	1.2.4 Captions (Live) 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

WCAG 2.0 AAA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
420	Sign Language (Prerecorded)	Sign language interpretation is provided for all pre-recorded 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 pre-recorded synchronized media and for all pre-recorded 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
18	Anchor should not open a new window without warning.	a `<code>a</code>`, or 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
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

WCAG 2.1 A

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
447	Covers multimedia alternatives	All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.		1.1.1 Non-text content
446	All heading elements are not used for formatting	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.		1.3.1 Sensory Characteristics
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
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
423	Bypass Blocks	A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.		2.4.1 Bypass Blocks
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
460	Links with identical accessible names and same context serve equivalent purpose	The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.		2.4.4 Link Purpose (In Context)
470	Visible label is part of accessible name	For user interface components with labels that include text or images of text, the name contains the text that is presented visually.		2.5.3 Label in Name
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
451	HTML page lang attribute has valid language tag	The default human language of each Web page can be programmatically determined.		3.1.1 Language of Page
434	Document has required lang attribute(s)	The default human language of each Web page can be programmatically determined.		3.1.1 Language of Page
467	An input error is described to the user in text.	If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.		3.3.1 Error Identification
473	Labels or instructions are provided when content requires user input	Labels or instructions are provided when content requires user input.		3.3.2 Labels or Instructions
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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
430	Video has audio description	Audio description is provided for all prerecorded video content in synchronized media.		1.2.5 Audio Description (Prerecorded)
452	Orientation of the page is not restricted using CSS transform property	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.		1.3.4 Orientation
431	Ensure input fields with autocomplete attributes align with their intended purpose.	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	review	1.3.5 Identify Input Purpose
455	Autocomplete attribute has valid value	The purpose of each input field collecting information about the user can be programmatically determined when: The content is implemented using technologies with support for identifying the expected meaning for form input data.	review	1.3.5 Identify Input Purpose
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)
438	Link text color must contrast sufficiently with its background color.	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
440	Text has minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
442	Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
444	Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
478	No change of context when receiving focus	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (Minimum)
453	Meta viewport allows for zoom	Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.		1.4.4 Resize text
466	Images of text	If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable The image of text can be visually customized to the user's requirements; Essential A particular presentation of text is essential to the information being conveyed.		1.4.5 Images of text
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 such as 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 the adjacent color: 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
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
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
454	Element with lang attribute has valid language tag	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.		3.1.2 Language of Parts
472	The local language attribute matches the actual language	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.		3.1.2 Language of Parts
468	All form submission error messages provide assistance in correcting the error.	If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.		3.3.3 Error Suggestion
469	Form submission data is presented to the user before final acceptance for all irreversible transactions.	For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible Submissions are reversible. Checked Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.		3.3.4 Error Prevention (Legal, Financial, Data)
448	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.		4.1.3 Status Messages

WCAG 2.1 AAA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
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
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)
439	The contrast between the color of link text and its background is not sufficient to meet WCAG 2.0 Level AAA.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
441	Text has enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
443	Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
445	Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
479	Link text color in user induced states must meet enhanced contrast or better with its background colour.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
449	Low or no background audio	For pre-recorded, audio-only content that contains primarily speech in the foreground is not an audio CAPTCHA or audio logo is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: No Background The audio does not contain background sounds. Turn Off The background sounds can be turned off. 20 dB The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.		1.4.7 Low or No Background Audio
465	Text is justified	For the visual presentation of blocks of text, a mechanism is available to achieve the following: Text is not justified, that is, aligned to both the left and the right margins.		1.4.8 Visual Presentation
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
476	Links with identical accessible names have equivalent purpose	A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.		2.4.9 Link Purpose (Link Only)
477	Pointer-interactive elements, such as linked icons, must be easy to target (extended)	The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline The target is in a sentence or block of text; User Agent Control The size of the target is determined by the user agent and is not modified by the author; Essential A particular presentation of the target is essential to the information being conveyed.		2.5.5 Target Size
471	Abbreviations must be described	A mechanism for identifying the expanded form or meaning of abbreviations is available.		3.1.4 Abbreviations
475	Context-sensitive help is available for forms	Context-sensitive help is available.		3.3.5 Help

WCAG 2.2 A

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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, which are stricter options.	warning	3.3.9 Accessible Authentication (Enhanced) WCAG 2.2 AAA

Additional resources

For more information, visit Accessibility guide

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.

Introduction

This article provides 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, visit Understanding the four principles of Accessibility.

The scan prioritizes 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 programmatically 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, visit Issue priority.

Checklist

This section provides 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 displayed 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, visit Accessibility guide.
- 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 displays the percentage of compliance on this domain.
- Pages: This column displays 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 provides a list of the checks that are done by the scan for this success criteria selection.

Check id	Check name	Description	Type	Success Criteria
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 that renders 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.	This rule states that `<code>a</code>`, or anchor, elements do not contain an `<code>href</code>` attribute value that ends with any of the following, all are 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.	This rule states that `<code>a</code>`, or anchor, elements must not contain an <code>href</code> attribute value that ends with any of the following, all are 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.	This rule states that `<code>area</code>` elements must not contain `<code>href</code>` attribute values that end with the following, all are 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).	This rule generates an error if the `<code>object</code>` element contains a `<code>type</code>` attribute value of "video".	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
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
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.	The `<code>table</code>` element cannot contain an empty `<code>summary</code>` attribute if it is 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
115	All layout tables do not contain <code>caption</code> elements.	The `<code>table</code>` element content cannot contain a `<code>caption</code>` element if it is 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 cannot 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 header 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 contain 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
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

WCAG 2.0 AA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

WCAG 2.0 A.

Check id	Check name	Description	Type	Success Criteria
401	Captions (Live)	Live video has captions.	warning	1.2.4 Captions (Live) 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

WCAG 2.0 AAA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
420	Sign Language (Prerecorded)	Sign language interpretation is provided for all pre-recorded 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 pre-recorded synchronized media and for all pre-recorded 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
18	Anchor should not open a new window without warning.	a `<code>a</code>`, or 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
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

WCAG 2.1 A

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
447	Covers multimedia alternatives	All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.		1.1.1 Non-text content
446	All heading elements are not used for formatting	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.		1.3.1 Sensory Characteristics
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
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
423	Bypass Blocks	A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.		2.4.1 Bypass Blocks
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
460	Links with identical accessible names and same context serve equivalent purpose	The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.		2.4.4 Link Purpose (In Context)
470	Visible label is part of accessible name	For user interface components with labels that include text or images of text, the name contains the text that is presented visually.		2.5.3 Label in Name
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
451	HTML page lang attribute has valid language tag	The default human language of each Web page can be programmatically determined.		3.1.1 Language of Page
434	Document has required lang attribute(s)	The default human language of each Web page can be programmatically determined.		3.1.1 Language of Page
467	An input error is described to the user in text.	If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.		3.3.1 Error Identification
473	Labels or instructions are provided when content requires user input	Labels or instructions are provided when content requires user input.		3.3.2 Labels or Instructions
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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
430	Video has audio description	Audio description is provided for all prerecorded video content in synchronized media.		1.2.5 Audio Description (Prerecorded)
452	Orientation of the page is not restricted using CSS transform property	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.		1.3.4 Orientation
431	Ensure input fields with autocomplete attributes align with their intended purpose.	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	review	1.3.5 Identify Input Purpose
455	Autocomplete attribute has valid value	The purpose of each input field collecting information about the user can be programmatically determined when: The content is implemented using technologies with support for identifying the expected meaning for form input data.	review	1.3.5 Identify Input Purpose
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)
438	Link text color must contrast sufficiently with its background color.	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
440	Text has minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
442	Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
444	Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (minimum)
478	No change of context when receiving focus	Make sure that users can read text that is presented over a background.		1.4.3 Contrast (Minimum)
453	Meta viewport allows for zoom	Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.		1.4.4 Resize text
466	Images of text	If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable The image of text can be visually customized to the user's requirements; Essential A particular presentation of text is essential to the information being conveyed.		1.4.5 Images of text
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 such as 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 the adjacent color: 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
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
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
454	Element with lang attribute has valid language tag	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.		3.1.2 Language of Parts
472	The local language attribute matches the actual language	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.		3.1.2 Language of Parts
468	All form submission error messages provide assistance in correcting the error.	If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.		3.3.3 Error Suggestion
469	Form submission data is presented to the user before final acceptance for all irreversible transactions.	For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible Submissions are reversible. Checked Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.		3.3.4 Error Prevention (Legal, Financial, Data)
448	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.		4.1.3 Status Messages

WCAG 2.1 AAA

This section provides a list of the checks that are done by the scan for this success criteria selection.

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
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
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)
439	The contrast between the color of link text and its background is not sufficient to meet WCAG 2.0 Level AAA.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
441	Text has enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
443	Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
445	Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
479	Link text color in user induced states must meet enhanced contrast or better with its background colour.	Make sure that users can read text that is presented over a background.	review	1.4.6 Contrast (Enhanced)
449	Low or no background audio	For pre-recorded, audio-only content that contains primarily speech in the foreground is not an audio CAPTCHA or audio logo is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: No Background The audio does not contain background sounds. Turn Off The background sounds can be turned off. 20 dB The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.		1.4.7 Low or No Background Audio
465	Text is justified	For the visual presentation of blocks of text, a mechanism is available to achieve the following: Text is not justified, that is, aligned to both the left and the right margins.		1.4.8 Visual Presentation
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
476	Links with identical accessible names have equivalent purpose	A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.		2.4.9 Link Purpose (Link Only)
477	Pointer-interactive elements, such as linked icons, must be easy to target (extended)	The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline The target is in a sentence or block of text; User Agent Control The size of the target is determined by the user agent and is not modified by the author; Essential A particular presentation of the target is essential to the information being conveyed.		2.5.5 Target Size
471	Abbreviations must be described	A mechanism for identifying the expanded form or meaning of abbreviations is available.		3.1.4 Abbreviations
475	Context-sensitive help is available for forms	Context-sensitive help is available.		3.3.5 Help

WCAG 2.2 A

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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

This section provides a list of the checks that are done by the scan for this success criteria selection.

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, which are stricter options.	warning	3.3.9 Accessible Authentication (Enhanced) WCAG 2.2 AAA

Additional resources

For more information, visit Accessibility guide

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.

Accessibility checks

Introduction

Checklist

WCAG 2.0 A

WCAG 2.0 AA

WCAG 2.0 AAA

WCAG 2.1 A

WCAG 2.1 AA

431

WCAG 2.1 AAA

WCAG 2.2 A

WCAG 2.2 AA

WCAG 2.2 AAA

Additional resources

Did not find what you were looking for?

Accessibility checks

Introduction

Checklist

WCAG 2.0 A

WCAG 2.0 AA

WCAG 2.0 AAA

WCAG 2.1 A

WCAG 2.1 AA

431

WCAG 2.1 AAA

WCAG 2.2 A

WCAG 2.2 AA

WCAG 2.2 AAA

Additional resources

Did not find what you were looking for?

Accessibility checks

Introduction

Checklist

WCAG 2.0 A

WCAG 2.0 AA

WCAG 2.0 AAA

WCAG 2.1 A

WCAG 2.1 AA

431

WCAG 2.1 AAA

WCAG 2.2 A

WCAG 2.2 AA

WCAG 2.2 AAA

Additional resources

Frequently asked questions

Is it possible to be 100% compliant with accessibility?

What Is Web Accessibility?

How can I repair accessibility issues with the Web Governance web browser extension?

What is the Accessibility Guide?

Did not find what you were looking for?

Accessibility checks

Introduction

Checklist

WCAG 2.0 A

WCAG 2.0 AA

WCAG 2.0 AAA

WCAG 2.1 A

WCAG 2.1 AA

431

WCAG 2.1 AAA

WCAG 2.2 A

WCAG 2.2 AA

WCAG 2.2 AAA

Additional resources

Frequently asked questions

Is it possible to be 100% compliant with accessibility?

What Is Web Accessibility?

How can I repair accessibility issues with the Web Governance web browser extension?

What is the Accessibility Guide?

Did not find what you were looking for?

Frequently asked questions

Is it possible to be 100% compliant with accessibility?

What Is Web Accessibility?

How can I repair accessibility issues with the Web Governance web browser extension?

What is the Accessibility Guide?

Frequently asked questions

Is it possible to be 100% compliant with accessibility?

What Is Web Accessibility?

How can I repair accessibility issues with the Web Governance web browser extension?

What is the Accessibility Guide?