<trackbot> Date: 13 December 2013

<Kathy> meeting: Mobile A11Y TF

<k> https://www.w3.org/WAI/GL/mobile-a11y-tf/track/users

<Kathy> scribe: Kathleen

<Kathy> https://www.w3.org/2000/09/dbwg/details?group=66524&public=1

Kathy: this will be our regular meeting time

review resources on wiki

<Kathy> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Mobile_Resources#Mobile_Accessibility_Dev_Techniques:_Applications

Kathy: any other resources?

<Jan_> JR: Has some resources

Kim: any other categories that we should add?

Kathy: any user testing scenerios or studies?

gavinevans: involved in three year study
... looking for feedback as to what we should be testing

<Detlev> Its Detlev not Gavin who said that...

gavinevans: we have a testing lab

Discussion on mobile accessibility challenges

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

detlev: should we check with the HTML5-WAI-ARIA task force?
... there may be some overlap

kathy: good next step is to have James and/or Loretta come to a meeting to tell us what they've been doing

<Detlev> This is the link to tests od ARIA Techniques, partly on mobile: http://3needs.org/en/testing/sr-aria.html

Kathy: our focus is native web apps as well as web sites

<agarrison_> Alistair - It would be useful to keep a track of mobile assistive technologies, and the capabilities and limitations

<Kathy> ACTION: Alistair Create list mobile assistive technologies, and the capabilities and limitations [recorded in http://www.w3.org/2013/12/13-mobile-a11y-minutes.html#action01]

<trackbot> Created ACTION-1 - Create list mobile assistive technologies, and the capabilities and limitations [on Alistair Garrison - due 2013-12-20].

Kim: what are the main mobile accessibility challenges?

agarrison_: a huge challenge - including huge libraries (JQuery) - the library is massive and takes a huge amount of bandwidth

<Jan_> JR: Key challenge: Custom widgets are a challenge on every platform (and as they become more complex WAI-ARIA becomes harder to use effectively).

detlev: different interaction paradigm
... swiping vs keyboard centric

detlve: touch vs keyboard input

Jan_: there are keyboard APIs built into iOS and Android
... the differences between touch and mouse result in accessibility problems

Kim: anyone have resources to go under missing information?

Kathy: what is frustrating companies trying to build mobile apps or web sites?

gavinevans: developing for different devices, different considerations, differences in touch guidelines

kathy: MIT did a study on different touch sizes

DavidTodd: work at IBM with dojo keyboard

Detlev: from a user perspective difficult to find out how to make your device more accessible

Next Steps

Kathy: there is a call next week, no call on the 27th
... need a good method of how to attack our next steps

<Kathy> trackbot, end meeting

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)

Found Scribe: Kathleen
Inferring ScribeNick: Kathleen
Default Present: Kathy_Wahlbin, Kathleen_Anderson, +1.720.663.aaaa, Detlev, alistair, +1.617.435.aabb, DavidTodd, Jan, Kim, wuwei, +44.179.281.aacc, gavinevens
Present: Kathy_Wahlbin Kathleen_Anderson +1.720.663.aaaa Detlev alistair +1.617.435.aabb DavidTodd Jan Kim wuwei +44.179.281.aacc gavinevens
Found Date: 13 Dec 2013
Guessing minutes URL: http://www.w3.org/2013/12/13-mobile-a11y-minutes.html
People with action items: alistair