axe-core, Deque’s open-source accessibility testing engine, has released version 4.12.0. This minor update, dated 2026-06-01, brings important refinements for automated accessibility testing. For the full changelog, refer to the official axe-core GitHub release notes.
Key Changes
- New Rule: A significant addition is the
aria-tab-namerule. This new check ensures that elements withrole="tab"possess an accessible name, improving navigation and understanding for assistive technology users. - Rule Deprecation: The
landmark-complementary-is-top-levelrule has been deprecated. This change aligns axe-core with updated ARIA specifications, which no longer require complementary landmarks to be top-level. This may resolve some previously flagged issues that were false positives. - Element Internals Support: Version 4.12.0 includes foundational work for Element Internals support. This feature, currently behind a flag, prepares axe-core to test the accessibility of custom elements that use the Element Internals API. This includes new external scripts and public APIs for managing Element Internal data, with partial support for roles like
listandlistitem. - Bug Fixes: Several issues have been addressed, enhancing the accuracy and reliability of existing rules. Fixes include improvements for
target-size,scrollable-region-focusable,aria-allowed-attr(specifically forbrandwbrelements),aria-conditional-attrforradioelements, and correct handling of multiplearia-errormessageIDs inaria-valid-attr-value. Other fixes prevent duplicate nodes ingetOwnedVirtualand exclude natively hidden elements fromaria-labelledbyaccessible names.
Impact for QA Teams
QA teams should update axe-core to v4.12.0 to ensure their automated accessibility tests reflect the latest ARIA standards. The new aria-tab-name rule may reveal previously undetected issues, while the deprecated rule and various bug fixes could reduce false positives. This update helps maintain accurate accessibility reporting and prepares for future testing of custom web components.
