You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across web-test-runner-voiceover on GitHub while looking for projects that automate screen readers. I’m part of a web standards group called ARIA-AT that is also looking into automating screen readers, for the purpose of conformance testing.
We're trying to standardize a new API to programmatically control screen readers that we hope will be implemented by vendors to unlock new functionality and to more reliably test the behavior of screen readers.
We’d like to include the input of tooling authors like you. If you're interested in participating in this effort, you're very welcome to attend the next ARIA-AT Automation meeting on February 28 at 12pm PT / 3pm ET. See details here:
There has been a change of plans since we need some more time to prepare. The new tentative date is March 28. See w3c/at-driver#17
Apologies for the late change, and thanks for understanding.
zcorpan
changed the title
Invitation to web standards meeting about a Screen Reader Automation API on 28th February 2022
Invitation to web standards meeting about a Screen Reader Automation API on 28th March 2022
Feb 24, 2022
Hi @coryrylan,
I came across
web-test-runner-voiceover
on GitHub while looking for projects that automate screen readers. I’m part of a web standards group called ARIA-AT that is also looking into automating screen readers, for the purpose of conformance testing.We're trying to standardize a new API to programmatically control screen readers that we hope will be implemented by vendors to unlock new functionality and to more reliably test the behavior of screen readers.
We’d like to include the input of tooling authors like you. If you're interested in participating in this effort, you're very welcome to attend the next ARIA-AT Automation meeting on February 28 at 12pm PT / 3pm ET. See details here:
w3c/at-driver#17
Thank you!
The text was updated successfully, but these errors were encountered: