-
Notifications
You must be signed in to change notification settings - Fork 10
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
Investigate the accessibility rules configured in the jest-axe library. #28
Comments
Here are a list of changes to axe-core from v4.4.1 to v4.7.24.7.2 (2023-05-25)Bug Fixes
4.7.1 (2023-05-15)Bug Fixes
4.7.0 (2023-04-17)Features
Bug Fixes
4.6.3 (2023-01-23)Bug Fixes
4.6.2 (2022-12-23)Bug Fixes4.6.1 (2022-12-14)Bug Fixes4.6.0 (2022-12-12)Features
Bug Fixes
4.5.2 (2022-11-14)Bug Fixes
4.5.1 (2022-11-01)Bug Fixes
4.5.0 (2022-10-17)FeaturesHighlights
Tags and Metadata UpdatesVarious changes of tags, for greater consistency with ACT Rules.
Deprecations
Others
Bug Fixes
4.4.3 (2022-07-13)Bug Fixes
4.4.2 (2022-05-12)Bug Fixes
|
Issue fixed with PR# microsoft/fluentui#30309 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Investigate the accessibility rules configured in the jest-axe library in fluent repo https://github.com/microsoft/fluentui/blob/d8321c5e8191f94e9413aee0e800f96d3de8e311/package.json#L251.
Our baseline is the accessibility insights web tool which keeps on adding more rules and checks in their releases.
Refer https://github.com/microsoft/accessibility-insights-web/releases/tag/web@2.41.0
Are the rules in jest-axe dependency upto date.
If not, then how to update these rules to represent the current standard.
Assigned to @Shubhabrata08
The text was updated successfully, but these errors were encountered: