<trackbot> Date: 10 January 2014

<kw> Meeting: Mobile Accessibility Taskforce

<kw> Meeting: Mobile Accessibility Taskforce

<kw> Chair: Kimberly_Patch

Going to be a couple of minutes late

<kw> scribe: agarrison

Mobile Resources

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

Kim, looking at what we have been building and continue with resources

kim, are there any things missing?

Kathleen, yes for phone8 and microsoft surface

Kim, should be a list coming from Alan

Kathy, any further lists people have can be added to the list

Kathy, Andrew Arch could be adding some information and Gavin sent his best practices

Kim, there is room for videos - what are the thoughts on this?

Kathy, looks like a good list - has anyone had a chance to look at the resources?

Jeanne, Yes - The list looks comprehensive

Kathy - Can people start to look through the resources as the basis of our work going forward.

Review Mobile Challenges

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

Kim, have people had a chance to review this

Kim, are there any missing challenges or pieces of information

Jeanne - Yes, there is a mobile accessibility workshop on facebook

Kim, are there any further challenges?

<Kathleen> https://www.facebook.com/groups/346444658786770/

Kim, looking at the missing information... are there bits which we still need to include - it cannot be complete

David, is there anything about contrast.

David, I don't know if iphone and android have high contrast

Kim, have people had a chance to look through them

David, on IOS and Android I don't know if font can be increased to what would be needed for WCAG 2 AA

Kim, other challenges or missing information

Kathy, there are so many places to get information that it becomes tricky to find

Kim, is it that there are so many apps on mobile devices

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

Kathy, when companies are looking for good examples of best practice - there are no lists

Kim, that makes sense - it is difficult to answer questions because there is so much experimentation

Jeanne, developers do not have the knowledge relating to accessibility i.e. aria

David, many desktop developers are adopting aria, but mobile is lagging which makes it difficult

Gavin, we are noticing the same thing - landmark support is lacking

Gavin, we have a wait between vendors and platform support

Kim, does gestures come into this

David, with bluetooth keyboard support this is an issue

Kim, are different developers dealing with it in different ways

David, yes - we have different widgets for different contexts

Kim, whats the solution

David - workarounds

Kim, would that be something this group could do

David, yes that could be something - especially around keyboard events

David, I don't know why Apple didn't do things with keyboard events

Gavin, there are areas which cause problems - but if they can be done in a sequential manner

Gavin: when you have a native app you can give hints
... Widget can be implemented to achieve the same action

Kim: Anyone else

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

Review List of Mobile Assisitve Technologies

<kw> Allistair: many items. On iOS there are good assistive techologies but does not cover everyone

<kw> Allistair: there is more items that could be added

Kathy: Happy to create a matrix of assistive technology
... Matrix would give a good overview

Deliverables - Recap deliverables discussion, brainstorm ideas, and finalize deliverables

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

Kim, new page

Kim, these are the deliverables from last time

Kim, how does this list look - are there other things

Kathy: From the last meeting we came up with a list of things we would like to put together
... The other thing is in the task force description we have the techniques, design best practices and best practices
... Some of the W3C resources are out of date
... What are the most valuable things out there
... What can we do to give people the information they need
... Need a concise list of deliverables
... There was also the idea of creating personas
... Now that mobile devices are omnipresent
... How do blind people us a mobile - is a question which is frequently being asked
... Developers could be better informed through the use of personas
... What do people think, are there other things

Gavin: Clarify that I was going to send across videos - also have some more general videos
... What is needed is more specific material - looking at specific contexts
... Tackling native apps and web apps independently

Kim: there are more videos available now than before
... Any further thoughts about the list
... Resource lists - are there other lists which we could make public or put effort into

Kathy: A list of good applications for mobile
... It would be good for people to have concrete examples to look at

Kim: It would be good to define apps along with why they show best practice
... Agree it is a little difficult to select apps - with regard to not playing favourites

Kathy: Does anyone have examples

Kim: Yes

Gavin: Yes

Kathy: We can create an accessible apps page
... I'll put it up

Kim: Any other thoughts on the resource lists

q

Alistair: Development environments and tools

Gavin: Agree
... Chrome for example contains a Mobile testing area
... Same with other platforms - Extends to testing mobile apps

Kim: On the resources we have testing tools, but should we include development environments

Gavin: Yes
... Developers select specific development environments

Kim: should that we a separate page, or do we add it to the resources page
... We shall add development environments to the same page

David: Agreed

Kim: Deliverables?
... Any last thoughts on the resource list?
... Other thoughts on the personas

David: By personas do you think disabilities of are you including situational disabilities

Kim: Personas of people with disabilities

Kathy: We can list the videos out there then decide
... We need to flesh out and finalise the list of current tasks
... Current deliverables

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

Kim: Other thoughts on deliverables

Kathleen: Google search W3C applies to mobile

<Kathleen> http://www.w3.org/TR/mwbp-wcag/wcag20-mwbp.html

Kathy: Some of the stuff we have listed is a little dated

Alistair: If the W3C process takes time - could we run a risk of producing material which is always off the leading edge

<Alan> sorry I'm late

Kim: Something to keep in mind

Kathy: Agree - it takes a while - so placing things on the wiki might allow a quicker speed to end user

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

Kim: Any thoughts on the list?
... We are going over the list to see if it makes sense

Alan: Number 1 seems to be the key - vendors who are reluctant about wcag 2 and web apps
... Vendors don't want to commit to mobile accessibility - due to lack of guidelines

David: When we say to developers make the mobile app accessibility - they say where are the standards which say how to do that or that we should do that

Alan: Mobile apps are not seen as needed to comply

Jeanne: If there were techniques in WCAG 2 for mobile would people pay more attention

Alan: There should be more saying that WCAG 2 is also applicable to a mobile

Kathleen: would it be useful to put together a list of current W3C resources in this area

<jeanne> http://www.w3.org/WAI/mobile/

Kim: Don't we already have that?

Alan: It would be better if it was easier to find

Kathy: Before next meeting can everyone take a look at the development techniques - wcag 2.0 and how it applies to mobile
... This would be a good area to look at - and what resources are already available on the w3c
... This can then be compared back to our work statement

<kw> akim, list participants

Kim: Last thoughts

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Thanks//
Succeeded: s/,/:/
Found Scribe: agarrison
Inferring ScribeNick: agarrison
Default Present: +1.978.760.aaaa, Kathy, Kim_Patch, Kathleen_Anderson, DavidTodd, WuWei, jeanne, agarrison, Michael_Cooper, gavinevens, Alan_Smith
Present: +1.978.760.aaaa Kathy Kim_Patch Kathleen_Anderson DavidTodd WuWei jeanne agarrison Michael_Cooper gavinevens Alan_Smith
Regrets: AS
Agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Jan/0000.html
Found Date: 10 Jan 2014
Guessing minutes URL: http://www.w3.org/2014/01/10-mobile-a11y-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.