Meeting minutes
Easy Checks
Shawn: Very excited that the wish list item of updating Easy Checks is now in queue. It was one of our most used resources and we are eager to update it. No need for you to focus on it yet. Eric's team will take it up next, and EOWG will talk about it when they are ready.
Kris Anne: Take a look if you wish and expect to see more of it in a couple of weeks.
URI for ARIA APG (plus, title for redesigned resource)
<shawn> https://
Shawn: Background is that ARIA Authoring Practices Guide folks came to us asking to get out of TR space and into the more useful WAI site space.
... (fyi, since we put the COGA design patterns in WAI space, analytics show that it has gotten a lot more use now that it is a nicely designed WAI space, compared to the TR doc published last year.)
<kevin> Link to current draft: https://
<shawn> project info: https://
Shawn: We've been working with them on the UI and there are a few things that remain inconsistant and we need to make some decisions. The overall project is meant to be broader than ARIA in the future. Though not sure of timeline. An issue is the URI. Many want w3.org/WAI/ARIA/APG
... We have a good redirect system so that is a consideraion for not having to make final decisions now.
Kevin: Authoring Practices is to me a vague term - what is an authoring practice? I put in GitHub some less jargony terms. I was puzzled about focus - this is about how to use ARIA properly, how to build nonstandard interactive widgets. Stay focused on that is my feeling.
<shawn> The URI the TF prefers is /WAI/apg/
Shawn: They favor acronyms
Kevin: That is making an acronyn of something already unclear - seems like obfuscation.
<estella_> +1 to Kevin
KrisAnne: I don't like apg, needs something more clear
Shawn: Though, those in-the-know do know that phrase/term and may look for that
Kris Anne:are we trying to be an insider resource or reach out to others?
Kevin: authoring practice is not a common term
Mark: It does not work for me, does not suggest what it is meant to suggest
Shawn: What would you call it if you wanted it to be more clear?
… remember it is for content developers- there is a different resource for user agent implementers (e.g., screen reader vendors)
Kevin: I would search for intro to aria, aria patterns, aria guide, something like that
… could maybe use aria patterns, and at this time that term does find this resource when I search. Those are the kind of terms a developer/content author might search for.
Shawn: Is the audience for this beyond coders?
Kevin: Interaction designers certainly, they need accessibility annotations so they will be using this info as they build the interactions and noting it in the design. Thinking of the public sector space.
Michelle: I call it ARIA authoring practices
KrisAnne: I just call it ARIA, not the full name or title. Just refer to it as aria
… I point them to the authoring practices but don't use the full name - will say, "Look at the 'ARIA reource'"
Howard: We are thinking of the URI, not the resource itself? The title of the draft is currently "ARIA Authoring Practices". I have seen Authoring Practices resource used a lot, I have gotten used to it - would simply go with that.
Kris Anne: SEO considerations...
Michelle: I don't use URLs to search, why is this an issue? People will search by title or topic.
Shawn: Some users do look at URLs. We are sharing ideas, moved from URL to the title, seems somewhat important for consistency. EO's role is to advise so I appreciate the time and effort.
Kevin: Interaction designers are an improtant audience and I think they have no clue about "authoring practices", There is no clarity around how to find or if I have found the right thing.
Shawn: Yes the comfort level of knowing you are where you need to be.
KrisAnne: And this is MORE than an authoring practice. There is more here than just what was in TR space.
Shawn: I think for now it is the same content just restructured.
Kevin: You could add 'The' and make it the definitive guide to take the authority position. The ARIA Guide.
<Michele> +1 to adding something like "the" to help people know they are in an official resource
Estella: I agree with Kevin, authoring practices it is a general term and Guide says it is to provide guidance, guide is more simple direct language and is self describing and clear.
Shawn: The purpose is for content authors and designers, not for user agents like screen reader programmers. It will also provide support.
… they will add how assistive tech supports various ARIA specs
Kevin: On the question of who is this for - it needs to recognize the significant audience. They may be authors but don't think of themselves as such. This is 90%, maybe 99% of the audience. User agent implementers only a tiny bit and they already know aboout ARIA.
...We need this to reach the group that think of themselves as designers, developers, etc, not authors.
Shawn: Point taken. Agree. I recind my comment about different audiences for somthing like "The ARIA Guide".
Accessibility of Remote Meetings
KrisAnne: The data from the survey we did in October on the resource never made it to the group that asked for it, so we are revisiting.
Shawn: The point was what should be in WAI pages vs TR space. Since we did not get it submitted and don't have an editor to help, we may let it go for now. it is possible, once we get in sync we may help make that transition.
KrisAnne: And please do add GitHub issues if you have comments for that doc.
Shawn: Yes as an individual, please submit through GitHub. We won't have time for working through EO group comments before next publication.
Work for this Week
KrisAnne: There are a couple of open surveys, please check work for this week. Please take the time to complete those. Monkey review for the course list is last chance, speak now phase, so please take a look.
Shawn: Thanks to all of you who have made the time to make considered, careful commenting and review on those draft resources - thanks so much!
KrisAnne: And if you haven't yet done it, there are still a couple of days.