-
Notifications
You must be signed in to change notification settings - Fork 4
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
ARIA AT Automation meeting: March 14, 2022 #17
Comments
For additional context, also see the Status Report for ARIA-AT Automation from December 2021. |
We need to move this meeting to March 14, as we needed some more time to prepare. Apologies for the late change. In addition, I think it might be a good idea to split into two meetings, one where we invite AT vendors and later one where we invite AT automation tool implementers. This is so we can properly prepare and have more productive discussion with each group. To clarify, I suggest:
|
Meeting details at https://lists.w3.org/Archives/Public/public-aria-at/2022Mar/0004.html |
Meeting minutes: https://www.w3.org/2022/03/14-aria-at-minutes.html Themes of discussion:
We'll file new issues for each topic. |
Meeting minutes from yesterday's meeting: https://www.w3.org/2022/03/28-aria-at-minutes.html A few points I recall from the meeting and from scanning the minutes:
|
Next ARIA AT Automation Group Meeting is today: #18 |
The next ARIA AT automation meeting will be on March 14 at 3pm ET. (The meeting was moved from Feb 28.)
As discussed in yesterday's call, we plan to invite screen reader vendors as well as screen reader automation framework authors to the next meeting to review the material we have so far and align on the guiding use cases for screen reader automation standardization going forward.
Suggested discussion topics:
The text was updated successfully, but these errors were encountered: