14:42:20 <RRSAgent> RRSAgent has joined #mobile-a11y
14:42:20 <RRSAgent> logging to http://www.w3.org/2015/06/04-mobile-a11y-irc
14:42:22 <trackbot> RRSAgent, make logs public
14:42:22 <Zakim> Zakim has joined #mobile-a11y
14:42:24 <trackbot> Zakim, this will be WAI_MATF
14:42:24 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
14:42:25 <trackbot> Meeting: Mobile Accessibility Task Force Teleconference
14:42:25 <trackbot> Date: 04 June 2015
14:46:43 <Kim> agenda+ Best Practices - Robust http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniques
14:46:44 <Kim> agenda+ WCAG Feedback
14:46:46 <Kim> agenda+ Next steps – next meeting Thursday, June 4
14:47:08 <Kim> Agenda?
14:48:49 <Detlev> Detlev has joined #mobile-a11y
15:01:44 <Mike_P> Mike_P has joined #mobile-a11y
15:02:24 <Kim> regrets+ Jan_Richards,  Mike_Shebanek, David_McDonald, Henny_Swan
15:04:21 <jon_avila> jon_avila has joined #mobile-a11y
15:06:15 <Mike_P> Webex is asking for a meeting password - I don't see that on the invite
15:06:21 <marcjohlic> marcjohlic has joined #mobile-a11y
15:06:30 <marcjohlic> present+ marcjohlic
15:06:39 <Kim> zakim, take up next
15:06:40 <Zakim> agendum 1. "Best Practices - Robust http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniques" taken up [from Kim]
15:09:02 <jeanne> jeanne has joined #mobile-a11y
15:10:45 <Kim> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniques
15:12:32 <Kim> http://w3c.github.io/Mobile-A11y-TF-Note/
15:13:20 <jon_avila> scribe: jon_avila
15:13:37 <jon_avila> TOPIC: set data entry to type of keyboard required
15:14:10 <jon_avila> jeanne: need to note that it can be less accessible for some but more accessible for others
15:14:37 <jon_avila> jeanne: could be issue for overlays, etc or people who predict layout
15:16:49 <jon_avila> jeanne: for most people it will be an improvment -- people with mobility issues
15:16:55 <jon_avila> kim: note is good idea
15:18:08 <jon_avila> detev: rethink what moving from robut to perhaps input assistance guideline 3.3
15:19:25 <jon_avila> kim: could be situation where developer has narrowed field to small and cut out option such as speech users being able to input
15:19:36 <jon_avila> kim: developers may not be aware of input possibilities
15:20:24 <jon_avila> detlev: good example with email to add @ sign and remove space.  But other situations could be problematic.
15:20:42 <jon_avila> jeanne: on iOS can usually change keyboard
15:21:14 <jon_avila> kim: what happens when field can't handle input but speech is enabled and can input a space.
15:23:14 <jon_avila> jon_avila: situation could arise where a keyboard doesn't support an input method such as paste but others would -- this could affect users of speech or other input methods.
15:24:50 <jon_avila> alan: iOS keyboard only always shows caps.  Android changes.
15:27:54 <jon_avila> detlev: Seems like user agent guidelines item.  Not sure how much control author has over keyboard.
15:28:22 <jeanne> Jeanne will add this discussion to the User Agent Capabilities page: https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/User_Agent_Capabilities
15:28:53 <jon_avila> kim: speech users may be in app but issue a global command.  With phones you typically are in narrow context -- but on Android you can have two things open at once.
15:29:46 <jon_avila> kim: Might want to do something more than what the keyboard would show.  Let the user control.
15:30:34 <jon_avila> detlev: perhaps that beyond the advice or techniques that we give.
15:30:52 <jon_avila> Kim: good to make people aware of the situations.  Connected with consistency of commands.
15:31:21 <jon_avila> kim: any other best practices related to setting virtual keyboard?
15:33:19 <jon_avila> detlev: Perhaps hints or other native techniques that could be useful
15:33:55 <jon_avila> detlev: could fit under 4.1.2
15:40:00 <jon_avila> kim: asks question about switch users and how changes to on-screen keyboard affects them and timing/consistency
15:40:17 <jon_avila> jeanne: more future oriented to have people support better semantics of input type
15:40:59 <jon_avila> kim: how does the user opt out?
15:41:11 <jon_avila> jeanne: seems that should be at the UAAG level
15:42:17 <jon_avila> jeanne: could support authors are aware of the variety of potential input such as a physical keyboard.
15:45:04 <jon_avila> jon_avila has joined #mobile-a11y
15:45:11 <jon_avila> scribe: jon_avila
15:45:25 <jon_avila> * I got kicked out of IRC but now I am back
15:47:29 <jon_avila> detlev: harder to provide text input on mobile -- screen is small and the user may be zoomed in.
15:48:00 <jon_avila> kim: are we talking about letters, numbers, characters?
15:48:10 <jon_avila> kim: correcting data entry is also part of it.
15:48:27 <jon_avila> detlev: Could also be providing input that has microphone button to support entry by voice
15:48:51 <jon_avila> kim:  can't backspace with speech
15:48:57 <jon_avila> jeanne: Platform issue.
15:49:04 <jon_avila> kim: Different input methods have different abilities
15:49:20 <jon_avila> kim: gesture input may be limited
15:51:49 <jon_avila> alan: easy is ambiguous term that is hard to test
15:53:38 <jon_avila> kim: Are we looking for techniques that accommodate all methods?
15:54:03 <jon_avila> detlev: good to have more than one way.
15:54:17 <jon_avila> Mikep: multiple ways to support input modalities
15:55:29 <Detlev> Jon: Specifying the input method can be tricky by being unnecessarily restrictive
15:56:05 <Detlev> Jon: Having the date picker  could mean not having the mic
15:56:32 <jon_avila> kim: some input methods breakdown quickly.  We need consistency -- but many things are controlled by the platform
15:57:28 <jon_avila> detlev: thinking of suggestion list that has an added advantage.  Would not take aways ability but add to it.  Good general technique.  Not sure where it might fit.
15:58:59 <jon_avila> kim: don't want to narrow the input abilities
15:59:15 <jon_avila> q?
16:00:55 <jon_avila> jeanne: is a platform bug
16:01:40 <jon_avila> zakim, make minutes
16:01:40 <Zakim> I don't understand 'make minutes', jon_avila
16:01:54 <jon_avila> zakim, attendees
16:01:54 <Zakim> I don't understand 'attendees', jon_avila
16:02:04 <jon_avila> RRSAgent, make minutes
16:02:04 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/04-mobile-a11y-minutes.html jon_avila
16:05:44 <Kim> chair: Kimberly_Patch
16:05:54 <Kim> RRSAgent, make minutes
16:05:54 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/04-mobile-a11y-minutes.html Kim
16:06:59 <Kim> chair: Kimberly_Patch
16:07:12 <Kim> RRSAgent, make minutes
16:07:12 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/04-mobile-a11y-minutes.html Kim
16:10:47 <Kim> present+ Kimberly_Patch, Jeanne_Spellman, Jon_Avila, Detlev_Fisher, Mike_Pluke, Mark_Johlic, Alan
16:11:00 <Kim> RRSAgent, make minutes
16:11:00 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/04-mobile-a11y-minutes.html Kim
16:22:27 <Kim> present Kimberly_Patch, Jeanne_Spellman, Jon_Avila, Detlev_Fisher, Mike_Pluke, Mark_Johlic, Alan
16:22:53 <Kim> RRSAgent, make minutes
16:22:53 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/04-mobile-a11y-minutes.html Kim