<trackbot> Date: 13 November 2014

<Kathy> meeting: Mobile A11Y TF

<scribe> scribe: jon_avila

<Kim> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Note:_WCAG_2.0_and_Mobile

kw: Some open questions regarding how we will structure mobile techniques. Question into where this fits or doesn't fit due to gaps. e.g. touch
... don't have answers and clear direction from where these will fit within WCAG. Discussion on Monday on what we can do now to get information out to developers.
... Can say how WCAG is applicable to mobile dev so they can thing about the things that are needed for mobile over all.
... We are going to create a note - interim deliverable - where we have info that can get out faster while we are wokring.
... This will allow us to get something published and then we can work on published techniques.
... Similar to issues with cognitive TF and overall direction
... Jan had taken a first pass on outline with Jeanne and Kathy contributing.
... Gap analysis has been done and we may find more. we will discuss how we present that information.
... 3 parts, note, gap analysis, and techniques themselves. For now we will concentrate on this note. The note would have 4 sections.
... First one is how it applies, touch on some techniques,
... Second section is on mobile specific issues.
... Third section is note on UAAG.
... Fourth section is a case study on sample mobile website/app that is designed to be accessible
... want to get your thoughts on structure and content and how this will be used. Is this going to get the information developers, managers, etc? Is there something that is missing?

kp: wanted to mention what we've talked about the what and how it fits in WCAG. Good solution to how it fits issues.
... a lot of new m techniques are in here

detlev: some mobile principles such as touch also apply to mouse operation. Some things in our list have been left out from WCAG. e.g. make sure things look actionable.
... Somethings like this apply to desktop as well as mobile. Consider why WCAG group had not included it for a reason - e.g. because it was a usability.

kw: One reason why we are stepping away from techniques so we can get more clear direction from WCAG WG.
... Discussion has shown that we need to discuss whether these are the right techniques. We will need to get that list clearly defined with details on whether this is something we should write for and whether it fits in mobile.
... Perhaps some of these are not specific to mobile but the interaction mode, touch, screen size, etc.
... Valid concerns and things that we have reaslized of the last month. So that is why we are going to focus on mobile accessibility in general.

kp: We have been working on the trees but now we will focus on the forest. We will take this as a template for techniques to come.

kw: Other thoughts on the note?

detlev: no WCAG guidelines for items appearing actionable. We could think about how we could work it into existing techniques. To move forward we need a place where these discussions take place.
... This document might not be the place but we need a place to discuss.

got kicked off call.

My phone is down can someone else scribe until I can get back in?

<Kathy> yes

<Kathy> kp: many of these we have talked about, this would eventually go into a github document

<Kathy> kp: this would be document that would inform "what to do"

<Kathy> kp: we would have people write paragraphs for the different items

<Kathy> jan: the wiki page is where we will start the writing

<Kathy> kw: is there sections missing or content to be added

<Kathy> detlev: people may wonder if this is an explanation of the mobile best practices

<Kathy> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Note:_WCAG_2.0_and_Mobile#Discussion_of_Mobile-Specific_Issues

<Kathy> jan: doesn't think that there would be confusion

<Kathy> detlev: maybe have it in the introduction

<Kathy> detlev: if I am designer I would want a subset of these

I am back

<Kathy> detlev: may want to talk about responsive images

ok

kw: Do you think we should have a section on responsive images?

detlev: We need to see what we are trying to achieve. Take into the whole development context?
... need to get overview so we can see how these overall development activities fit in.

kw: You detlev talked about how we might break it up by roles such as designer. Do you think we should break it up that way?

detlev: Map WCAG SC to roles is helpful -- there is a document that does that.

jan: at this point that is a layer complexity that is too much.

kp: It is all very connected so we want developers to think about it all.

mike: like outline and structure

<Shebanek> +1 for adding a page for each numbered item

<Kim> Making assignments – Kathy adding names to wiki

<Kim> Jan: workflow here, if everything is off in the sub pages it's going to be really hard to read this thing for flow.

<Kim> Kathy: draft sections, can combine later

<Kim> Jan: make sure not to edit the document as a whole, just under one heading

<Kim> Detlev: I like the concise overview

<Kim> Kathy: will create everything is a separate section – make sure to use the edit buttons

<Kim> Kathy: contents block gives an overview

<Kim> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/index.php?title=Click_language&action=edit&redlink=1

<Kim> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Subset_of_WCAG_2.0_Techniques_Applicable_to_Mobile_without_Changes_that_need_language_update

<Shebanek> +1 for activate!

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)

Found Scribe: jon_avila
Inferring ScribeNick: jon_avila

WARNING: No "Topic:" lines found.

Default Present: Kim_Patch, Kathy_Wahlbin, AWK, Detlev, jon_avila, Jan, +1.408.425.aaaa, Brent, Jeanne, +1.703.862.aacc
Present: Kim_Patch Kathy_Wahlbin AWK Detlev jon_avila Jan +1.408.425.aaaa Brent Jeanne +1.703.862.aacc
Found Date: 13 Nov 2014
Guessing minutes URL: http://www.w3.org/2014/11/13-mobile-a11y-minutes.html
People with action items: 

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report