13:40:03 <RRSAgent> RRSAgent has joined #mobile-a11y
13:40:03 <RRSAgent> logging to http://www.w3.org/2014/06/06-mobile-a11y-irc
13:40:05 <trackbot> RRSAgent, make logs public
13:40:05 <Zakim> Zakim has joined #mobile-a11y
13:40:07 <trackbot> Zakim, this will be WAI_MATF
13:40:07 <Zakim> ok, trackbot; I see WAI_MATF()10:00AM scheduled to start in 20 minutes
13:40:08 <trackbot> Meeting: Mobile Accessibility Task Force Teleconference
13:40:08 <trackbot> Date: 06 June 2014
13:40:17 <jeanne> jeanne has joined #mobile-a11y
13:40:22 <kw> rrsagent, make log world
13:43:38 <wuwei> wuwei has joined #mobile-a11y
13:44:05 <kw> chair: Kathy
13:54:26 <Zakim> WAI_MATF()10:00AM has now started
13:54:33 <Zakim> + +1.617.577.aaaa
13:56:08 <Kathy> zakim, aaaa is me
13:56:08 <Zakim> +Kathy; got it
13:56:15 <Jan_> Jan_ has joined #mobile-a11y
13:59:43 <Zakim> +Kim_Patch
13:59:59 <Kathy> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/New_WCAG_2.0_Techniques
14:02:08 <Zakim> +Jeanne
14:02:14 <Zakim> +EricP
14:02:28 <wuwei> zakim, EricP is wuwei
14:02:28 <Zakim> +wuwei; got it
14:02:39 <Zakim> +[IPcaller]
14:03:03 <Jan_> zakim, [IPcaller] is really Jan
14:03:03 <Zakim> +Jan; got it
14:03:53 <Jan_> zakim, who's here?
14:03:53 <Zakim> On the phone I see Kathy, Kim_Patch, Jeanne, wuwei, Jan
14:03:55 <Zakim> On IRC I see Jan_, wuwei, jeanne, Zakim, RRSAgent, KimPatch, Kathy, MichaelC, trackbot
14:04:29 <jon_avila> jon_avila has joined #mobile-a11y
14:04:48 <Zakim> +[IPcaller]
14:04:53 <jon_avila> zakim, I am IPcaller
14:04:53 <Zakim> ok, jon_avila, I now associate you with [IPcaller]
14:05:58 <Kathy> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/New_WCAG_2.0_Techniques
14:06:55 <KimPatch> http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Jun/0000.html
14:07:39 <jon_avila> kw: follow-up discussion on item 13 design clickable objects to look clickable
14:08:27 <jon_avila> jeanne: Last week we talked about button appearance is inconsistent across platforms.  Talked about testability.
14:09:06 <jon_avila> jeanne: meet w/ Kathleen, and Alan and talk about different platforms and small group decided that it was an accessibility issue for people with cognitive impairments
14:09:14 <jeanne> http://www.w3.org/WAI/UA/IMPLEMENTING-UAAG20/#sc_131
14:09:44 <jon_avila> jeanne: couldn't find specific WCAG SC but there is a UAAG 1.3.1 and for 1.3.2 requires class of objects with custom appearance and different ways these can be highlighted.
14:10:44 <jon_avila> jeanne: small group recommend leave as BP for now because there is no WCAG SC but reference UAAG 1.3.1 and 1.3.2.  Advise to tell author to code them so they have semantics as buttons that way the platform can change how they are rendered to appear as buttons.
14:11:02 <jon_avila> kw: Are you recommending a new name for this?
14:11:31 <jon_avila> kw: suggested new name might help it to fall under WCAG 1.3.1 Info and Relationships
14:12:14 <jon_avila> kw: any comments or disagreement? None heard.  Thanks for organizing meeting
14:13:07 <Zakim> +Alan_Smith
14:13:44 <Kathy> https://www.w3.org/2002/09/wbs/66524/20140512_survey/results#xq5
14:13:58 <jon_avila> RESOLUTION: Modify item #13 from survey text and name and reference UAAG and be a ST under 1.3.1
14:14:01 <jeanne> New title: Code active elements semantically so they can be customized by the user agent
14:14:19 <jon_avila> TOPICI: #4 from Survey
14:15:08 <jon_avila> TOPIC: 4. Specify input type for numerical or character data
14:15:30 <AlanSmith> AlanSmith has joined #mobile-a11y
14:15:31 <jon_avila> kw: wanted to ask about what it was saying - are we talking about HTML5 input type?
14:15:38 <wwu> wwu has joined #mobile-a11y
14:16:26 <jon_avila> jan: Thinks it is related to HTML5 semantic input text.  Has concern that user agent needs to be smart about when keystrokes are ignored, e.g. letters don't enter when it expects number.
14:16:33 <jon_avila> jan: also concerned about format.
14:17:24 <jon_avila> kw: If we did this specific to HTML5 and then reference techniques for instructions rather than including it. Would that cover it?
14:17:32 <jon_avila> jan: possibly technique under 1.3.1
14:17:51 <jon_avila> kw: agress under 1.3.1
14:18:37 <jon_avila> alan: what about mobile apps?  We could have another technique.
14:19:03 <jon_avila> kp: question about speech users where app is not listening for what you are speaking.
14:19:37 <jon_avila> kp: User needs to know what key type app is listening to.
14:21:27 <jon_avila> ja: SC 3.3.2 may also be relevant to this technique.
14:23:34 <jon_avila> ja: relevant to desktop but more an of an issue to mobile.
14:23:46 <jon_avila> kp: Affects VO and speech users.
14:24:44 <jon_avila> kw: put in Jon's point about affecting what keyboard is shown on mobile device -- will add and see how we can incorporate this into the technique - will likely require multiple techniques for #4.
14:25:07 <jon_avila> TOPIC: #5 support characteristic properties for the platforms (font, etc.)
14:25:45 <jon_avila> kw: Comments all over the board.  Some people may want to focus specific settings.
14:27:59 <jon_avila> jan: technique should be very granular.  How do you program this in iOS vs. Android.  Windows has a high contrast mode whereas other's have invert colors.
14:28:20 <jon_avila> scribe: jon_avila
14:29:39 <jon_avila> kw:  should we break up or keep together?  Differences between platforms would be hard to maintain.   If we did this as one, would this be advisory, best practice, of ST?  and what SC?
14:31:56 <jon_avila> q?
14:32:54 <jon_avila> jan: captions are one example of play captions if user has set them.  Do something smart with user settings. Different from SC 1.2
14:33:29 <jon_avila> ja: UAAG perhaps, also Section 508 type requirement.
14:35:08 <jon_avila> jan: can generic refer to flags that browsers and apps can set.
14:36:23 <jon_avila> ja: iOS 8 has new flags to check for user requesting bold text, etc.
14:37:07 <jon_avila> kw: Mark as new SC/best practice because it currently doesn't map to WCAG or UAAG, any objections?
14:37:42 <jon_avila> TOPIC: 6. Set the virtual keyboard to the type of data entry required (e.g. date picker, email keyboard with @ sign)
14:38:27 <jon_avila> kw: responses were all over the place?
14:38:52 <jon_avila> jan: may depend on if it was apps or web.
14:39:17 <jon_avila> kw: this would apply to native apps as we already have prior one for HTML5?
14:40:30 <jon_avila> kw: perhaps 4.1.2?
14:41:35 <jon_avila> kw: may not have SC and something we should consider down the road.
14:41:50 <jon_avila> TOPIC: 7. Position important elements before the page scroll.
14:42:21 <jon_avila> kw: Detlev says page scroll will vary a lot based on device. Jan had similar comment.
14:46:35 <jon_avila> kw: no mappings to SC at this point.
14:46:44 <jon_avila> TOPIC: 8 group elements that go together.
14:48:30 <jon_avila> ja: h2 sounds a lot like this.
14:48:47 <jon_avila> kw: Any thoughts on why this might be an advisory?
14:48:47 <Zakim> -Alan_Smith
14:49:09 <jon_avila> jan: thinking about situations where one group awakens another controls - a larger relationship.
14:50:26 <jon_avila> ja: ST under 1.3.1 for grouping links.
14:50:35 <jon_avila> kw: is this already covered under current ST?
14:51:29 <jon_avila> RESOLUTION: would be to very and make sure we have this covered under current ST and add a mobile example to those.
14:51:56 <jon_avila> TOPIC: #9 Keep the page banner short to avoid unnecessary scrolling
14:51:58 <jon_avila> kw: varying techniques
14:52:59 <jon_avila> s/techniques/comments/
14:54:26 <jon_avila> jan: what's the alternate, there might be times were you want a long banner.
14:54:41 <jon_avila> kw: anyone disagree with keeping this a bp?
14:55:00 <jon_avila> TOPIC: 10 place buttons where they are easy to access.
14:56:13 <jon_avila> jan: concern over width - mm would be better than percents as device sizes are different.
14:56:23 <jon_avila> kw: don't see falling under any SC
14:57:18 <jon_avila> ja: reachability about using with one hand while holding and pressing a button.
14:58:12 <jon_avila> ja: best practice
14:58:25 <jon_avila> kw: keep at best practice
14:58:31 <jon_avila> kw: last one to go through for this meeting.
14:58:49 <jon_avila> kw: last call wed did 11,12,13,and 14.  Next call we will pick up on #15 from the survey.
14:59:08 <jon_avila> kw: can pick up and talk about iOS and browser settings if you have time.
14:59:13 <jon_avila> kw: Any questions?
14:59:36 <Zakim> -Jan
14:59:58 <Zakim> -Kim_Patch
15:00:20 <jon_avila> zakim, bye
15:00:20 <Zakim> leaving.  As of this point the attendees were +1.617.577.aaaa, Kathy, Kim_Patch, Jeanne, wuwei, Jan, [IPcaller], Alan_Smith
15:00:20 <Zakim> Zakim has left #mobile-a11y
15:01:12 <jeanne> present- 1.617.577.aaaa
15:01:48 <jon_avila> present+jon_avila
15:01:56 <jon_avila> present+ jon_avila
15:02:03 <jon_avila> present- IPcaller
15:02:10 <jon_avila> list attendees
15:02:15 <jon_avila> zakim, list attendees
15:02:42 <jon_avila> rrsagent, make minutes
15:02:42 <RRSAgent> I have made the request to generate http://www.w3.org/2014/06/06-mobile-a11y-minutes.html jon_avila
15:04:42 <jeanne> regrets+ Kathleen, Gavin, Detlev
15:04:56 <jon_avila> rrsagent, make minutes
15:04:56 <RRSAgent> I have made the request to generate http://www.w3.org/2014/06/06-mobile-a11y-minutes.html jon_avila
15:05:35 <jon_avila> rrsagent, bye
15:05:35 <RRSAgent> I see no action items