axe-core 4.11.2

This page is not available in the language you requested. You have been redirected to the English version of the page.
Link to this page copied to clipboard

Release Notes

This release addresses a number of false positives, including ones related to target size. It adds new affordances for ARIA, and adds a clarification around the scrollable regions rule.

Bug Fixes

  • aria-valid-attr-value: handle multiple aria-errormessage IDs (#4973) (9322148)
  • aria: prevent getOwnedVirtual from returning duplicate nodes (#4987) (99d1e77), closes #4840
  • DqElement: avoid calling constructors with cloneNode (#5013) (88bc57f)
  • existing-rule: aria-busy now shows an error message for a use with unallowed children (#5017) (dded75a)
  • scrollable-region-focusable: clarify the issue is in safari (#4995) (2567afd), closes WebKit#190870 WebKit#277290
  • scrollable-region-focusable: do not fail scroll areas when all content is visible without scrolling (#4993) (240f8b5)
  • target-size: determine offset using clientRects if target is display:inline (#5012) (69d81c1)
  • target-size: ignore widgets that are inline with other inline elements (#5000) (cf8a3c0)

View on GitHub

Product Impacts

note

Each product has a separate axe-core version rollout process. The information below describes the impacts of this axe-core release once it is pulled into the given product.

axe Auditor

Issue counts could be impacted in some cases based on rule updates.

axe Developer Hub

Issue counts could be impacted in some cases based on rule updates.

axe DevTools APIs and CLI

Issue counts could be impacted in some cases based on rule updates.

axe DevTools Extension

Issue counts could be impacted in some cases based on rule updates.

axe DevTools Linter

Issue counts could be impacted in some cases based on rule updates.

axe Monitor

Issue counts could be impacted in some cases based on rule updates.

axe Reports

Issue counts could be impacted in some cases based on rule updates.