See also: IRC log
<trackbot> Date: 08 January 2015
<jeanne> +1 at CSUN
<Jan> +1 to that day
<Kim> Kathy: Tuesday, March 3 possible joint meeting with WCAG at CSUN
<Kim> I'll put out a survey with that question. We are also looking at people attending remotely..
<Kim> Kathy: make sure that we align with WCAG so we have consistency within documentation
<scribe> Scribe: Kathy
http://www.w3.org/WAI/GL/mobile-a11y-tf/WD-Mobile-A11y-NOTE-20141219/AppendixA.html
Kim - the first link is the work we did previously
Kim - the second URL is the appendix A that lists the WCAG 2.0 Techniques that Apply to Mobile
Jeanne - this was a manual process of putting this together
Jeanne - we envision on having collapsible text
http://www.w3.org/WAI/WCAG20/quickref/
<Kim> Kathy: so the idea is to have a list that applies to mobile.
<Kim> Kathy: the doesn't seem to be any exceptions that have come across so far – the general techniques apply to both native and web, the HTML, scripting and aria all apply to mobile web and don't really apply to the native apps because they are very specific techniques to HTML
<Kim> Kathy: and so with that we don't necessarily need to call out native and web specifically, we could do a general statement, and if there are exceptions we could list those out
<Kim> Kathy: also listing out failures just they are in WCAG – looking at this so we can align so it's closer to the structure of WCAG
<Kim> Kathy: ideas about this? How can we present the so it's clearer?
<Kim> Jan: looking at what's actionable, when it doesn't say native apps…
<Kim> Kathy: I went through n detail this week and I didn't see any that wouldn't apply to native apps
<Kim> Jan: depends on what you've built your HTML with
<Kim> Kathy: that would be a hybrid app, so we could call that out specifically. Instead of applies to native and web it applies to programming in iOS Android framework versus HTML CSS aria are for HTML development
<Kim> Kathy: you are right Jan it's more complicated because we have hybrid apps
<Kim> Jan: filter native, hybrid
<Kim> Kathy: right now we don't, so this appendix is designed to give someone a snapshot of what is applicable to mobile
<Kim> Jan: great if someone wants to see the whole thing, but maybe at the top quick list, what doesn't apply. That's what's interesting
<Kim> Jeanne: we should automate this
<Kim> Jeanne: room is available, need to firm up quickly
<Kim> Andrew: WCAG hasn't come to clear conclusion about whether we will meet or not. Either its shared or mobile.
<Kim> Andrew: Tuesdays the day we would be meeting.
<Kim> Jeanne: so two rooms and we can be flexible
<Kim> Kathy: still need to poll the group to see who's going to be there
<Kim> Kathy: we can sort out the details but it would be good to schedule something and we will work out what to do as far as cooperation with WCAG and meeting time. If people can plan if you are going to CSUN to be there on Tuesday.
<Kim> Jeanne: room is tentative
<Kim> Kathy: we will plan on it and work something out
<Kim> Kathy: any other thoughts on appendix a. I'm working toward making the changes to the structure of it so now's the time to voice any concerns or suggestions
<Kim> Kathy: Andrew, is this something the WCAG working group would like to look at after we have put together – this is separate from the note right now
<Kim> Andrew: Yes
<Kim> Kathy: questions, when will sections be ready? Over the next few weeks we will be reviewing sections and getting those finalized
<Kim> Jan: I feel like I've wrapped up my sections and I took my name off them so anyone can go in and edit as well. If there are other sections you'd like me to work on shoot them over
<Kim> Kathy: we will review Jan's sections next week, and I should have mine done as well
<jon_avila> I put in my bit on contrast.
<Kim> Kathy: Marc, if there's any sections that you feel you'd like to contribute on or any comments that you have on this document we love to get your input
<Kim> Jon: email on contrast
<Kim> Kathy: did you add in the stuff from Greg
<Kim> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Note:_WCAG_2.0_and_Mobile
<Kim> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Main_Page
<Kim> Kathy: what I will do for next week is detail the sections, put out a survey so we can review the sections. If you have time please work on writing for the assigned sections. If you have time and can work on other sections or have comments feel free to put those into the document.
<Kim> Kathy: we can use the time left today to work on the note, and then next time will be going over those sections that are marked done
<Kim> Kathy: any other questions about what we are trying to accomplish or time frames
<Kim> Kathy: please take time to read through the note, send your comments either in an email to the group or put them in the document. We would like to have conversations going off-line as well so we can continue moving this forward.
<Kim> Andrew: to get Jan's attention because he did the keyboard section – I put a note, talking to Randy Marston about keyboard access later today.
<Kim> Jan: we can express the keyboard access is very important
<Kim> Andrew: I will also suggest that if he knows someone from Apple who can be involved with the task force that would be useful
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: Kathy Inferring ScribeNick: Kathy Default Present: Kathy_Wahlbin, Kim_Patch, Jeanne, TomB, Jan, Marc_Johlic, Jon_avila, AWK, Michael_Cooper Present: Kathy_Wahlbin Kim_Patch Jeanne TomB Jan Marc_Johlic Jon_avila AWK Michael_Cooper Agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2015Jan/0001.html Found Date: 08 Jan 2015 Guessing minutes URL: http://www.w3.org/2015/01/08-mobile-a11y-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]