Accessibility checks in mabl now run on axe-core 4.13.0. The update brings the latest rule improvements from Deque, including fewer false positives for color contrast and target size, and new coverage for a few patterns that went unreported before.
Most accessibility checks will report about the same number of violations or slightly fewer. Some checks may report new violations on pages that haven't changed, so review any check that starts failing after the update.
Cloud runs use the new version automatically. To ensure you get consistent results across local and cloud runs, make sure to update your mabl Desktop App and/or CLI to the latest version:
- Update the mabl Desktop App for Trainer and local runs triggered from the Desktop App
- Update the mabl CLI for local runs triggered from the CLI
What's changed
New violations
-
aria-tab-name (serious, WCAG 2 A): elements with
role="tab"that have no accessible name and aren't native buttons. An unnamed<button role="tab">was already reported underbutton-name. -
summary-name (serious, WCAG 2 A):
<summary>elements with no accessible name. -
td-headers-attr (serious, WCAG 2 A): table cells whose
headersattribute points at another<td>instead of a header cell.
Severity changes
- meta-viewport is now moderate instead of critical. If an accessibility check fails on critical violations and a page that blocks zoom was the only critical violation, that check now passes.
Fewer false positives
- color-contrast is more accurate for stacking contexts, overflow, blend modes, and oklch/oklab colors.
- target-size is more accurate for inline, offscreen fixed-position, shadow DOM, and tab panel elements.
- landmark-complementary-is-top-level is deprecated and no longer runs by default. Checks that use the default configuration or tags stop reporting it, while checks that list the rule by ID still run it.
More incomplete results
axe-core now reports more results it can't confirm automatically, such as aria-haspopup buttons whose aria-controls menu isn't in the DOM yet. These results appear on the Incomplete tab of the accessibility check results. They never fail an accessibility check and don't count toward the pass rate.
For the full list of upstream changes, see the axe-core changelog.