WAI Coordination Call -- 13 Sep 2017

Confirm scribe, agenda, next meeting date

<Judy> NEXT MEETING SEPT 27

Update on ACT rules draft & format

<Kim> Judy: there was an announcement yesterday

<Kim> Michael: Published by the working group – everything is in the announcement

<Judy> https://www.w3.org/TR/act-rules-format/

<Kim> Judy: This is work that we been doing to try to make sure it's easy to test this stuff. Updated plan for the rules, format lays out what would be included in it. If you're interested in how accessibility gets assessed you may want to look at the draft rules format just to make sure that this looks like a target to which the organization or people you know of trying to improve accessibility...

<Kim> ...and standardized onto – I encourage people to look at it even if you're not directly involved. May have improvement on how stuff gets assessed in the future

How is pre-planning for TPAC joint meetings going?

<Kim> Judy: there were some groups that are meeting there but wanted to get some coordinated meetings in progress – anything to report on that

<Kim> Janina: looking for a wider review before we get into that meeting in terms of whether we care about any AT beyond screen readers around input events

<Kim> Lisa: the COGA task force will have five people. If anyone wants to coordinate or have participation it would be good. We don't actually have a room. Just be in touch – we just like to join in with other people's conversations and maybe will find a quiet corner to do a bit of work as well.

<Kim> Judy: Is there any piggybacking that could work with other groups

<Kim> Judy: a few questions that have come up in one or two discussions recently on plans for 1.2 – how much of the discussion at TPAC will focus on 1.2

<Kim> Joanmarie: there are different flavors – but if we just want to call it the broad umbrella of 1.2 that's pretty much both days

<Kim> Judy: there had been some architectural, tag interest on that in a previous incarnation. I'm wondering if that's coming up again.

<Kim> Joanmarie: AAM's is on the list

Rechecking for interested parties in SVG accessibility

<Kim> Judy: there had been some concern for a while that the SVG group might not be continuing – it will be continuing. It will be resuming

<Kim> Judy: I wanted to check in to see who people know of who are interested in this area – people who are more active previously but maybe in new organizations – anyone in your groups who are aware of who may be interested in plugging into the SVG accessibility work again

<Kim> Judy: Chris or Liam Quinn will be doing the outreach for getting this going again

<AWK> +AWK

Question on work estimate for use case development

<Kim> Judy: A question that comes up from time to time in different accessibility groups. Background – when W3C is exploring a new technology or has launched standardization in a new technology there are very few people who already have both the expertise and that technology and standards background and interest. One of the best ways to prime the pump for getting some accessibility standardization

<Kim> wo

<Kim> rk going is to present use cases – this is how people would use the technology – a lot of engineers don't have a background in this. Sometimes it's hard to populate these use scenarios. So I've been getting some updated requests for use case development recently.

<Kim> Judy: for those who've done them before or who wish to be doing them but lack resources I'm curious what as needed for resource development for these

<Kim> Judy: any thoughts on how hard it is to pull together good use cases – sometimes it's not even a chartered item, extracurricular

<Kim> Judy: in some cases my impression is some of the task force work – if we had use cases where scenarios would it have been easier for people to picture how some of these things might work

<Kim> Judy: I'm looking for comments both on usefulness of use cases and also effort in doing those. I'm trying to get internal input for an internal discussion on whether we should do more to plan for resources for these

<Kim> Tziya: not necessarily from the accessibility perspective but I've done a lot of use cases for publishing and it is a tremendous amount of work but now that we are working on the actual specifications we go back to it – if you don't actually document use – the use cases are invaluable, most people don't know how to write good use cases

<Kim> Judy: standard format or did you do custom to the situation – what did you do

<Kim> Tziya: we looked at the web annotation use cases because there easy to read

<Kim> Lisa: I find use cases extremely useful. It's probably halfstep away from what our core mandate is to do – requirements. Having use cases is not mission-critical but it's useful. It might not be priority 1, but it might be priority 1.1. it's extremely useful if people don't understand what you're doing and why you're doing it.

<Kim> Janina: some come very quickly, on the other hand we've had trouble with the Internet of things use cases

<allanj> in the LVTF requirements doc we create scenarios to explain issues and how they impacted user need http://w3c.github.io/low-vision-a11y-tf/requirements.html. it helped the group firm up our concepts and explanations. haven't had much feed back from people who read the document.

<Kim> Judy: my impression was getting ideas was easy getting them developed to a level of usefulness was hard

<Kim> Janina: on WoT use cases, we are making progress but it has been hard

<Kim> Judy: the web TV use cases – do you think they lead to features

<Kim> Janina: fairly elaborate document, what we provided them is very definitely part of it

<tzviya> annotations use cases for reference https://www.w3.org/annotation/wiki/Use_Cases

<Kim> Jeanne: I found them very helpful in UAAG – particularly for presentations, having them in mind particularly with the browser developers they were so handy to have. We are definitely going to be doing – writing these cases for silver. I would be very interested in seeing samples of what other people have done for use cases so that we can look at what's the best model – what is a...

<Kim> ...good use...

<Kim> ...case in the accessibility realm. So I would really appreciate if you could share those links – I would like to see them

<Kim> Judy: I've sent people to the UAAG use cases many times, but my impression is it was a lot of work

<Kim> Jeann: it didn't take that long – it took a focused effort. We got a group of people sat down for a day and wrote them all

<Judy> scribe: Judy

Kim: I want to echo Jeanne.
... they are extremely useful, both in explaining what you need, as well as why it's important.
... it makes the dryer language more accessible, because it makes the technical aspects come to life for people.
... and we were able to knock these out in a day.
... once we had them, others flowed, easier to bring along.
... use case very helpful. A lot of developers have trouble picturing users. Requires a leap.

<tzviya> I think sitting down for a day to write use cases is a really good approach

<janina> Web & TV at:

<janina> https://www.w3.org/WAI/APA/track/actions/2135

<Kim> Judy: any other comments on use case development. developers have trouble picturing users

<scribe> scribe: Kim

Janina: URL – cloud browser elaborated on video description, others to elaborate in there if you want a recent pointer that's a good one

Key upcoming conferences, accessibility & not

Judy: thanks – if there are others to put into the minutes that would be a useful collection
... around this time of year usually call for papers comes out from CSUN conference. Call for papers usually comes out the 14th, tomorrow. Heads-up and also give people an opportunity if they're looking for co-presenters. Also inviting people to mention other conferences The typical concern that comes up is that we're talking to the choir.

Andrew: there's Accessing Higher Ground, but that's coming up soon

Any WAI meetings planned around CSUN

Judy: are there plans for face-to-face meetings at CSUN – curious if any plans yet

Jeanne: the silver task force is planning our big prototyping workshop before CSUN. Not large number of people but large in importance for the project

Judy: how will you be promoting that – regular lists

Jeanne: will be coordinating – starting to move in that direction

Andrew: we have not talked about it in the accessibility guidelines group, but I have to imagine that it'll come up soon. Our scheduled deliverable is June so CSUN is in that window of time where we might need more time together, so answer is probably yes but not figured out yet.
... we will have published CR by then

Judy: the speed with which you get through CR is roughly proportionate to the clarity of materials – the more planning and structure the faster you will get through

Milestones, publications, announcements check

Topics & reviews for WAI IG?

Judy: (for milestones, publications, above) one publication yesterday – others? Republishing of ARIA next week, WCAG 2.1 yesterday, Core-AAM next week
... we are next scheduled to meet on September 27, Rich will be joining us for that call

<Judy> s/we are scheduled to meet/(for other business) we are scheduled to meet/

- DRAFT -

WAI Coordination Call

13 Sep 2017

Attendees

Contents