-
Notifications
You must be signed in to change notification settings - Fork 42
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
Accessibility module in WebDriver BiDi? #443
Comments
One could argue that a very popular use case is to fetch an element via a11y name. WebdriverIO currently computes some complex xPath to make a good guess about it according to the spec but it doesn't work all time due to xPath limitations. It the would help a lot if this could be a primitive, e.g. a selector strategy. |
I would love for this to be supported. Had a request posted in the interop issue with reasonings for it:
Originally posted by @clshortfuse in web-platform-tests/interop-accessibility#2 (comment) |
The Browser Testing and Tools Working Group just discussed The full IRC log of that discussion<davehunt> topic: Accessibility module for WebDriver BiDi<AutomatedTester> github: https://github.com//issues/443 <jgraham> q? <davehunt> orkon: Since last year we have the ability to locate DOM elements by accessibility attributes <davehunt> orkon: Still not supported is getting snapshots of the accessibility tree <davehunt> whimboo: I added this as it was a request from Playwright <orkon> q+ <simonstewart> q? <jcraig> q+ <jgraham> q+ <Jamie> q+ <davehunt> jimevans: We've already done the location of nodes. Being able to get the snapshot would be useful to me <simonstewart> q+ <AutomatedTester> ack orkon <jcraig> q+ to ask the need for the tree, since the implmentations will be different across WPT tests. <jgraham> q- <davehunt> orkon: We can't implement because there's no agreement yet on what the accessibility tree looks like <jcraig> ack jcraig <Zakim> jcraig, you wanted to ask the need for the tree, since the implmentations will be different across WPT tests. <simonstewart> q- <whimboo> orkon: you were right. the interop 2024 initiative was the reason <davehunt> jcraig: Lot of accessibility automation stacks being worked on. WPT tests currently exists entirely in the browser. <jgraham> q+ <AutomatedTester> q? <davehunt> jcraig: We have an investigation to implement a tree dump. There's going to be different trees. I'd like to understand more about the needs are for getting the tree. <davehunt> jimevans: Cross browser tree comparisons is something that we would be interested in. <davehunt> jcraig: It's achievable in the near future to do comparisons by walking the tree if we have limited known test cases <AutomatedTester> ack jamie <jcraig> s/had an investigation/have an investigation/ <gsnedders> RRSAgent, make minutes <RRSAgent> I have made the request to generate https://www.w3.org/2024/09/27-webdriver-minutes.html gsnedders <davehunt> Jamie: The thinking is that if we get accessible node working well then it's possible to write a tree dump as a layer on top of that. Important to get accessible node right first. I think we're heading in a direction that allows this. <AutomatedTester> ack jgraham <Jamie> https://github.com/web-platform-tests/interop-accessibility/issues/51#issuecomment-2099462510 <simonstewart> q? <AutomatedTester> q? <jcraig> TreeDump Investiigation (abandoned) https://github.com/web-platform-tests/interop-accessibility/issues/51 <davehunt> jgraham: Puppeteer exposes an API for accessibility trees, Playwright API redirects to alternate tools. Agree that don't expect the accessibility tree to be comparable between browsers in the near future. <jcraig> Some explanation of the reasoning for moving https://github.com/web-platform-tests/interop-accessibility/issues/90 <jcraig> s/moving/moving to a treewalker plan/ |
Puppeteer exposes the information about the browser's a11y tree in a couple of ways:
via Accessibility.queryAXTree to query elements by the accessible name and role. This allows Puppeteer to implement element selectors based on the a11y tree data.solved via https://w3c.github.io/webdriver-bidi/#collect-nodes-using-accessibility-attributesAdditionally, there were requests recently to include A11y tree information into WebDriver https://goo.gle/chromedriver-a11ytree. I think we should discuss if we want to add these capabilities to WebDriver BiDi.
The text was updated successfully, but these errors were encountered: