-
Notifications
You must be signed in to change notification settings - Fork 14
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
Fix accessibility tests π¨π»βπ§ #11
Conversation
The latest patch of this library throws unexpected accesssibility violations around duplicated ID attributes on components. See this issue for more context: NickColley/jest-axe#56
We were skipping some tests are they were throwing unexpected errors related to accessibility. See this issue for more context: #1 After downgrading `jest-axe` they behave correctly. We'll open an issue once the correct patch for `jest-axe` comes in.
b75ee10
to
e70b3c8
Compare
Had a |
After rebasing against `master` we lost some changes. Bringing them back.
@poteirard ah I see many of the atoms are written in this fashion for some reason: const SAtom = styled.div`
/* ... */
`
const Atom = props => <SAtom {...props} />;
export default Atom; Doesn't look too good as it seems it's done to workaround the Styleguidst warning above? π€ I'll revert the changes of the file as they're out of the scope of this PR, but maybe we can open an issue to dive deep into this warning? |
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.
Thank you <3
π This PR is included in version 1.1.1 π The release is available on: Your semantic-release bot π¦π |
Summary
It seems that the latest patch of
jest-axe
throws unexpected errors around accessibility violations.See this issue for more context on why.
I pinned
jest-axe
to3.1.0
and brought back the tests we were skipping.I'll open an issue to bring back
jest-axe
to^3.*.*
once they patch their patch ππ» πIssue
Fixes #1