Skip to content

Detector So Far ​

Check Points ​

Each row links to two places: the left column to how the detector checks that criterion in this documentation, the right column to the official WCAG 2.2 Understanding page on w3.org, which opens in a new tab.

In this documentationIn the WCAG 2.2 standard
1.1.1 Non-text Content — not currently in productionUnderstanding 1.1.1 Non-text Content
1.3.1 Info and RelationshipsUnderstanding 1.3.1 Info and Relationships
1.4.1 Use of ColorUnderstanding 1.4.1 Use of Color
1.4.3 Contrast (Minimum)Understanding 1.4.3 Contrast (Minimum)
1.4.4 Resize TextUnderstanding 1.4.4 Resize Text
1.4.10 ReflowUnderstanding 1.4.10 Reflow
1.4.11 Non-text ContrastUnderstanding 1.4.11 Non-text Contrast
2.1.1 KeyboardUnderstanding 2.1.1 Keyboard
2.1.2 No Keyboard TrapUnderstanding 2.1.2 No Keyboard Trap
2.4.3 Focus OrderUnderstanding 2.4.3 Focus Order
2.4.7 Focus VisibleUnderstanding 2.4.7 Focus Visible
4.1.2 Name, Role, ValueUnderstanding 4.1.2 Name, Role, Value
4.1.3 Status MessagesUnderstanding 4.1.3 Status Messages

Hospitality Booking ​

Hospitality Booking — the specialised checks for hotel booking flows, covering the destination field, the calendar and the guests-and-rooms panel — is currently in development.


Problem Type Reports ​


1.1.1 Non-text Content (Level A):

  • The decorative image is not set as such
  • The decorative logo is not set as such.
  • The informative image does not have an accessible name.
  • The logo image lacks an accessible name.
  • The accessible name provided for the image is not descriptive enough.
  • The accessible name provided for the logo image is not descriptive enough.

1.3.1 Info and Relationships (Level A)

  • The page does not define a valid main landmark
  • Landmark without accessible label when multiple of same type exist
  • Page has multiple landmarks of the same type without unique names
  • Headings incorrectly nested into each other
  • Visual heading is not marked up as such

1.4.1 Use of Color (Level A)

  • The link relies on color for identification and fails to contrast requirements with the surrounding text
  • The control indicates its focus state using color alone, with insufficient contrast between states

1.4.3 Contrast (Minimum) (Level AA)

  • The color text name (foreground color: hex, font size: px, font-weight: bold) fails color contrast against the cyan background (hex) with a ratio of <contrast ratio>.
  • The color text name (foreground color: hex, font size: px, font-weight: bold) on hover fails color contrast against the cyan background (hex) with a ratio of <contrast ratio>.
  • The color text name (foreground color: hex, font size: px, font-weight: bold) on focus fails color contrast against the cyan background (hex) with a ratio of <contrast ratio>.
  • The color text name (foreground color: hex, font size: px, font-weight: bold) on hover and focus fails color contrast against the cyan background (hex) with a ratio of <contrast ratio>.

1.4.4: Resize Text (Zoom 200%)

  • Text is cut off at 200% zoom
  • Browser zoom is disabled (cannot resize text to 200%)
  • Text overlaps when zooming to 200%
  • Text does not resize when zooming to 200%

1.4.10 Reflow (Level AA)

  • Content disappears at 320 px width.
  • Once the viewport is set to 320 px wide by 256 px high, a horizontal bar is displayed.
  • The content on the page does not reflow correctly

1.4.11 Non-text Contrast

  • The focus indicator in the control fails to meet color contrast requirements against the background
  • Insufficient contrast against the control borders and background
  • Insufficient contrast against the control and background
  • Insufficient contrast against the control and background (adjacent background)
  • Insufficient contrast against the control and background (states selected-hover)
  • Focused non-text element does not have sufficient contrast against its background

2.1.1 Keyboard (Level A)

  • Unfocused element (Tab - Shift-Tab)
  • The interactive control is not keyboard operable

2.1.2 No Keyboard Trap (Level A)

  • Keyboard trap in interactive controls.
  • Keyboard trap in loop forms

2.4.3 Focus Order (Level A)

  • Non-interactive elements focused (Tab - Shift-Tab)
  • Hidden control receives focus during navigation
  • The focus order is not logical and intuitive in the (Tab - Shift+Tab) navigation order
  • Interactive element receives focus more than once during navigation
  • Multiple focus on interactive controls due to nesting between them

2.4.7 Focus Visible

  • The interactive element does not have a visible focus indicator

4.1.2 Name, Role, Value (Level A)

  • The element 'affected element name' is announced without a role
  • The element 'affected element name' is announced without an accessible name
  • The element 'affected element name' is announced without an accessible name or role
  • 'Disabled' state of the control is not announced

4.1.3 Status Messages (Level AA)

  • Loading indicator appears without being announced to screen readers
  • Search results change without being announced to screen readers
  • Action feedback (toasts, form success/error, counters) is not announced to screen readers

Extension and visual interface ​

  • tabindex validations.

  • Preview option for reported issues.

  • User action recording.

  • Viewport adjustment.