-
Puppeteer exposes the information about the browser's a11y tree in a couple of ways:
1) via [Accessibility.getFullAXTree](https://chromedevtools.github.io/devtools-protocol/tot/Accessibility/#metho…
OrKoN updated
1 month ago
-
It's probably way too early to actually take any action here, but one of the common criticisms with applications that do custom UI rendering is that they typically have terrible accessibility, and do …
-
Wooshy has now become very good at swiftly finding and activating all possible UI elements and other text fragments on the screen and in web pages (based on the accessibility information that is expos…
-
This is great project. I'd like to contribute to this as much as I can. But I'm not quite comfortable with Lua. Any chance you might consider using TS (transpiled to Lua, e.g. [TypeScriptToLua](https:…
-
Hello,
I am facing this issue when the following code is being executed. But this is not consistent. Sometimes the element is returned with no error. Sometimes the error is throwing. We are using p…
-
Might this be a source of confusion?
-
From an accessibility perspective it would be valuable to have A programmatic way for alternate input solutions to drive some of the changes. For example, an AT might want to insert the text now that …
-
## What's the problem?
When using a screen reader and trying to read a `Phrase` or `Group` on screen that has a resting animation `Sequence`, there should be a description of the animation. For exa…
-
I noticed that whenever Chrome re-instantiates, the Chrome://accessbility page resets. This severely limits the interaction between the framework and Chrome, my current workaround is to use another br…
-
## Expected Behavior
Would like to manipulate the software
## Actual Behavior
Here is the screen snapshot of the application.
![Application](https://user-images.githubusercontent.com/4430876…