-
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
1.4 Prioritization #1884
Comments
Relevant minutes seem to be https://www.w3.org/2023/05/03-aria-minutes#t01 @spectranaut Not sure if it makes sense to keep this issue open. |
Thanks Peter -- I have a note to go through the discussion and make sure there were issues for all the topics discussed, so I'll assign this to myself. |
Here is a summary from some of the main ideas from this brainstorming. Projects mentioned that are actively being worked on:
Projects that do not presently have champions or ongoing work:
|
@spectranaut should we create a 1.4 project? (I was hoping we could clean up the existing projects on an editors call some time, too) |
Hmmm if you would like, it sounds like a good idea but I'd like to understand your vision/use of the projects a bit more! |
@pkra should this be on the editors meeting? |
Sounds good. |
@FabasoftAccessibility, and me would like to work on following projects:
|
Discussed during TPAC this week, notes here: https://www.w3.org/2023/09/12-aria-minutes#t03 |
The next F2F can be a time for us to think about what to focus on for ARIA 1.4.
We can start the F2F with the opening question, "What do you want to work on in ARIA this next year?"
This could be aspiration (something big that you haven't begun and/or that can't do alone) or immediate (something small or something you have already started). It can be related to the spec, new support, better integration, process or test related.
The goal is to understand where our interests and motivations are as a working group, and where we can collaborate and focus on in the next year.
The text was updated successfully, but these errors were encountered: