Accessibility engine for automated Web UI testing
overflow: hidden
ancestor (#4357) (bdb7300), closes #4253
This release should not result in different issue numbers. For TypeScript users, an error in type definitions has been corrected. This release could require a correction to how axe-core types are used. This release may change selectors on elements with the xmlns
attribute, as the selectors axe-core prosed with those was invalid. Deduplication based on selectors between this and and prior versions of axe-core can fail because of this change.
This axe-core release makes various changes to impact. As a result issues previously reported in one rule may now be reported under a different rule. In rarer cases, the impact under which an issue is reported may change. This release has further deprecated the duplicate-id
and duplicate-id-active
rule, along with setting the duplicate-id-aria
to always report as "needs review" rather than as a violation. As these three rules are fairly common causes of issues, this change may result in the total issue reported going down significantly.
This release changes it so that a rule never changes what impact it reports. To facilitate this while without changing the impact on certain issues, some rules have been split. The following changes were involved:
Various improvements were made to the types. Potentially the most impactful of which is that the target
and ancestry
property now return as UnlabelledFrameSelector
instead of as string[]
, which is incorrect for selectors involving shadow DOM. This may create some issues during migration for any code that has been incorrectly assuming these two properties have the string[]
type. For more details and other type changes, see the commit itself:
This release addresses a number of bugs. Some things that were failed in the previous release may now be passed or require manual review.
This release adds support for a few features that have been added to browsers in the last year. No new rules are added, and it did not make axe-core stricter in any other significant way. The number of issues reported by this version may be lower than from the prior version. Of one rule, the impact level was raised.
Page.setDocumentContent
(#3921) (66f23e5)This release can reduce the number of issues reported. On color-contrast it will result in fewer incomplete results (aka "needs review"), which may result in a few more color-contrast violations found.
<slot>
elements (#3847) (844cea1)