<trackbot> Date: 20 November 2014

<Kim> http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Nov/0010.html

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

<scribe> scribe: jon_avila

Q&A Note assignments / status

kp: Are there any questions about the note and writing it in sections.

alan: asked about purpose

kp: Purpose is so instead of handing WCAG one piece -- we hand them our thinking in entirety of what is missing - this is the forest rather than an tree. A better way to start.
... It's a little more causal and explanatory. Techniques would come out of this. This will allow us to move forward faster.

jan: Question about perspective. You say it will spot gaps. The audience isn't WG members. Instead this document is for mobile developers who want guidance and who don't see work mobile in title
... This note says WCAG applies and the principles apply and here is the explanation and that will lead WCAG WG to then build techniques into their document.

kp: This would be a stand alone document that developers could use before its carried over into WCAG.

jeanne: We actually do write techniques and associate them with this document and that will avoid some of the structural problems with fitting them into WCAG
... Those structures have been constraining us. E.g. This issue of sufficient or advisory. I don't want all of our techniques to be labeled advisory which people see as optional just because there is not some place to plug them into WCAG.
... WCAG WG is making their own progress in updating their documents. Later our stuff can be rolled in WCAG documents.

kp: wanted to point out resources on the WCAG note page under current work at top of main wiki page.
... Discussion notes are ones we had before we started. These map to survey and the survey number and how to link to the discussion notes.
... If you are writing one of these sections and you want to go back and look at the discussions.
... last link is survey we had on the mobile technique and gap analysis

jeanne: wrote introduction and added routine W3C things like abstract and status.
... used WCAG ICT document as guideline
... would like to position this document o mobile app even though WCAG only directly applies to web. the WCAG ICT doc dealt with non-web things so we could use similar language
... key things is 3rd paragraph. Also discussed mobile web best practice documents.
... added UAAG applies to mobile also. In particular the UAAG mobile examples document. Will provide link.
... This document talks about how these are informative not normative.
... happy to have comments/edit, etc.

kp: put comment at bottom of section with your name and date if you want to comment

+1

jan: Worked on perceivable section. Talked about small screen size. e.g. adapting link text, etc. Might have 3 to 5 discussion areas under the principles. We don't want to dilute what we are trying to say.
... Add touch target size and keyboard control on mobile devices under operability.
... Trying to call out WCAG SC when relevant in each place. Also added changing screen orientation will go under perceivable.

alan: looks good.

jan: UAAG shows up a lot -- perhaps they could be combined.

kp: Should we have references to WCAG and UAAG at teh bottom of each section?

jan: Do like the idea of grounding what we are saying in these discussions. Danger is that some that don't have SC will stand out more.

jeanne: if we put reference directly in without a separate section it doesn't draw so much attend to places where we don't have a reference.

kp: make references linked.
... Is there a way to open links in different window?
... Like use of @@

jeanne: Add idea of appendix for WCAG sc that apply.

kp: Is at bottom
... right now it points to the document that we did before for techniques that apply without changes. Some changes may apply to make them more applicable.

jeanne: allows us to show our work without being tied to WCAG publishing deadlines
... like to be able to adapt the WCAG work to create the document.

jan: concern is that when you click that link you get this big list. Maybe flip question about what is not relevant.
... some techniques numbers aren't in use.

jeanne: agreed -- we want to think about appendix and success criteria and applicable links to techniques to avoid numbering issues.

kp: mental map would be good with coding

jan: also leery of saying something doesn't apply.
... e.g. skip over links is not listed.

kp: any other questions?
... going forward with small changes. Next time there will be more to talk about. We will go down both tracks.
... end meeting early. Use time to work on doc. Remember to use edit link right by your section to not tie up whole document for editing.

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
Default Present: Alan_Smith, Kim_Patch, Jeanne, +1.703.637.aaaa, jon_avila, Jan
Present: Alan_Smith Kim_Patch Jeanne +1.703.637.aaaa jon_avila Jan
Regrets: Kathleen_Wahlbin Tom_Babinszki Gavin_Evans
Found Date: 20 Nov 2014
Guessing minutes URL: http://www.w3.org/2014/11/20-mobile-a11y-minutes.html
People with action items: 

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