-
Notifications
You must be signed in to change notification settings - Fork 788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(duplicate-id-aria): set to review on fail and tag as wcag412 #4075
Conversation
assert.lengthOf( | ||
test[collection], | ||
0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This lets us say not to expect any violations. Previously that was just erroring.
This is marked as closing 3892, but that issue includes this note that I don't think has been resolved yet:
Are we still planning that? Do we at least want to extract that bit to a separate rule suggestion issue before allowing this PR to close it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes LGTM!
Here's the issue you asked for: #4076 |
#### Details This PR updates axe-core to its latest version, [4.8.4](https://github.com/dequelabs/axe-core/releases/v4.8.4), from [4.7.2](https://github.com/dequelabs/axe-core/releases/v4.7.2). It also bumps the accessibility-insights-report package version. As part of the axe-core update: - The deprecate & disable duplicate-id / duplicate-id-active rule has been deprecated (dequelabs/axe-core#4071). - moved duplicate-id-aria to needs review. (dequelabs/axe-core#4075) <img width="922" alt="image" src="https://github.com/microsoft/accessibility-insights-web/assets/95463767/152c51ce-16d9-4550-aee2-6ddd8155a722"> - checks: enable help-same-as-label, but remove from rules (dequelabs/axe-core#4096) - 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[], - Major version upgrade 4.8.0 details https://github.com/dequelabs/axe-core/releases/tag/v4.8.0 <!-- Usually a sentence or two describing what the PR changes --> ##### Motivation This change is part of https://dev.azure.com/mseng/1ES/_workitems/edit/2157659/ ##### Context <!-- Are there any parts that you've intentionally left out-of-scope for a later PR to handle? --> <!-- Were there any alternative approaches you considered? What tradeoffs did you consider? --> #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [ ] Addresses an existing issue: #0000 - [ ] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [ ] (UI changes only) Added screenshots/GIFs to description above - [ ] (UI changes only) Verified usability with NVDA/JAWS --------- Co-authored-by: Rakesh Shivapooja <v-rakeshsh@microsoft.com> Co-authored-by: Vikash Yadav <v-viyada@microsoft.com>
Closes: #3892