-
Notifications
You must be signed in to change notification settings - Fork 125
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
Discussion tracking for ARIA Notification proposal #1957
Comments
@benbeaudry and I will be attending TPAC virtually from the Redmond area. @douggeoffray isn't registered but would be virtual from the Redmond area. @spectranaut will it be required for Doug to register in order to attend the call for this topic? |
It is preferred but not required |
Since it is tough to tell in the list what has been resolved and what hasn't, I will be planning to open individual issues for various topics ahead of TPAC to help in framing our discussions there. I will plan to post the new issues to the topics noted above that they are related to so folks will know where to look for the new issues. |
I've put together a pre-read with a summary and status of |
Thanks @alisonmaher
I’ve just linked to this document from the agenda page
https://github.com/w3c/aria/wiki/TPAC-2024-ARIA-Meetings
Let me know if that’s OK or you’d prefer something else.
Best.
|
@daniel-montalvo that works great, thanks! |
During the most recent ARIA F2F meeting the ARIA Notification proposal was presented and there were a number of open questions that needed resolution to move forward.
The purpose of this issue is to create a list of those discussion points so that there can be a single unified issue where resolution of those topics are tracked and reported upon, rather than having to dive into various different issues or discussion threads.
The text was updated successfully, but these errors were encountered: