<Kim> clear agenda

<jon_avila> scribe: jon_avila

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

marc: question on m22 - think we said that would go away now related to 2.5.3. Should I put strike through it on wiki

Kim: use status column to say it has been removed
... realized that it was not needed
... thnink it was 2.5.3 and 2.5.4 touch target size covers the whole thing.

marc: thought I had signed up for writing a failure technique. Not sure which one -- will go through minutes to find out which one I volunteered for

kim: some don't yet have github respotitory but are in wiki. We can then work on Wiki and move to github.
... Wiki links are there now.

jeanne: didn't have good record of who signed up for what. So we want to have chart and then action items to manage

marc: think it was FM002

jeanne: still working out permissions to wiki.
... Jon write failure for 2.5.3 but found action item that Jan was going to revise 2.5.3 and he can't do it.

Kim: Marc to take 2.5.1
... any volunteers for 03, 04,or 05?

marc: will take 2,4, and 5.

chris: will take FM003

kim: Fm001 is done

jeanne: 28,39,30 and are not assigned at all

kim: will anyone take one of those?

Jon Avila to 28

Jon to take M28

<jeanne> https://w3c.github.io/Mobile-A11y-Extension/#techniques-and-failures-for-success-criterion-2.5.4

<jeanne> M030 Multiple Elements: When multiple elements perform the same action or go to the same destination (e.g. link icon with link text), these should be contained within the same actionable element. This increases the touch target size for all users and benefits people with dexterity impairments. It also reduces the number of redundant focus targets, which benefits people using screen readers

<jeanne> and keyboard/switch control.

https://www.w3.org/WAI/GL/WCAG20-TECHS/H2.html

<jeanne> ACTION: Marc to write FM002 [recorded in http://www.w3.org/2016/02/18-mobile-a11y-minutes.html#action01]

<trackbot> Created ACTION-34 - Write fm002 [on Marc Johlic - due 2016-02-25].

<jeanne> ACTION: Chris to write FM003 [recorded in http://www.w3.org/2016/02/18-mobile-a11y-minutes.html#action02]

<trackbot> Created ACTION-35 - Write fm003 [on Chris McMeeking - due 2016-02-25].

<jeanne> ACTION: Marc to write FM004 [recorded in http://www.w3.org/2016/02/18-mobile-a11y-minutes.html#action03]

<trackbot> Created ACTION-36 - Write fm004 [on Marc Johlic - due 2016-02-25].

<jeanne> ACTION: Marc to write FM005 [recorded in http://www.w3.org/2016/02/18-mobile-a11y-minutes.html#action04]

<trackbot> Created ACTION-37 - Write fm005 [on Marc Johlic - due 2016-02-25].

<jeanne> ACTION: Jon to write M028 [recorded in http://www.w3.org/2016/02/18-mobile-a11y-minutes.html#action05]

<trackbot> Created ACTION-38 - Write m028 [on Jonathan Avila - due 2016-02-25].

kim: can be problematic for speech world as you have to figure out how things work first time - so there are pluses and minuses
... is anyone will to take on first draft M30?
... that will remain unassigned for the moment
... Jeanne, could you go right to the understanding stuff

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

jeanne: put in wrong link

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

jeanne: trying to update list of what you are working on

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

<chriscm> Can everyone double check their assignments on the wiki? I just saved the set of changes regarding FM001 - FM005 and M28.

detlev: am listed for all the things I am working on in wiiki. M29 could be mine as well

Finish 2.5.3 - https://w3c.github.io/Mobile-A11y-Extension/#touch-and-pointer

<jeanne> https://w3c.github.io/Mobile-A11y-Extension/#touch-and-pointer

<jeanne> 2.5.3 Single Taps and Long Presses Revocable: Interface elements that require a single tap or a long press as input will only trigger the corresponding event when the finger is lifted inside that element. (Level A)

jeanne: fixed numbers. Text of 2.5.3 posted in
... found thread of email from Patrick. Found action item from Jan that he was going to write it but he cann't now. Does anyone remember what we were going to do with 2.5.3?

<jeanne> Patricks' email thread https://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2015Jul/0038.html

jeanne: should talk about this next week if no one remembers?

detlev: need to review emails and someone shoudl dig through those and draft something -- person may need to get in touch with patrick. Should have one person take up task.

chris: will take up

<jeanne> ACTION: Chris to research changes to 2.5.3 and write a new proposal. [recorded in http://www.w3.org/2016/02/18-mobile-a11y-minutes.html#action06]

<trackbot> Created ACTION-39 - Research changes to 2.5.3 and write a new proposal. [on Chris McMeeking - due 2016-02-25].

chris: is this a discussion and where should I put content based on the action item?

detlev: m29 closely relates

<jeanne> ACTION: Chis to draft M029 technique [recorded in http://www.w3.org/2016/02/18-mobile-a11y-minutes.html#action07]

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

<jeanne> ACTION: Chris to write M029 technique [recorded in http://www.w3.org/2016/02/18-mobile-a11y-minutes.html#action08]

<trackbot> Created ACTION-40 - Write m029 technique [on Chris McMeeking - due 2016-02-25].

<Kim> https://w3c.github.io/Mobile-A11y-Extension/#techniques-and-failures-for-success-criterion-2.5.2

<jeanne> Swipe gestures are useful for displaying new content. Giving focus to new content via a swipe gesture also needs a gesture or method to move focus back to the main content — either by swiping to return or by informing the user of the method needed to return. These methods must work with assistive technology. This success criterion is the touch equivalent of WCAG 2.1.2 No keyboard trap.

<jeanne> Example 1: Infinite scroll of content, where there is additional content in the footer, but the user with assistive technology (e.g. screenreader) cannot move focus to the footer and therefore cannot read the footer content and may not even know that the footer content exists. .

<jeanne> Example 2: An infinite carousel advances with a swipe gesture. The instructions indicate that a touch outside the carousel will exit the carousel. The user can touch outside the carousel with assistive technology (e.g. screenreader) turned on.

<Detlev> scribe: Detlev

Jeanne: suggestions for wording?

Chris: Dynamic content

<jeanne> Swipe gestures are useful for displaying dynamic content. Giving focus to dynamic content via a swipe gesture also needs a gesture or method to move focus back to the main content — either by swiping to return or by informing the user of the method needed to return. These methods must work with assistive technology. This success criterion is the touch equivalent of WCAG 2.1.2 No keyboard

<jeanne> trap.

<jeanne> Swipe gestures are useful for displaying dynamic content. Giving focus to dynamic content via a swipe gesture also needs a gesture or method to move focus back to the prior content — either by swiping to return or by informing the user of the method needed to return. These methods must work with assistive technology. This success criterion is the touch equivalent of WCAG 2.1.2 No keyboard

<jeanne> trap.

Jeanne: prior conten?

Detlev: question if trap is correct term

<jeanne> Swipe gestures are useful for displaying dynamic content. Giving focus to dynamic content via a swipe gesture also needs a gesture or method to move focus back to prior content — either by swiping to return or by informing the user of the method needed to return. These methods must work with assistive technology. This success criterion is similar to WCAG 2.1.2 No keyboard trap.

Jeanne: it's equivalent to trap - you can't get to content (say, foter)

<chriscm> +1

<Kim> +1 intent

<jeanne> +1

+1

<Jatin> +1

RESOLUTION: accept Intent for 2.5.2

<jeanne> Content that is after or outside of infinite scrolling content, and content that is off the visible screen can be accessed by screenreader users.

<Kim> Content that is after or outside of infinite scrolling content, or off the visible screen, can be accessed by screenreader users.

FM003 Failure of 2.5.1 Failure of 2.5.1 Component can be opened but cannot be closed with touch when a system screen reader is running. (Level A) wold apply to 2.5.2 as well

<chriscm> +1

<jeanne> +1

Jeanne: any other issues?

<Kim> +1

+1

RESOLUTION: accept Understanding for 2.5.2

Jeanne: 2.5.3 will change based on Chris' input
... has started new guideline 2.6 ans 2.7 (speech input)

Kim: give input on speech input if you can

<jeanne> prsent- Jon

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: jon_avila
Inferring ScribeNick: jon_avila
Found Scribe: Detlev
Inferring ScribeNick: Detlev
Scribes: jon_avila, Detlev
ScribeNicks: jon_avila, Detlev
Default Present: Kim, Alistair, Kathy, David, Detlev, Jan, Marc, Jon, Jeanne, JF, Jatin, Chrism, jon_avila, MacDOnald, Jatim, alan, marcjohlic
Present: Chrism Detlev Jatin Jeanne Kim Marc jeanne jon_avila marcjohlic
Regrets: Alastair Alan Kathy Jan
Found Date: 18 Feb 2016
Guessing minutes URL: http://www.w3.org/2016/02/18-mobile-a11y-minutes.html
People with action items: chis chris jon marc

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