[Feature] Using Playwright to automate some of the guided tests for accessibility Insights for Web

[harir5]

Hi,

Just a thought at the moment. Accessibility insights for web(which i stumbled upon in your community showcase page) currently offers some guided tests and automated checks; the guided tests that are provided have to be run manually( for instance keyboard navigation and tabbing) - is there a way to run some playwright tests (for instance number of tabs can be provided as input for a particular page and the script can tab across different components in the page) and at the end pass or fail the accessibility test perhaps ?

is this feasible?

[mxschmitt]

This is not yet possible!

what guided checks do you mean? This would help us to understand the use-case.

[harir5]

@mxschmitt - checks like these :

this 'guided' test has to be run manually and the user then has to pass/fail the test manually. If we can automate this in Playwright and pass/fail the guided test from code, it would really be useful during accessibility assessments.

[mxschmitt]

I'll mark it as a feature request, so we can include it into the accessibility story when we revisit the accessibility topic.

[dbjorge]

Hi @harir5 ! I'm an engineer on the Accessibility Insights team.

Our recommendation for folks that want to include the automatable portions of Accessibility Insights in a Playwright test suite is to use @axe-core/playwright to write test cases using axe-core, the accessibility rules engine that Accessibility Insights uses for its automated checks.

I've just written up a feature proposal (#14112) for adding official documentation to playwright.dev explaining how to do this, but in the meantime, our team maintains some samples at microsoft/axe-pipelines-samples that might give you a good starting point.

[harir5]

@dbjorge - thank you for your response. I have already completed a small proof of concept with Axe-Core. I have created default reports that get generated when we run these tests as well. I would like to discuss further on integrating playwright with some of the manual tests that we run using MS Accessibility insights. is it possible to get in touch with you to discuss about these things further ?

[pavelfeldman]

Why was this issue closed?

Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a manageable database, we prioritize issues based on these factors.

If you disagree with this closure, please open a new issue and reference this one. More support or clarity on its necessity may prompt a review. Your understanding and cooperation are appreciated.