<trackbot> Date: 23 April 2015

<scribe> scribe: David

Mobile checker – Jeanne

Mobile a11y in alpha

Guillaume

Not an a11y checker yet...

<guillaume> https://validator.w3.org/mobile-alpha/

Checker checks if a site is mobile ready

<guillaume> https://validator.w3.org/mobile-alpha/

<guillaume> https://github.com/w3c/Mobile-Checker

The Mobile Checker was built to provide all of us web developers with a new and helpful experience of mobile Web developement. We built the base. Now join us, and make it grant your wishes. We hope you will make it awesome.

want to include a11y mobile tests

https://www.google.com/webmasters/tools/mobile-friendly/

David: What is the difference btween this and Google

The goal is the same, but we want to include a11y tests

We are simulating the mobile web app on Chrome, and we can extend to other browsers

Alan: wondering if the tests I sent were useful

Guillaume: I haven't added it yet but find it interesting

<guillaume> https://github.com/w3c/Mobile-Checker/tree/master/lib/checks

Henny: What tests do you have that we can look at?

Guillaume: The tests are in the link above

<guillaume> https://github.com/w3c/Mobile-Checker/blob/master/CONTRIBUTING.md

Guillaume: I want to make it easier to use, have to work with it...

David: All the regular checks found in AMP, Tenon, AMP, etc...

Jan: What about issues rasied by the checks themselves. ie. Sometimes, having all images on same page... making sure existing checks are not counter to a11y

Guillaume: we are not going to do a right/wrong model, but rather notify the user of concerns certain approaches raise...

Jean: Thanks for coming Guillaume and we'll be talking more about it...

Guillaume: open an issue, pull requests etc... appreciate collaboration

Comments on 3.1 keyboard control https://github.com/w3c/Mobile-A11y-TF-Note/issues/4

to wonder about "Mobile Touchscreen devices and apps should be operable using a physical keyboard or alternative external input device and provide or support alternative on-screen keyboard layouts."

Mobile Touchscreen devices and apps should be operable using a physical keyboard which can be emulated by alternative external input device and provide or support alternative on-screen keyboard layouts.

David: I added to the github

<Kim> "Mobile Touchscreen devices and apps should be operable using a physical keyboard which can also be an emulated by alternative external input device and provide or support alternative on-screen keyboard layouts."

<Kim> "Mobile Touchscreen devices and apps should be operable using a physical keyboard that can also be emulated by alternative external input devices and that can provide or support alternative on-screen keyboard layouts."

<Jan> However, keyboard accessibility remains as important as ever. WCAG 2.0 requires keyboard control at Level A and keyboard control is supported by most major mobile operating systems via keyboard interfaces, which allow mobile devices to be operated using external physical keyboards (e.g. keyboards connected via Bluetooth, USB On-The-Go) or alternative on-screen keyboards (e.g. scanning...

<Jan> ...on-screen keyboards).

Jan: let's not put in this level... let's put it in the techniques

David: agree, I think he was wanting us to call out specifically, to ensure tabindex="0" to non actionable elements

<jeanne> Is this Mike's original text? https://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2015Mar/0021.html

kim: table it for later so Jan can read

Best Practices assignments

<Kim> http://www.w3.org/WAI/UA/work/wiki/Main_Page

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

<jeanne> s/ http://www.w3.org/WAI/UA/work/wiki/Main_Page//

kim: Starting on Perceivable techniques

<jeanne> http://w3c.github.io/Mobile-A11y-TF-Note/#mobile-accessibility-considerations-primarily-related-to-principle-1-perceivable

<jeanne> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Technique_Development_Assignments#Mobile

Jan: Non linear screen layouts... does this spawn any new techniques

David: Tables may go off the side... techniques to fix that?

Jan: you've chosen to make things complicated, and convoluted is there antechnique... and if you bring a lot of other things from the sides but not from the top down
... should we have sufficient techniques that address that?

David: There is nothing in WCAG techniqies to address that

Jan: Managing accessibility for non linear screen layouts

Jeanne: Microsoft is going to go beyond the dom to address these types of issues

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/skte/site/
Succeeded: s/take/raise/
Succeeded: s/0"/0" to non actionable elements/
Succeeded: s/csn/can/
WARNING: Bad s/// command: s/ http://www.w3.org/WAI/UA/work/wiki/Main_Page//
No ScribeNick specified.  Guessing ScribeNick: David_
Found Scribe: David
Default Present: Kim_Patch, Jeanne, Alan_Smith, Guillaume, David_MacDonald, Henny, Jan, Kenny, Mike_Pluke, AWK
Present: Kim_Patch Jeanne Alan_Smith Guillaume David_MacDonald Henny Jan Kenny Mike_Pluke AWK
Regrets: marc_Johlic mike_shebanek
Agenda: https://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2015Apr/0017.html
Found Date: 23 Apr 2015
Guessing minutes URL: http://www.w3.org/2015/04/23-mobile-a11y-minutes.html
People with action items: 

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