Accessibility engine for automated Web UI testing
MPL-2.0 License
Bot releases are visible (Hide)
overflow: hidden
ancestor (#4357) (bdb7300), closes #4253
Published by attest-team-ci 8 months ago
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.
Published by attest-team-ci 10 months ago
Published by attest-team-ci about 1 year ago
Published by attest-team-ci about 1 year ago
Published by attest-team-ci about 1 year ago
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:
Published by attest-team-ci over 1 year ago
This release corrects the Trusted Tester v5 tags, which were introduced in 4.7.0, and it addresses a few false positives which for pages with forms may result in a few less issues found.
Published by attest-team-ci over 1 year ago
This release addresses a number of bugs. Some things that were failed in the previous release may now be passed or require manual review.
Published by attest-team-ci over 1 year ago
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)Published by attest-team-ci over 1 year ago
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)Published by attest-team-ci almost 2 years ago
Published by attest-team-ci almost 2 years ago
Published by WilcoFiers almost 2 years ago
This release adds requirements introduced in WAI-ARIA 1.2, which can result in new issues. The color contrast rule has been improved which should reduce the number of incomplete (aka "needs review") results.
Lastly, this release adds the ability to include or exclude elements inside shadow DOM trees from a test run. See [dom selection] for details.
Published by attest-team-ci almost 2 years ago
This release can result in fewer issues reported on link-in-text-block and aria-required-children. This release addresses an issue where color-contrast and target-size violations were not reported after the page was scrolled.
Published by attest-team-ci almost 2 years ago
This release does not change results of axe-core. It resolves a problem where axe had gotten unnecessarily picky about which order things need to be loaded in in some test environments.
Published by attest-team-ci almost 2 years ago
This release may increase or decrease the number of violations reported. This can be because some rules have changed in which ruleset they run (best practice to WCAG, and vice versa). It can also be because the rules themselves got stricter in some places so are able to find new violations, and got more permissive in other places in order to handle more edge cases.
Tags that indicate which success criteria a rule tests violations for have been changed for several rules. In some cases new success criteria tags were added, and in others criteria tags were removed.
Various changes of tags, for greater consistency with ACT Rules.
Published by attest-team-ci over 2 years ago
This release does not change results of axe-core. Instead it gets rid of a warning when axe-core is installed with NPM using older versions of NodeJS. We also added a missing type definition when using axe.configure()
in TypeScript.
Published by attest-team-ci over 2 years ago
This release could reduce the number of violations reported and it could increase the number of incomplete items reported. We've tweaked a few remediation messages of rules for greater consistency and clarity. Role presentation and role none are now allowed on the HTML nav element. The aria-hidden-focusable rule now returns reports incomplete instead of a violation if the element has the onfocus attribute.
Published by WilcoFiers over 2 years ago
Published by straker over 2 years ago
aria-attributes
for role="row"
(#3160) (cfa900d)aria-errormessage
(#3156) (95d37dd)p-as-heading
rule to account for textContent
length (#3145) (400a230)window.postMessage
is null
(#3249) (b37b2f6)