See also: IRC log
<trackbot> Date: 31 January 2014
<scribe> scribenick: jeanne
<KimPatch> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Draft_WCAG_Techniques
KP: Today we are going to walk through the process of evaluating the techniques
This is #4 in "Work in PRogress" section
scribe: In the survey, you signed
up for one of these sections
... there are instructions and samples in the "General
Techniques" section
... what you will do is click the Technique list you signed up
for
... you will see the Instructions, and under that is the list
of all the Techniques
... in the General section, Jeanne did the first 3 as a
sample
KP: If Not Applicable, you will
edit the list, and paste the code in the box i
...
JR: When we are looking at the
Techniques, are we seeing these as applying to sites with
mobile optimized page.
... When we are assessing them, what level of mobile
optimization should we be thinking?
KP: We want all levels.
... change that to a "requires changes" -- [gives instructions
for requires changes]
Alan: It's important to consider all kinds of mobile devices
<Jan> Instructions ok
Kathleen: I don't know what you mean by the [[ ]] and don't include the colon
JS: we are trying to create a
list where we can all see what needs to be worked on.
... and then create a new page for a Technique that needs more
work
JR: I think we will have very few "not applicable", a lot of "applicable as is" and then a group of "requires changes"
KP: I think if it applies broadly, we should mark it as requires changes and then put it in the comments.
JR: I think we have to be very
careful about marking existing WCAG techniques as not
APplicable.
... for example, saying keyboard doesn't apply to mobile is not
correct.
... be careful about marking things as not applicable, because
there will be very very few that actually are not
applicable.
... beware of stereotypes of mobile
Alan: I think when we look at different devices and screensides we have to be very careful of saying "not applicable"
JS: Should we remove the "not applicable" and only work with "as is" and "changes"
ALan: I think we can keep it, but use it very rarely.
JS: I worry that people not in this meeting may not understand the context we have been discussing
ALan: Put a note in the instructions
KP: Next time people will have more experience and things will come up.
JS: There will be a meeting on
5th to coordinate with other task forces who are working on the
Techniques
... that Kathy and Kim will be attending
<Alan_> Alan will work on his items over the weekend so you have supporting documentation for your Wednesday meeting with the other workgroups.
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: jeanne Inferring Scribes: jeanne Default Present: Kim_Patch, Kathleen, Alan_Smith, Jan, Jeanne, wuwei Present: Kim_Patch Kathleen Alan_Smith Jan Jeanne wuwei Regrets: gavin kathy david_todd Agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Jan/0009.html Found Date: 31 Jan 2014 Guessing minutes URL: http://www.w3.org/2014/01/31-mobile-a11y-minutes.html People with action items:[End of scribe.perl diagnostic output]