– DRAFT –
ARIA WG

New Issue Triage<https://bit.ly/3ux6hXE>

jamesn: braille role description is new in one dot three and we should get the examples right.

jcraig: already fixed it

https://bit.ly/3ux6hXE

jamesn: next one 1406 ARIA spec.

Scott_O: it is something could be editorial updates for aria-current or need to define who so people toggle something.

jamesn: it looks like a switch or radio

Scott_O: its more like radio button. you can not unselect

jamesn: is it 1.3 issues?

jamesn: if it is minor then we can have it for 1.3

Scott_O: will take it

New PR Triage<https://bit.ly/3kivsbH>

jamesn: some of the PRs need some review

Matt_King: I think putting you know if there was wonderful support for article enroll description and screen readers it'd be awesome if you know the article key took you from side to side and I called it an article because you use role description

<CurtBellew> https://github.com/w3c/accname/pull/112

<CurtBellew> JN: who should review this - to Bryan

Meaty topic for next week<https://bit.ly/3pUi5PU>

<CurtBellew> jn: list of potential deep dive topics for next week

<CurtBellew> jn: peter do you want to propose the mobile touch topic

<CurtBellew> jn: should we take a week off from deep dives because we've had a couple in a row?

<CurtBellew> jn: anything urgent?

<CurtBellew> carmacleod: ok why don't we leave it open?

<CurtBellew> jn: hearing nothing let's move on

onboarding - please provide input<https://github.com/w3c/aria/issues/1401>

<CurtBellew> jn: two new members on this call. introductions

<CurtBellew> welcome Tammy Campoverde and Jory Cunningham

<CurtBellew> jn: onboarding. we're looking to improve this process

<CurtBellew> jn: We know there are many things we need to do but this is an open forum. What information might you have needed when you started out in this group that didn't have access to

<CurtBellew> michaelc: this is also a topic in the working group. A suggestion has been for me to do an introduction orientation video

<CurtBellew> michaelc: it may make sense to do one of those fo rhe aria working group as well

<CurtBellew> jn: I have a task to create an email when a new member joins but I haven't been able to do that yet

<CurtBellew> MK: Does the task force have a similar email?

<CurtBellew> Michaelc: joining a task force doesn't trigger the email

<CurtBellew> Michaelc: Getting added to a working group does not add you automatically to a task force.

<CurtBellew> MK: I remember back in the beginning I remember trying to sort a lot of concepts about ARIA itself out.

<Zakim> jcraig, you wanted to mention new people can filing issues or pull requests against the markdown readme at https://github.com/w3c/aria/

<CurtBellew> jcraig: We do have a readme and I would encourage any new people or people who have been around to read that and if you find something that needs to be added to the readme , please file an issue

<CurtBellew> jcraig: An "it would be nice to have this" in the intro document request

<CurtBellew> jn: this would be best from recent joiners

<CurtBellew> jn: we want as many people to be involved as possible

<CurtBellew> Jemma: In the beginning this group can be a little intimidating. Please feel free to reach out

<CurtBellew> MK: The notion of mentorship is really a pretty good idea. Maybe we do topic specific mentorship.

<CurtBellew> MK: There might be things where you get mentored from multiple things in the group.

<CurtBellew> JN: A buddy system when they join would be a good idea

<jcraig> PR https://github.com/w3c/aria/pull/1409 is now ready to merge with the changes we just discussed.

<CurtBellew> CurtBellew: An email group or some other way to ask questions related to processes etc

<CurtBellew> JN: There is an unofficial Slack channel

<CurtBellew> Jemma: Can we have a wiki document. I think people might be worried about sending an email to the entire group.

<CurtBellew> JN: Slack would be a great place to find answers to process questions. So that could help

<CurtBellew> Jemma: Can we have a page on how to do the basics in github with respect to ARIA?

<CurtBellew> JN: There are great guides on github

<CurtBellew> Jemma: this would be more about our repository and our specific procedures

Updated aria-setsize and aria-posinset to clarify usage for authors<https://github.com/w3c/aria/pull/1332>

<CurtBellew> JN: waiting on malanie so we can skip this one

1.2 Status

<CurtBellew> Harris: I've posted a comment in the previous issue wrt onboarding.

<CurtBellew> ifran: do we have any of the quick keys documented

<CurtBellew> JN: Michael, where are we?

<CurtBellew> Michaelc: The doc was supposed to be published on Tuesday but ran in to issues. Fixed those and tried again today and had more issues. Monday

<CurtBellew> JN: is there a way to try to resolve the issues today rather than waiting until Monday?

<CurtBellew> Michaelc: It's on my todo list

<CurtBellew> JN: let me know if I can help

<CurtBellew> JN: no virtual celebration for 1.2 release. soon

<CurtBellew> JN: hopefully next week we will have 1.2 candidate out the door

1.3 planning - focus areas??<https://bit.ly/37JmRtA>

<CurtBellew> JN: This may morph in to the deep dive topic for next week

<CurtBellew> JN: we planned to have our first working draft out by now - 1.3

<CurtBellew> JN: We are running out of time to get features in to 1.3. We already have a lot of braille support and annotation support. We don't want to hold those up for a long time

<CurtBellew> JN: so we don't want to put a lot more in. So propose we have a small focus area that we put a lot of work in to so that we can call 1.3 done and move on

<CurtBellew> JN: An ARIA where I believe we need a lot of work is live regions

<harris> +1 to working on live regions

<CurtBellew> jcraig: acknowledge that live regions have a lot of areas to delve in to

<CurtBellew> jcraig: anything in particular?

<CurtBellew> JN: We have a lot of issues. The fact that they're read once and then done etc

<CurtBellew> JN: problems of using a part of the page for notification type messages

<CurtBellew> MK: If you're thinking one to two month timeline then this is probably better for 1.4

<CurtBellew> MK: I'd like to get out 1.3 as soon as possible

<CurtBellew> MK: could we focus on aria-invalid as a compliement to annotations rather than live regions

<CurtBellew> JN: that does seem more like a bug fix that a focus area.

<CurtBellew> MK: agree, it just feels like it would be great to get 1.3 shipped sooner than later and the live region topic is a really big one

<CurtBellew> MK: lining up the browser support is a big topic

<CurtBellew> jcraig: would be AT support too.

<CurtBellew> jcraig: We would need to decide everything we need to get in to webkit before May which seems like it's not quite enough time to get it out this year

<CurtBellew> jcraig: Live regions do seem like a 1.4 things

<CurtBellew> JN: So no major focus area for 1.3 so we can get the release out sooner

<CurtBellew> carmacleod: what about value-text?

<CurtBellew> MK: value-text and aria-invalid would be good

<CurtBellew> JN: what if we take the ARIA call for next week and make it a 2 hour call to look through issues

<CurtBellew> JN: Things that you would like to work on

<CurtBellew> MK: use the deep dive time?

<CurtBellew> JN: yes , that's my proposal

<CurtBellew> JN: to get some firm plans for 1.3

<CurtBellew> JN: The proposed meeting would start at 9am Pacific on the 4th of March

<CurtBellew> Jemma: Which issues should we be looking at?

<CurtBellew> MK: propose we focus on the ones that have been triaged for 1.3

<CurtBellew> JN: I'd agree with that unless someone has something they really want to work on and will do the work themselves

<CurtBellew> jcraig: how would the new attendees prepare?

<CurtBellew> MK: send out an email with the list of issues. Make a URL for that. Would be a guide to open issues

<CurtBellew> jcraig: a link is one thing but a nice quick walk through would be benificial

<CurtBellew> Tammy: would be nice to get that. Would be nice to shadow somebody. So we get an idea of what is the correct process

<Jemma> https://github.com/w3c/aria/labels/ARIA%201.3

<CurtBellew> JN: good idea. I don't want to volunteer anyone. One thing is that we are all doing the work in small slices during our days.

<Jemma> this is the label with aria 1.3 in github

<Jemma> https://github.com/w3c/aria/labels/ARIA%201.3

<CurtBellew> JN: Tammy, I could do a short call with you to walk through some things though

<CurtBellew> jcraig: I could hang around on this call to do a quick walk through of the milestones and the pull request process.

<CurtBellew> CurtBellew: can I be in that call?

<CurtBellew> jcraig: sounds great.

<CurtBellew> JN: let's wrap this up. next week plan on a longer meeting