Mobile Accessibility Task Force -- 19 Nov 2013

<MichaelC> scrib: KimPatch

Kathy: Introductions

<MarcoZ> Hi there!

Kathy: give your name, location and a little bit about yourself
... CEO of interactive accessibility. I'm in the Boston area. I'm oing to be co-facilitating this task force with Kim Patch. I've been working with companies within the United States on accessibility including usability testing with mobile devices – both applications and websites.

<MarcoZ> Marco Zehe, Hamburg, Germany. I'm accessibility QA engineer and evangelist at Mozilla.

Alan Smith, working on some apps facing the challenges of dealing with legal issues of lack of standards for mobile accessibility in the eyes of some folks. So I'm excited to behere, happy to be involved with the team.

<Kiran_Kaja> Hi, I am Kiran Kaja, Accessibility Program Manager at Adobe based in Europe (London). Very actively participate in Accessibility standardisation. Last W3C TF involvement was with WCAG2ICT Taskforce.

Andrew Kirkpatrick, work on accessibility, also one of the cochairs of the WCAG working group

David Todd, IBM

Deitlef Fischer

Gavin Evans, based in Wales, multi-platforms and gaming

<MichaelC> d/Deitlef/Detlev/

Kira Kaja Adobe

Karen McGrane, based in New York consulting with lots off clients on mobile web – content management, supporting mobile on different devices

<AWK> I didn't say so but I'm based outside of boston

Michael Cooper, staff contact for the Web content accessibility guidelines working group which is one of the group sponsoring this task force, and also protocols and formats and indiUI working groups. Go to person for technical issues along with Jeanne Spellman.

Peter Thiessen: I'm in Spain, JavaScript developer, work with WAI ARIA, cloud stuff

<Kathy> http://www.w3.org/WAI/GL/mobile-a11y-tf/work-statement

Kathy: Reviewing the work statements
... creation of mobile techniques for HTML 5, development of design guidance and mobile accessibility best practices and review of the existing resources outside of the WC3
... get started by looking at the existing resources – what's out there, what's public knowledge – as well as looking at the W3C resources that are already there. Set up a wiki. Wiki organization input.

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

Kathy: Describing the wiki organization, want your feedback. The idea is to collect the information that's currently out and available so that we can review it before starting to think about what techniques, best practces, design best practices we should start reviewing and collecting under the WCAG guidelines
... first to topics – broke out applications versus websites, maybe out to be the same. mobile design separated out iOS and android, should we have other platforms in that list?

<MarcoZ> Firefox OS...

Kathy: platform accessibility features what's there now, we have iOS and Android, could put more

<Alands> Other platforms, Windows 8

Kathy: what are other resources that you know that are available that we could collect that don't fit under one of these headings and we could consider adding?

<MarcoZ> Kathy: Firefox OS. Also, on Android, there's a multitude of browsers. Some distros come with Chrome, some with Firefox for Android, some with the old stock browser.

Alan: Windows 8 and Blackberry

<Peter_Thiessen> +1 Alands comment about adding BB and win8

Kathy: wiki is open for everyone to edit – idea is everyone can go when we want to collect the resources that people already know are out there. We want to go in and put in everything that we know is out there already – get a really good resource list of things that are there so that we can all go through and look at it

<AWK> Doesn't each wiki editor need an account to enable editing?

Kathy: we will add Windows 8, Blackberry and Firefox OS

Detlev: one of our main outputs is test results – would it make sense to have a section on test results for the different operating systems?

Kathy: testing means you've tested with someone who's using voice over an iPhone type thing or something different?

Detlev: yes – to what extent accessible, a task like opening a calendar on Windows 8 – the IOS operating system just to get an idea of how well they perform. Is that useful information?

Kathy: I think that's useful information – helpful to go in there and know. Maybe under five we could put some usability test results.

Alan: May be a heading of testing and we can have things under that, testing guidelines, testing results

David: what having a section about the different mobile screen readers be helpful?

Kathy: yes, I think that can go under mobile accessibility platform features

Kiran: thinking about what Detlev was saying, would it be helpful to have some sort of accessibility support matrix or compatibility matrix. So I'm thinking about we have these different platforms IOS, something about mobile web, we start developing the techniques, we find that some browsers have support for accessibility elements and attributes and others don't. So it's probably the output...
... that would come out of the task force put if we can have some sort of compatibility matrix on the wiki when we find things that are supported in one browser and not the others we can add that.

Kathy: I think that's a great idea. Do you know if something like that exists or is this something we have to start from scratch?

<Peter_Thiessen> Agree with Kiran, a compatibility table could be a useful deliverable, perhaps something like this for ES5 http://kangax.github.io/es5-compat-table/

Kiran: yes, but probably scattered. Maybe a heading under accessibility features and we can take it from there

<MarcoZ> Kathy: Kiran_Kaja: The Paciello Group might have started or done something like this already, I know they have a browser feature matrix, but don't know if that now also includes mobile browsers.

Michael Cooper: can send information out about using the wiki

<Kiran_Kaja> I can login with the W3C account

Kim: one minute wiki tour – make sure you are logged on, click edit to edit, help button along the left

Gavin: what type of apps – for gaming as well?

Kathy: we have to determine what the focuses and prioritize the items that were going to work on. We can later have discussions about that so we can define that work moving forward. I don't have a complete answer for you at this time. It depends on what we determine the need is and what our priorities are.
... any other thoughts on mobile resources?
... what I'd like everybody to work on over the next couple weeks is really adding information to the wiki under each of these – everybody will see what everyone else is adding so before you add check to see that it's not edit already. But if you could put in the resources that you know that are out there – things that you have done, anything that is public you can go in and really...
... populate the wiki when we come back on our next meeting we will go through those resources and start talking about the information that's currently there and walk through that information so very pretty to take some time and add to the wiki that would be appreciated

<MarcoZ> Kathy: We're currently collecting lots of experience in making the Firefox OS UI accessible. Lots of CSS tricks that actually don't fool the a11y APIs into thinking stuff is really invisible, though the touch screen doesn't display it. Will make an effort to gather all the info in a sensible manner.

Kathy: times for the task force

<Kiran_Kaja> This time slot is good for me

Kathy: We are spread across the world – what time works well for people, what day of the week works well for people and we can get this regularly scheduled

<MarcoZ> Same for me.

<Detlev> time is fine forme

<Alands> Alan, I'm flexible with time and date

<DavidTodd> This time slot is good for me.

<gavinevans> This time is very good for me

<Peter_Thiessen> +1 this time (will try to take a short lunch on Tuesdays :)

Michael: interest from China, accommodating Australia, US and Europe – maybe even alternating times to accommodate that

Kathy: the challenge right now is what to do. Your idea that alternating schedule would work. But it would be a little more challenging to remember when the meetings were.

Michael: another survey, your general availability for this day and cover 24 hour time period to get a sense of what might work and keeping open the option of having alternating times might help in the scheduling. You can deal with some of the confusion by posting times and dates in the agenda

Kathy: can we use a regular survey

<Kiran_Kaja> Doodle is OK for me

Michael: can try to get regular survey set up this week. I've been told that doodle is reasonably accessible

<Zakim> MichaelC, you wanted to say we shouldn´t make a decision about how good this time with just the people for whom it was good on the call

Kathy: I'll send out a Doodle and we can go from there
... next steps are to fill out the mobile resources – really get a good idea of what currently is out there. Beyond that is to look at the objectives under this task force and really start defining the work that we want to do and what we think is the need.
... what I'd like people to do over the next few weeks is at the resources, and then start looking at what everyone has added. So when we get back we can start defining the work that we do moving forward.

Michael: if we can ry to have a scheduling done so we can have a meeting by the week of December 2

<Peter_Thiessen> sounds good

Kathy: so aiming to look at the mobile resources the week of December 2
... questions or other comments?

<Peter_Thiessen> cheers all

<Detlev> bye evervone!

<gavinevans> Thanks everyone

<Alands> thank you.

- DRAFT -

Mobile Accessibility Task Force

19 Nov 2013

Attendees

Contents

Summary of Action Items

Scribe.perl diagnostic output