All Collections
Accessibility
Accessibility Checks
Accessibility Checks

A list of the accessibility checks done for each WCAG level

Updated this week

This chapter gives information about the accessibility checks that Monsido performs.

Article Navigation


Introduction

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

  • "Perceivable - Information and user interface components must be presentable to users in ways they can perceive.

    This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses).

  • Operable - User interface components and navigation must be operable.

    This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform).

  • Understandable - Information and the operation of user interface must be understandable.

    This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding).

  • Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

    This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible).

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

For more information, see the external guide:

Monsido 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 programatically determined as an error or warning and requires human review . Do a manual review of the issue to determine if any fix can be done.

For more information, see the User Guide chapter:


Checklist

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

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

The location of the Checklist option on the left menu.

Select the compliance level to filter for on the Accessibility Checklist page:

  • Level A

  • Level AA

  • Level AAA

  • Ignored

  • Passed.

Filter the list for:

  • Responsibility

  • Labels

  • Accessibility Error Type.

The results are shown in a table with the following headers:

  • Check: This column shows the name and description of the check that is done.

  • Responsibility: This column shows the designated team or teams that are normally responsible for fixing this type of error. This column is automatically filled in by Monsido. The areas of responsibility are:

    • UX Design

    • Front End Development

    • Content Authoring

    • Visual Design.

  • Related to Success Criteria: This column shows a list of the compliance success criteria category.

  • Help Center: Click to navigate to the Help Center to see the details about the issue and some suggestions on how to fix it.
    For more information, see the User Guide chapter:

  • Action Button: This column has a button. Click the button for more options:

    • Ignore this check: Issues that are set to Ignore are permanently omitted from future scans and compliance scores.

  • Domain Compliance: This column shows the percentage of compliance on this domain.

  • Pages: This column lists the number of pages that have the error. Click to navigate to the error page to view:

    • The URL for all of the pages where the error occurs.

    • Suggestions on how to fix the errors.

    • Information about the designated team or competence that is needed to fix this type of error.


WCAG 2.0

Principle 1: Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Level

Subgroup Identification

Rule

A

1.1

Text Alternatives: Provide text alternatives for all non-text content

A

Subgroup 1.1.1

Non-text Content

1.2

Time-based Media: Provide alternatives for time-based media

A

Subgroup 1.2.1

Audio-only and Video-only (Prerecorded)

A

Subgroup 1.2.2

Captions (Prerecorded)

A

Subgroup 1.2.3

Audio Description or Media Alternative (Prerecorded)

AA

Subgroup 1.2.4

Captions (Live)

AA

Subgroup 1.2.5

Audio Description (Prerecorded)

AAA

Subgroup 1.2.6

Sign Language (Prerecorded)

AAA

Subgroup 1.2.7

Extended Audio Description (Prerecorded)

AAA

Subgroup 1.2.8

Media Alternative (Prerecorded)

AAA

Subgroup 1.2.9

Audio-only (Live)

1.3

Adaptable: Create content that can be presented in different ways without losing information or structure.

A

Subgroup 1.3.1

Info and Relationships

A

Subgroup 1.3.2

Meaningful Sequence

A

Subgroup 1.3.3

Sensory Characteristics

1.4

Distinguishable: Make it easier for users to see and hear content including separating foreground from background.

A

Subgroup 1.4.1

Use of Colour

A

Subgroup 1.4.2

Audio Control

AA

Subgroup 1.4.3

Contrast (Minimum)

AA

Subgroup 1.4.4

Resize text

AAA

Subgroup 1.4.6

Contrast (Enhanced)

AAA

Subgroup 1.4.7

Low or No Background Audio

AAA

Subgroup 1.4.8

Visual Presentation

AAA

Subgroup 1.4.9

Images of Text (No Exception)


Principle 2: Operable

User interface components and navigation must be operable.

Level

Subgroup Identification

Rule

2.1

Keyboard Accessible: Make all functionality available from a keyboard.

A

Subgroup 2.1.1

Keyboard

A

Subgroup 2.1.2

No Keyboard Trap

AAA

Subgroup 2.1.3

Keyboard (No Exception)

2.2

Enough Time: Provide users enough time to read and use content.

A

Subgroup 2.2.1

Timing Adjustable

A

Subgroup 2.2.2

Pause, Stop, Hide

AAA

Subgroup 2.2.3

No Timing

AAA

Subgroup 2.2.4

Interruptions

AAA

Subgroup 2.2.5

Re-authenticating

2.3

Seizures: Do not design content in a way that is known to cause seizures.

A

Subgroup 2.3.1

Three Flashes or Below Threshold

AAA

Subgroup 2.3.2

Three Flashes

2.4

Navigable: Provide ways to help users navigate, find content, and determine where they are.

A

Subgroup 2.4.1

Bypass Blocks

AAA

Subgroup 2.4.10

Section Headings

A

Subgroup 2.4.2

Page Titled

A

Subgroup 2.4.3

Focus Order

A

Subgroup 2.4.4

Link Purpose (In Context)

AA

Subgroup 2.4.5

Multiple Ways

AA

Subgroup 2.4.6

Headings and Labels

AA

Subgroup 2.4.7

Focus Visible

AAA

Subgroup 2.4.8

Location

AAA

Subgroup 2.4.9

Link Purpose (Link Only)


Principle 3: Understandable

Information and the operation of user interface must be understandable.

Level

Subgroup Identification

Rule

3.1

Readable: Make text content readable and understandable

A

Subgroup 3.1.1

Language of Page

AA

Subgroup 3.1.2

Language of Parts

AAA

Subgroup 3.1.3

Unusual Words

AAA

Subgroup 3.1.4

Abbreviations

AAA

Subgroup 3.1.5

Reading Level

AAA

Subgroup 3.1.6

Pronunciation

3.2

Predictable: Make Web pages appear and operate in predictable ways.

A

Subgroup 3.2.1

On Focus

A

Subgroup 3.2.2

On Input

AA

Subgroup 3.2.3

Consistent Navigation

AA

Subgroup 3.2.4

Consistent Identification

AAA

Subgroup 3.2.5

Change on Request

3.3

Input Assistance: Help users avoid and correct mistakes.

A

Subgroup 3.3.1

Error Identification

AA

Subgroup 3.3.3

Error Suggestion

AA

Subgroup 3.3.4

Error Prevention (Legal, Financial, Data)

AAA

Subgroup 3.3.5

Help

AAA

Subgroup 3.3.6

Error Prevention (All)


Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

A warning in this category means that the site does not meet the requirements for compatibility with current and future user agents, including assistive technologies.

Level

Subgroup Identification

Rule

A

Subgroup 4.1.1

Parsing

A

Subgroup 4.1.2

Name, Role, Value


WCAG 2.1

Principle 1: Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Level

Subgroup Identification

Rule

1.1

A

Subgroup 1.1.1

All img elements have an alt attribute

A

Subgroup 1.1.1

Image Alt text is short

A

Subgroup 1.1.1

Alt text for all img elements is not placeholder text unless author has confirmed it is correct

A

Subgroup 1.1.1

Alt text for all img elements used as source anchors is not empty when there is no other text in the anchor

A

Subgroup 1.1.1

A long description is used for each img element that does not have Alt text conveying the same information as the image

A

Subgroup 1.1.1

Alt text for all img elements is the empty string ("""") if the image is decorative

A

Subgroup 1.1.1

Applet contains a text equivalent in the alt attribute of the applet.

A

Subgroup 1.1.1

Text equivalents for applet must be updated if applet changes

A

Subgroup 1.1.1

Applet contains a text equivalent in the body of the applet

A

Subgroup 1.1.1

All input elements with a type attribute value of ""image"" have an alt attribute

A

Subgroup 1.1.1

Alt text for all input elements with a type attribute value of ""image"" identifies the purpose or function of the image.

A

Subgroup 1.1.1

Alt text for all input elements with a type attribute value of ""image"" is less than 100 characters (English) or the user has confirmed that the Alt text is as short as possible

A

Subgroup 1.1.1

Image used in input element - Alt text should not be placeholder text

A

Subgroup 1.1.1

All area elements have an alt attribute

A

Subgroup 1.1.1

Alt text for all area elements identifies the link destination

A

Subgroup 1.1.1

Area link to sound file must have text transcript

A

Subgroup 1.1.1

All objects contain a text equivalent of the object

A

Subgroup 1.1.1

All embed elements have an associated noembed element that contains a text equivalent to the embed element

A

Subgroup 1.1.1

Alt text for all img elements that are not used as source anchors conveys the same information as the image

A

Subgroup 1.1.1

Alt text for all input elements with a type attribute value of ""image"" contains all non-decorative text in the image

A

Subgroup 1.1.1

Alt text for all area elements contains all non-decorative text in the image area

A

Subgroup 1.1.1

All input elements, except those with with a type attribute value of ""image"", do not have an alt attribute

A

Subgroup 1.1.1

Title attribute for all img elements is absent or the empty string ("""") if the image is decorative

A

Subgroup 1.1.1

Alt text should not be part of the filename

1.2

A

Subgroup 1.2.1

Sound file must have a text transcript

A

Subgroup 1.2.1

Links to multimedia require a text transcript

A

Subgroup 1.2.1

Links to multimedia have a link to text alternative

A

Subgroup 1.2.3

Object link to multimedia file require equivalent alternatives (Such as captions or auditory descriptions of the visual track)

A

Subgroup 1.2.3

Object may require a long description

1.3

A

Subgroup 1.3.1

All input elements, type of ""text"", have an explicitly associated label

A

Subgroup 1.3.1

All p elements are not used as headers

A

Subgroup 1.3.1

All select elements have an explicitly associated label

A

Subgroup 1.3.1

All textarea elements have an explicitly associated label

A

Subgroup 1.3.1

All textarea elements have a label that is positioned close to control

A

Subgroup 1.3.1

All complex data tables have a summary

A

Subgroup 1.3.1

All data table summaries contain text

A

Subgroup 1.3.1

All layout tables have an empty summary attribute or no summary attribute

A

Subgroup 1.3.1

All layout tables do not contain caption elements

A

Subgroup 1.3.1

All input elements, type of ""password"", have an explicitly associated label

A

Subgroup 1.3.1

All input elements, type of ""checkbox"", have an explicitly associated label

A

Subgroup 1.3.1

All input elements, type of ""file"", have an explicitly associated label

A

Subgroup 1.3.1

All input elements, type of ""radio"", have an explicitly associated label

A

Subgroup 1.3.1

All input elements, type of ""password"", have a label that is positioned close to the control

A

Subgroup 1.3.1

All input elements, type of ""checkbox"", have a label that is positioned close to the control

A

Subgroup 1.3.1

All input elements, type of ""file"", have a label that is positioned close to the control

A

Subgroup 1.3.1

All input elements, type of ""radio"", have a label that is positioned close to the control

A

Subgroup 1.3.1

All data tables contain th elements

A

Subgroup 1.3.1

All layout tables do not contain th elements

A

Subgroup 1.3.1

All data tables contain a caption unless the table is identified within the document

A

Subgroup 1.3.1

pre element should not be used to create tabular layout

A

Subgroup 1.3.1

All radio button groups are marked using fieldset and legend elements

A

Subgroup 1.3.1

All data table summaries describe navigation and structure of the table

A

Subgroup 1.3.1

All input elements, type of ""radio"", have a label containing text

A

Subgroup 1.3.1

All input elements, type of ""checkbox"", have a label containing text

A

Subgroup 1.3.1

All input elements, type of ""password"", have a label containing text

A

Subgroup 1.3.1

All select elements have a label that contains text

A

Subgroup 1.3.1

All select elements have a label that is positioned close to the control

A

Subgroup 1.3.1

All input elements, type of ""text"", have a label that is positioned close to the control.

A

Subgroup 1.3.1

All textarea elements have a label containing text

A

Subgroup 1.3.1

All input elements, type of ""text"", have a label containing text

A

Subgroup 1.3.1

All input elements, type of ""file"", have a label containing text

A

Subgroup 1.3.1

Use thead to group repeated table headers, tfoot for repeated table footers, and tbody for other groups of rows

A

Subgroup 1.3.1

Use colgroup and col elements to group columns.

A

Subgroup 1.3.1

Table markup is used for all tabular information

A

Subgroup 1.3.1

Table captions identify the table

A

Subgroup 1.3.1

Table summaries do not duplicate the table caption

A

Subgroup 1.3.1

Data tables that contain more than one row/column of headers use the id and headers attributes to identify cells

A

Subgroup 1.3.1

All checkbox groups are marked using fieldset and legend elements

A

Subgroup 1.3.1

All visual lists are marked

A

Subgroup 1.3.1

Unicode right-to-left marks or left-to-right marks are used whenever the HTML bidirectional algorithm produces undesirable results

A

Subgroup 1.3.1

All changes in text direction are marked using the dir attribute

A

Subgroup 1.3.1

Data tables that contain both row and column headers use the scope attribute, or id and headers, to identify cells

A

Subgroup 1.3.3

All layout tables make sense when linearized.

A

Subgroup 1.3.3

Sensory Characteristics

AA

Subgroup 1.3.4

Content is not restricted to a single display orientation

AA

Subgroup 1.3.5

The purpose of each input field collecting information about the user can be programmatically determined

1.4

A

Subgroup 1.4.1

For all img elements, text does not refer to the image by color alone

A

Subgroup 1.4.1

Applet should not use color alone

A

Subgroup 1.4.1

Input should not use color alone

A

Subgroup 1.4.1

object must not use color alone

A

Subgroup 1.4.1

Color alone should not be used in the script

A

Subgroup 1.4.1

All text colors or no text colors are set

A

Subgroup 1.4.1

Links inside text are distinguishable

AA

Subgroup 1.4.10

Scrolling in more than one direction is not necessary for display on mobile phones.

AA

Subgroup 1.4.11

The visual presentation of UI and graphics components have a contrast ratio of at least 3:1 against adjacent color(s)

AA

Subgroup 1.4.12

No loss of content or functionality occurs when changing certain text style properties

AA

Subgroup 1.4.13

Additional content that appears and disappears in coordination with keyboard focus or pointer hover does not obstruct operation

A

Subgroup 1.4.2

Autoplaying audible Multimedia can be shut down

AA

Subgroup 1.4.3

The luminosity contrast ratio between text and background color in all images is at least 4.5:1

AA

Subgroup 1.4.3

Visited link text color must contrast sufficiently with its background color

AA

Subgroup 1.4.3

Active link text color must contrast sufficiently with its background color

AA

Subgroup 1.4.3

Selected link text color must contrast sufficiently with its background color

AA

Subgroup 1.4.3

Provide sufficient contrast between text and background colors

AA

Subgroup 1.4.3

Link text color must contrast sufficiently with its background color

AA

Subgroup 1.4.4

b (bold) element is not used

AA

Subgroup 1.4.4

i (italic) element is not used

AA

Subgroup 1.4.4

Basefont must not be used

AA

Subgroup 1.4.4

Font must not be used

AA

Subgroup 1.4.4

Ensure pinch-to-zoom is enabled

A

Subgroup 1.4.5

Alt text for all img elements contains all text in the image unless the image text is decorative or appears elsewhere in the document


Principle 2: Operable

User interface components and navigation must be operable.

Level

Subgroup Identification

Rule

2.1

A

Subgroup 2.1.1

Applet user interface must be accessible

A

Subgroup 2.1.1

Object user interface must be accessible - (codebase)

A

Subgroup 2.1.1

User interface for script must be accessible

A

Subgroup 2.1.1

All ondblclick event handlers have corresponding keyboard-specific functions

A

Subgroup 2.1.1

All onmousedown event handlers have an associated onkeydown event handler

A

Subgroup 2.1.1

All onmousemove event handlers have corresponding keyboard-specific functions

A

Subgroup 2.1.1

All onmouseout event handlers have an associated onblur event handler

A

Subgroup 2.1.1

All onmouseover event handlers have an associated onfocus event handler

A

Subgroup 2.1.1

All onmouseup event handlers have an associated onkeyup event handler

A

Subgroup 2.1.2

Applet provides a keyboard mechanism to return focus to the parent window

A

Subgroup 2.1.2

Object provides a keyboard mechanism to return focus to the parent window

A

Subgroup 2.1.2

Embed provides a keyboard mechanism to return focus to the parent window

A

Subgroup 2.1.4

Keyboard shortcuts are implemented in a changeable and safe manner

2.2

A

Subgroup 2.2.2

Meta refresh is not used with a time-out

A

Subgroup 2.2.2

Blink element is not used

A

Subgroup 2.2.2

Marquee element is not used

A

Subgroup 2.2.2

Auto-redirect must not be used

2.3

A

Subgroup 2.3.1

All img elements have associated images that do not flicker

A

Subgroup 2.3.1

Applets cause screen flicker

A

Subgroup 2.3.1

All objects do not flicker

A

Subgroup 2.3.1

Script should not cause screen flicker

2.4

A

Subgroup 2.4.1

A ""skip to content"" link appears on all pages with blocks of material prior to the main document

A

Subgroup 2.4.1

All frames have a title attribute

A

Subgroup 2.4.1

All frame titles identify the purpose or function of the frame

A

Subgroup 2.4.1

ASCII art should have a skipover link

A

Subgroup 2.4.1

All groups of links with a related purpose are marked

A

Subgroup 2.4.2

Document contains a title element

A

Subgroup 2.4.2

Title contains text

A

Subgroup 2.4.2

Title is short

A

Subgroup 2.4.2

Title is not placeholder text

A

Subgroup 2.4.2

Title describes the document

A

Subgroup 2.4.4

Link text is meaningful when read out of context

A

Subgroup 2.4.4

Suspicious link text

A

Subgroup 2.4.4

Each source anchor contains text

AA

Subgroup 2.4.5

Sites must have a site map

AA

Subgroup 2.4.6

The header following an h1 is h1 or h2

AA

Subgroup 2.4.6

The header following an h2 is h1, h2 or h3

AA

Subgroup 2.4.6

The header following an h3 is h1, h2, h3 or h4.

AA

Subgroup 2.4.6

The header following an h4 is h1, h2, h3, h4 or h5

AA

Subgroup 2.4.6

The header following an h5 is h6 or any header less than h6

AA

Subgroup 2.4.6

All h1 elements are not used for formatting

AA

Subgroup 2.4.6

All h2 elements are not used for formatting

AA

Subgroup 2.4.6

All h3 elements are not used for formatting

AA

Subgroup 2.4.6

All h4 elements are not used for formatting

AA

Subgroup 2.4.6

All h5 elements are not used for formatting

AA

Subgroup 2.4.6

All h6 elements are not used for formatting

2.5

A

Subgroup 2.5.1

Content can be operated using simple inputs on a wide range of pointing devices

A

Subgroup 2.5.2

Functionality that can be operated using a single pointer, is implemented in a safe manner

A

Subgroup 2.5.3

User interface components with labels that include text or images of text has the text that is presented visually contained in the name

A

Subgroup 2.5.4

Functionality that can be operated by device motion or user motion can also be operated by user interface

A

Subgroup 2.5.4

Functionality that can be operated by device motion or user motion can be disabled to prevent accidental actuation


Principle 3: Understandable

Information and the operation of user interface must be understandable.

Level

Subgroup Identification

Rule

3.1

A

Subgroup 3.1.1

Document has required lang attribute(s)

A

Subgroup 3.1.1

Document has valid language code

A

Subgroup 3.1.1

Reading order direction is marked using the html element's dir attribute if the document""s primary language is read right to left

AA

Subgroup 3.1.2

Words and phrases not in the document's primary language are marked.

3.2

A

Subgroup 3.2.1

Loading the web page does not cause a new window to open

A

Subgroup 3.2.2

Area should not open new window without warning

A

Subgroup 3.2.2

All select elements do not cause an extreme change in context

A

Subgroup 3.2.2

Change of context occurs only by user activation unless a warning is provided

AA

Subgroup 3.2.3

Repeated blocks of content appear in the same frame within the frameset

AA

Subgroup 3.2.3

AThe tab order specified by tabindex attributes follows a logical order

AA

Subgroup 3.2.3

Repeated components appear in the same relative order each time they appear

AA

Subgroup 3.2.4

List items must not be used to format text

AA

Subgroup 3.2.4

Blockquote must not be used for indentation

AA

Subgroup 3.2.4

Use the blockquote element to mark-up block quotations

3.3

A

Subgroup 3.3.1

All form submission error messages identify any empty required fields

A

Subgroup 3.3.2

Each input element has only one associated label

A

Subgroup 3.3.2

Each label associated with an input element contains text

A

Subgroup 3.3.2

Each label describes its associated input element

A

Subgroup 3.3.2

All input elements, type of "file", have a label that describes the purpose or function of the control

A

Subgroup 3.3.2

All select elements have a label that describes the purpose or function of the control

A

Subgroup 3.3.2

All input elements, type of "password", have a label that describes the purpose or function of the control

A

Subgroup 3.3.2

All input elements, type of "text", have a label that describes the purpose or function of the control.

A

Subgroup 3.3.2

All input elements, type of "checkbox", have a label that describes the purpose or function of the control

A

Subgroup 3.3.2

All input elements, type of "radio", have a label that describes the purpose or function of the control

A

Subgroup 3.3.2

All form fields that are required are indicated to the user as required

AA

Subgroup 3.3.3

All form submission error messages provide assistance in correcting the error

AA

Subgroup 3.3.4

Form submission data is presented to the user before final acceptance for all irreversible transactions

AA

Subgroup 3.3.4

Information deleted using a web page can be recovered


Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

A warning in this category means that the site does not meet the requirements for compatibility with current and future user agents, including assistive technologies.

Level

Subgroup Identification

Rule

4.1

A

Subgroup 4.1.1

id attributes must be unique

AA

Subgroup 4.1.3

Status messages can be programmatically determined through role or properties


WCAG 2.2

Principle 1: Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Level

Subgroup Identification

Rule

1.1

Text Alternatives: Provide text alternatives for all non-text content

A

Subgroup 1.1.1

Non-text Content

1.2

Time-based Media: Provide alternatives for time-based media

A

Subgroup 1.2.1

Audio-only and Video-only (Prerecorded)

A

Subgroup 1.2.2

Captions (Prerecorded)

A

Subgroup 1.2.3

Audio Description or Media Alternative (Prerecorded)

AA

Subgroup 1.2.4

Captions (Live)

AA

Subgroup 1.2.5

Audio Description (Prerecorded)

AAA

Subgroup 1.2.6

Sign Language (Prerecorded)

AAA

Subgroup 1.2.7

Extended Audio Description (Prerecorded)

AAA

Subgroup 1.2.8

Media Alternative (Prerecorded)

AAA

Subgroup 1.2.9

Audio-only (Live)

1.3

Adaptable: Create content that can be presented in different ways without losing information or structure

A

Subgroup 1.3.1

Info and Relationships

A

Subgroup 1.3.2

Meaningful Sequence

A

Subgroup 1.3.3

Sensory Characteristics

AA

Subgroup 1.3.4

Orientation

AA

Subgroup 1.3.5

Identify Input Purpose

AAA

Subgroup 1.3.6

Identify Purpose

1.4

Distinguishable: Make it easier for users to see and hear content including separating foreground from background.

A

Subgroup 1.4.1

Use of Colour

A

Subgroup 1.4.2

Audio Control

AA

Subgroup 1.4.4

Resize text

AA

Subgroup 1.4.5

Images of Text

AAA

Subgroup 1.4.6

Contrast (Enhanced)

AAA

Subgroup 1.4.7

Low or No Background Audio

AAA

Subgroup 1.4.8

Visual Presentation

AAA

Subgroup 1.4.9

Images of Text (No Exception)

AA

Subgroup 1.4.10

Reflow

AA

Subgroup 1.4.11

Non-context Contrast

AA

Subgroup 1.4.12

Text spacing

AA

Subgroup 1.4.13

Content on Hover or Focus


Principle 2: Operable

User interface components and navigation must be operable.

Level

Subgroup Identification

Rule

2.1

Keyboard Accessible: Make all functionality available from a keyboard.

A

Subgroup 2.1.1

Keyboard

A

Subgroup 2.1.2

No Keyboard Trap

AAA

Subgroup 2.1.3

Keyboard (No Exception)

A

Subgroup 2.1.4

Character Key Shortcuts

2.2

Enough Time: Provide users enough time to read and use content.

A

Subgroup 2.2.1

Timing Adjustable

A

Subgroup 2.2.2

Pause, Stop, Hide

AAA

Subgroup 2.2.3

No Timing

AAA

Subgroup 2.2.4

Interruptions

AAA

Subgroup 2.2.5

Re-authenticating

AAA

Subgroup 2.2.6

Timeouts

2.3

Seizures and Physical Reactions: Do not design content in a way that is known to cause seizures or physical reactions.

A

Subgroup 2.3.1

Three Flashes or Below Threshold

AAA

Subgroup 2.3.2

Three Flashes

AAA

Subgroup 2.3.3

Animation from Interactions

2.4

Navigable: Provide ways to help users navigate, find content, and determine where they are.

A

Subgroup 2.4.1

Bypass Blocks

A

Subgroup 2.4.2

Page Titled

A

Subgroup 2.4.3

Focus Order

A

Subgroup 2.4.4

Link Purpose (In Context)

AA

Subgroup 2.4.5

Multiple Ways

AA

Subgroup 2.4.6

Headings and Labels

A

Subgroup 2.4.7

Focus Visible

AAA

Subgroup 2.4.8

Location

AAA

Subgroup 2.4.9

Link Purpose (Link Only)

AAA

Subgroup 2.4.10

Section Headings

AAA

Subgroup 2.4.12

Focus Appearance (Enhanced)

A

Subgroup 2.4.13

Fixed Reference Points

2.5

Input Modalities

A

Subgroup 2.5.1

Pointer Gestures

A

Subgroup 2.5.2

Pointer Cancellation

A

Subgroup 2.5.3

Label in Name

A

Subgroup 2.5.4

Motion Actuation

AAA

Subgroup 2.5.5

Target Size

AAA

Subgroup 2.5.6

Concurrent Input Mechanisms

AA

Subgroup 2.5.7

Dragging

AA

Subgroup 2.2.5.8

Pointer Target Spacing


Principle 3: Understandable

Information and the operation of user interface must be understandable.

Level

Subgroup Identification

Rule

3.1

Readable: Make text content readable and understandable

A

Subgroup 3.1.1

Language of Page

AA

Subgroup 3.1.2

Language of Parts

AAA

Subgroup 3.1.3

Unusual Words

AAA

Subgroup 3.1.4

Abbreviations

AAA

Subgroup 3.1.5

Reading Level

AAA

Subgroup 3.1.6

Pronunciation

3.2

Predictable: Make Web pages appear and operate in predictable ways.

A

Subgroup 3.2.1

On Focus

A

Subgroup 3.2.2

On Input

AA

Subgroup 3.2.3

Consistent Navigation

AA

Subgroup 3.2.4

Consistent Identification

AAA

Subgroup 3.2.5

Change on Request

A

Subgroup 3.2.6

Findable Help

AA

Subgroup 3.2.7

Hidden Controls

3.3

Input Assistance: Help users avoid and correct mistakes.

A

Subgroup 3.3.1

Error Identification

A

Subgroup 3.3.2

Labels or Instructions

AA

Subgroup 3.3.3

Error Suggestion

AA

Subgroup 3.3.4

Error Prevention (Legal, Financial, Data)

AAA

Subgroup 3.3.5

Help

AAA

Subgroup 3.3.6

Error Prevention (All)

A

Subgroup 3.3.7

Accessible Authentication

A

Subgroup 3.3.8

Redundant entry


Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

A warning in this category means that the site does not meet the requirements for compatibility with current and future user agents, including assistive technologies.

Level

Subgroup Identification

Rule

4.1

Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

A

Subgroup 4.1.1

Parsing

A

Subgroup 4.1.2

Name, Role, Value

AA

Subgroup 4.1.3

Status Messages


Additional Resources

For more information, see the User Guide articles:

For more information, see the external guide:

For definitions and explanations of acronyms and abbreviations used in the Monsido User Guide, see:

For further assistance, contact the Monsido support team at support@monsido.com or use the Monsido chat and help features inside the application.

Image of the toolbar with the Help Center buttons highlighted.

Did this answer your question?