Mobile Accessibility Task Force Teleconference -- 19 Mar 2015

<trackbot> Date: 19 March 2015

yes

<Kim> http://w3c.github.io/Mobile-A11y-TF-Note/

Fine with me.

I can

<scribe> scribe: jon_avila

<scribe> ACTION: Change ""mobile" screen size" to "various screen size" [recorded in http://www.w3.org/2015/03/19-mobile-a11y-minutes.html#action01]

<trackbot> Error finding 'Change'. You can review and register nicknames at <http://www.w3.org/WAI/GL/mobile-a11y-tf/track/users>.

<scribe> ACTION: Change point 1.1 ""mobile" screen size" to "various screen sizes" on Jeanne Spellman [recorded in http://www.w3.org/2015/03/19-mobile-a11y-minutes.html#action02]

<trackbot> Error finding 'Change'. You can review and register nicknames at <http://www.w3.org/WAI/GL/mobile-a11y-tf/track/users>.

ACTION Jeanne Spellman: change point 1.1 ""mobile" screen size" to "various screen sizes"

<trackbot> Created ACTION-25 - Spellman: change point 1.1 ""mobile" screen size" to "various screen sizes" [on Jeanne F Spellman - due 2015-03-26].

kp: next one small screen sizes 2.1

jan: This is basically mobile first which we discussed a reword a few weeks ago

kp: 3.3. and 3.2 were the changes from last time

Yes, we did change 2.1

kp: was EO comments on 2.1
... Skip this comment for 2.1 because it was already addressed

<Jan> Mobile first discussion and actions: http://www.w3.org/2015/02/26-mobile-a11y-minutes.html

kp: Add a bullet or note to 3.3 to make keyboard equivalents explicit

jan: agree with him. Had added that note in what was sent to the group.

<Jan> JR: Note I proposed: Note: While improving the accessibility of touchscreen gestures is important, keyboard accessibility is still required by some users and to meet WCAG 2.0 (see “3.1 Keyboard Control for Touchscreen Devices”).

kp: thoughts on Jan's proposed note versus other comment.

mike: need for note for sure -- may want to mention spcific success criteria. Perhaps mention SC 2.1.1

jan: Thought might be better to refer to other section might be better.

mike: Ok with referring back to section in this document.

kp: other thoughts? Hearing none - go with Jan's.

mike: should we drop "by some users"?

jan: the need is for some users and there is still the requirement

mike: misread the "and" -- so it's fine -- missed the and. Looks good.

kp: put note in -- do we need an action jeanne?

ACTION jeanne spellman: Implement Jan's note Note I proposed: Note: While improving the accessibility of touchscreen gestures is important, keyboard accessibility is still required by some users and to meet WCAG 2.0 (see “3.1 Keyboard Control for Touchscreen Devices”).

<trackbot> Created ACTION-26 - Spellman: implement jan's note note i proposed: note: while improving the accessibility of touchscreen gestures is important, keyboard accessibility is still required by some users and to meet wcag 2.0 (see “3.1 keyboard control for touchscreen devices”). [on Jeanne F Spellman - due 2015-03-26].

kp: 3.4. change a should to required for keyboard access.
... say that developer still need to provide keyboard ... options.

jan: ok with changing should to must -- also add an internal document reference.

<Jan> Therefore, even when device manipulation gestures are provided, developers must still provide touch and keyboard operable alternative control options (see “3.1 Keyboard Control for Touchscreen Devices”).

<Jan> Another issue with control via device manipulation gestures is that they might lack onscreen indicators that remind people how and when to use them. See “4.6 Provide instructions for custom touchscreen and device manipulation gestures”.

mike: prefer this wording from jan over commenters as it avoids the words conforming to WCAG

Jeanne: like need better than must
... withdraw comments on need and must.

mike: developers still need to provide.... combine jan's with the need instead of must.

+1 to mike

<Mike_Pluke> +1

<marcjohlic> +1 need to

jeanne: because we are note we should use "need to"

kp: Use Jan's wording with but change "must" to "need to"

<Kim> Therefore, even when device manipulation gestures are provided, developers still need to provide touch and keyboard operable alternative control options (see “3.1 Keyboard Control for Touchscreen Devices”).

<Kim> Another issue with control via device manipulation gestures is that they might lack onscreen indicators that remind people how and when to use them. See “4.6 Provide instructions for custom touchscreen and device manipulation gestures”.

mikeS: ok to keep in coformance.

<Kim> Therefore, even when device manipulation gestures are provided, in order to conform to WCAG, developers still need to provide touch and keyboard operable alternative control options (see “3.1 Keyboard Control for Touchscreen Devices”).

mikeP: In EU standard we created a set of software unique requirements that were different from the WCAG ones with updated language for software.

jan: we don't use conform other places

keep it out

kp: any objectives to both of the paragraphs from Jan.

ACTION Seanne Spellman to make Jan's changes above in 3.4.

<trackbot> Error finding 'Seanne'. You can review and register nicknames at <http://www.w3.org/WAI/GL/mobile-a11y-tf/track/users>.

ACTION Seanne Spellman: to make Jan's changes above in 3.4.

<trackbot> Error finding 'Seanne'. You can review and register nicknames at <http://www.w3.org/WAI/GL/mobile-a11y-tf/track/users>.

ACTION Jeanne Spellman: to make Jan's changes above in 3.4.

<trackbot> Created ACTION-27 - Spellman: to make jan's changes above in 3.4. [on Jeanne F Spellman - due 2015-03-26].

kp: Can switch tasks for second half and then switch to new stuff?
... Section 4.2 consistentcy in WCAG.
... commenter said that layout wasn't covered by SC 3.2.3 or 3.2.4

mikeP: Discussed this in taskforce. Had to introduce a set of software for 3.2.3. EU don't have equivalents to 3.2.3 and 3.2.4.
... can't apply as written to software with this particular meaning. It was thoroughly covered in WCAG to ICT.
... can't apply they are directly relevant. Meaning of consistency is different.

jeanne: is this a case to write new guidance rather than relying on WCAG.

<Kim> 4.2 Components that are repeated across multiple pages should be presented in a consistent layout. In responsive web design, where components are arranged based on device size and screen orientation, web pages within a particular view (set size and orientation) should be consistent in placement of repeated components and navigational components. Consistency between the different screen sizes...

<Kim> ...and screen orientations is not a requirement under WCAG 2.0.

jan: current document says SC most related to are -- perhaps we could move around this statement to make it more coherent.

<Jan> Consistency between the different screen sizes and screen orientations is not a requirement under WCAG 2.0. The WCAG 2.0 success criteria that are most related to the issue of consistency are:

mikeS: the word predictable may be better than the word consistent.

mikeP: would be good guidance for now because we aren't in the stage of conformance with this document. Predictable isn't testable -- but for this note it's fine.

<Mike_Pluke> +1

kp: is there anything needed beyond the move?

KP; any objections to the move?

kp: no objections

ACTION Jeanne Spellman: to make move put in Jan above for 4.2

<trackbot> Created ACTION-28 - Spellman: to make move put in jan above for 4.2 [on Jeanne F Spellman - due 2015-03-26].

jeanne: resent minutes from F2F meeting so we discussed the items that we talked about.
... having meeting to discuss WAI 2020 guidelines. One thing that came out of it -- support from people who were there - supporting doing extensions to WCAG. This would keep WCAG stable for the near term future.
... this would allow us to address evolving technologies and address areas for cognitive and low vision and concepts like the web of things and TV
... This isn't final so we aren't putting normative language in our document yet. But we should think about writing this document in a way that we could change this over to be normative document.
... The idea is that we could do small documents and in future maybe authorized to convert these into normative documents.

kp: Did detlev join? Some people got caught in daylight saving trap.
... See you next week. We will go with new SC discussion. Thanks

<Detlev> problems dialling in...

<Detlev> getting "this passcode is not valid" when using the code supplied in the invitation...

<Kim> Hi Detlev – meeting just ended – we're still in the daylight savings time mismatch

<Detlev> Arghhh!!!

- DRAFT -

Mobile Accessibility Task Force Teleconference

19 Mar 2015

Attendees

Contents

Summary of Action Items

Scribe.perl diagnostic output