Mobile Accessibility Task Force Teleconference -- 28 Aug 2014

<trackbot> Date: 28 August 2014

<KimPatch> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Techniques_Resources

http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Techniques_Resources

<scribe> scribe: Kathy

<KimPatch> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Techniques_Resources

Kim - Techniques resource review guide is a step by step example on how to make changes

Kim- need to fill in all the columns on the technique assignments. See G10 for example

<KimPatch> Kathy: the general gist of what we are going to do in terms of procedure is we are having people sign up for the different techniques – many of you on the phone have already done that. Over the weekend of the filling out the new techniques we are going to do as well so you'll be able to sign-up for those starting on Monday. Based on those assignments would like people to be working in...

<KimPatch> ...submitting these to the group so that we can get them on a survey. So what we'll do is once an item is finished will be collecting all of the items into of weekly survey and will have everybody do comments on them – except as proposed, except as proposed with changes, or do not accept and you can then enter in comments for all of those

<KimPatch> Kathy: the reason for the surveys is we have some asynchronous users.

<KimPatch> Kathy: the deadline to get the items to the WCAG working group is November 18. We will submit as we get these done. In order to give the group enough time to review all the items are deadline is November 18. The items that get submitted to the working group by November 18 will be in the March 2015 release of the WCAG techniques. We need to get as much done as we can by this date. We will...

<KimPatch> ...do some new techniques as well. I'll prioritize to suggest which new ones we can get into the March release so we can get this information out to people. If we don't get out before November 18 the next releases six months after March, so them were looking at the summer.

<KimPatch> Kathy: we would love to get as many as done as possible especially since some of them are small.

kim- on the process, click on the link to the left. That page, is the comments, make sure you start at the bottom and put in the suggested chnage

<jon_avila> +1

<KimPatch> take up next

Techniques resources review:

Kathy: Jon completed G4

Jon - suggested a third example

https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/G4

<KimPatch> Jon: we could of just included tapping, but I tried to provide a more device independent example

Techniques review: G9, G53

<KimPatch> Jon: originally reviewed by Jeanne, I added a second example

<KimPatch> Kathy: alternative for via

https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/G53

http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/G53.html

<KimPatch> Kathy: Alan had some suggested changes. This has a lot of user agent and assistive technology support notes and it's got several different examples – where you can have the link text of the sentence together. Originally we looked at this and said we need to have user agent support notes, mobile is to be added. Alan had additional edits – additional example. He didn't address the support note.

<KimPatch> Kathy: the question out to everybody is there are different key commands for iOS and android that I know of for reading paragraphs and text – if we're looking at user agent support notes what devices do you think we should cover

<KimPatch> is iOS and android sufficient at this time?

<KimPatch> Kim: those of the obvious ones, there are many, and there are many that do things that the obvious ones don't do – don't know how to address that

<KimPatch> Kathy: when we are adding in user agent notes how inclusive do we have to be – right now it's pretty old, fairly out of date as it is

<KimPatch> Tom: should we have Microsoft in that?

<KimPatch> Kathy: is anyone on the call doing anything with Microsoft mobile?

<KimPatch> Jon: I have some devices – are we going to include surface, tablet as well?

<KimPatch> Kathy: surface you can just put jaws on it,

<KimPatch> Jon: that's Pro, not RT

<KimPatch> Kathy: I've done a little bit with Windows, but if we have people who are during more on Microsoft that would be great

<KimPatch> Jon: I have devices, I've used them, it would certainly take time. But I was looking through a lot of these techniques a lot of these questions came up where I think it would be good to actually collaborate and discuss some of these, and then we could delegate certain tasks. For this particular one I can research Windows phone and window surface support

<KimPatch> Tom: should we reach out to Microsoft

<KimPatch> Jeanne: I think that's a good idea – for Microsoft all they have to do is contact their rep and they can be put into the group. If there's someone from Microsoft we want to invite let me know

<KimPatch> Tom: we have enough contacts, we might be able to provide an introduction, let me look into it and find the best person to work with

<KimPatch> Jon: just looking at the Windows phone, swipe very similar to iOS and android. We can have a general mobile touchscreen gesture to say if you are using a screen reader with a mobile device to swipe previous or next you can… That is perhaps what Alan was getting at. And then we can put in an example for narrator on the surface.

<KimPatch> Kim: the other device is the fire phone

<KimPatch> Kathy: iit's actually very interesting, and I can play around with that, has its own screen reader

<KimPatch> Kathy: only so much we can do – scope

<KimPatch> Jon: is the reader different

<KimPatch> Kathy: I can look and if it's different we can make you know, otherwise it's the same

https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/SCR37

<KimPatch> Kathy: with this one we will do more research – Jon you can add Microsoft notes, I will add notes on the fire phone and we can look at that next week

<KimPatch> Kathy: SCR37

"The tab and the enter keys may not work on tablets and smartphones operated via bluetooth keyboards. On some devices and operating systems, arrow keys can be used to move the keyboard focus instead. Focused elements may need to be activated via other key combinations such as control-alt-space (iOS)."

<KimPatch> Jon: on android there can be tab support and also support with arrow keys. can get confusing, certainly focus, whatever commands available, device independent way of exiting the dialogue. There are things that could be done consistently across all platforms

<KimPatch> Kathy: I think this was to be added as a note, not as an example

<KimPatch> Jon: do the notes appear in the description area?

<KimPatch> Kathy: I don't know where this fits in – we should wait until Detlev is on the phone

<KimPatch> Jon: I'm looking at tab order, we should probably change that to focus order to be more general

<KimPatch> Kathy: number two also says check that the dialogue can be open and tab to the area and hit enter – I think that is what he was getting at you might not be able to do this

<KimPatch> Kathy: encouraging people to sign up for more techniques, also shoot us an email if you have one that's ready that would help out.

<KimPatch> Kathy: if you have anything else that should be discussed on these, it's fine to put that into the summary and we will put that was into the surveys and discuss as well. Do what you can, and add notes if we need to find more information or anything like that – don't want that the holdup discussions

<KimPatch> Jon: was looking at some of these and would like to discuss – can we do part of the meeting getting some feedback

<KimPatch> Kathy: good idea – we can make part of the meeting, maybe first 15 minutes to do discussion and if there is nothing, then we can move on to the rest of the agenda items

<KimPatch> Kathy: a few minutes left – can look at techniques and sign up for a few more. I'll have the list of new techniques by Monday and we can sign up for those as well

<KimPatch> rsagent, make minutes

- DRAFT -

Mobile Accessibility Task Force Teleconference

28 Aug 2014

Attendees

Contents

Techniques resources review:

Techniques review: G9, G53

Summary of Action Items

Scribe.perl diagnostic output