-
Notifications
You must be signed in to change notification settings - Fork 129
test(a11y): e2e baseline tests for a11y screen reader descriptions #2684
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
Conversation
markov00
left a comment
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.
Looks good to me, I just like to wait for @nickofthyme review on the CI part but looks working/running fine!
|
@nickofthyme as discussed I renamed the existing playwright tests/reports to include a reference to VRT so we have a better VRT/A11Y distinction for the e2e tests. |
nickofthyme
left a comment
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.
First pass on test code, looking at ci changes now.
Summary
This PR adds e2e accessibility tests to assert screen reader summaries for different chart types and configurations. The aim is to get a baseline of the current state of these summaries before we merge the improvements being worked on in #2683. This will allow us to track regressions/improvements in a better way.
Details
The accessibility e2e tests pick up the existing setup to run visual regression tests. Originally I thought we could run them as part of the visual regression tests, but then it would be tricky to run them locally because the visual ones don't pass there. So I implemented this via a separate command you can run via
yarn test:e2e:a11y. Like the visual regression tests, the a11y ones also walk through the storybook examples and then assert the screen reader description (what's within.echScreenReaderOnly).I added the tests to the CI setup too, the scripts are mostly copies of the ones used for the visual regression tests.
Open Question: We now run
yarn test:e2efor visual regression tests andyarn test:e2e:a11y. Should we be more explicit about the visual regression test ones (likeyarn test:e2e:vrt) - and also update descriptive texts to include VRT or Visual Regression Testing for the default e2e tests?Issues
Part of #36386.
Checklist
:interactions,:axis)closes #123,fixes #123)