We've upgraded our Accessibility validation servers to the latest version of axe-core, 4.5, which introduces a new WCAG 2.2 rule to check the target size. We've also enabled 7 experimental rules that existed in previous releases of axe-core.
New WCAG 2.2 rule to test for a minimum size of touch targets
Axe-core’s new target-size rule tests if links, buttons, form fields, and other controls have a width and height of at least 24 pixels, or if they don’t, that they have that much space from the closest other control. This helps people who are less accurate in using a mouse or touchpad from accidentally activating the wrong control. For more information on target size, see understanding 2.5.8 Target Size.
7 experimental rules now enabled
css-orientation-lock
Checks that 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.
focus-order-semantics
Checks all interactive elements in the focus order to ensure that the role attribute value is valid and appropriate, whether native HTML or a custom ARIA widget.
hidden-content
Checks CSS style property values of display: none; and visibility: hidden; and alerts users to the presence of hidden item content requiring further review.
label-content-name-mismatch
For each user interface component that includes a visible text label, the accessible name must match (or include) the visible text in the label.
p-as-heading
Ensures that paragraph elements do not use italic, bold or font size to give the appearance of headings.
table-fake-caption
Checks that data tables are marked up with table cells that use a colspan element to indicate a caption visually.
td-has-header
Checks that data tables are marked up semantically and have the correct header structure.
Bug Fixes
Check out the 4.5 release notes.
Current accessibility ruleset
Check out the full list of accessibility rules that are being checked currently by our web crawler
Accessibility rules checked by Rocket Validator