14:37:53 <RRSAgent> RRSAgent has joined #matf
14:37:53 <RRSAgent> logging to http://www.w3.org/2016/09/21-matf-irc
14:37:58 <AWK> ... different application for different parts of the service
14:38:02 <jeanne> jeanne has joined #matf
14:38:04 <AWK> ... and received feedback
14:38:17 <AWK> ... so they formed task forces to address
14:38:20 <chunming> present+ chunming
14:38:21 <patrick_h_lauke> Scribe: AWK
14:38:54 <AWK> Objective: share implementation practices from Alibaba
14:39:17 <AWK> blind users  use screen readers to navigate, on PC and mobile devices
14:39:30 <AWK> presentation will share difficulties shared with team
14:39:45 <AWK> use case 1: picture - no description
14:39:59 <AWK> solution: alt attribute on img elements
14:40:46 <chunming> present+ kepeng, IanPouncey, jeanne, patrick_h_lauke, AWK, QingAn
14:41:53 <AWK> case 2: verification code (CAPTCHA)
14:42:02 <patrick_h_lauke> AWK: as the slide contains HTML, are your apps native or hybrid (e.g. using phonegap)
14:42:11 <AWK> screen reader users can't read it
14:42:39 <AWK> solution: voice verification or SMS code verification
14:43:51 <AWK> AWK: Which was better received?
14:44:02 <AWK> KL: Not completely sure, think Voice
14:44:11 <AWK> Case 3: Floating page
14:44:22 <QingAn_> QingAn_ has joined #matf
14:44:27 <AWK> focus issues, closing issues
14:44:38 <QingAn_> QingAn_ has left #MATF
14:44:41 <AWK> solution: ensure dialog is focused and able to be closed
14:44:49 <AWK> case 4: focus
14:45:01 <AWK> no focus on page, user can't select
14:45:11 <AWK> for each element, ensure focus with attribute
14:45:15 <AWK> case 5: controls
14:45:29 <AWK> missing labels
14:45:37 <AWK> solution: add labels
14:46:58 <AWK> case 6: missing labels
14:47:06 <AWK> solution: use for attribute
14:47:17 <AWK> Gap analysis
14:47:30 <AWK> In WCAG there is a need for more details
14:47:35 <AWK> more techniques!
14:47:46 <AWK> Next steps
14:47:59 <AWK> detailed drafts will be submitted to document the issues and practices
14:48:44 <AWK> AWK: These are the common issues, were there more
14:49:59 <patrick_h_lauke> AWK: now that you've addressed things as per your slides, do you still have issues that users are reporting?
14:50:26 <chunming> q+
14:50:28 <AWK> KL: yes, some issues addressed but there were more
14:51:12 <AWK> chunming: interested in the MATF
14:51:58 <AWK> ... talked with Judy Brewer, told that we are increasing mobile guidance in WCAG
14:52:44 <AWK> ... we may like to participate in effort
14:53:38 <AWK> PL: Issues seem to be largely in WCAG 2.0
14:53:48 <AWK> PL: seems to be following WCAG best practices well
14:55:06 <AWK> AWK: the SMS integration is a solution that is more mobile focused but increasingly available on desktop also
14:55:29 <jeanne>  https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m1.md
14:55:57 <AWK> IP: WCAG doesn't specifically speak to things like the dialog issue mentioned
14:56:11 <AWK> (floating page)
14:56:59 <patrick_h_lauke> Patrick: here's some of the work we're doing specifically in the "Mobile" Accessibility Taskforce, particularly focused on different input modalitites https://gist.github.com/patrickhlauke/96110b10547770021e58f5098dd31087
14:58:05 <AWK> AWK: speaks to a need for more techniques
14:58:21 <QingAn> QingAn has joined #matf
14:58:46 <AWK> PL: (sharing gist of current work of MATF)
14:59:45 <AWK> PL: moving to a situation where there are many modalities that need to be covered for input
15:00:11 <AWK> PL: currently in WCAG we have keyboard-specific items, but not touch
15:02:07 <AWK> PL: or pointer devices
15:02:28 <AWK> ... also looking to address size of targets
15:02:37 <AWK> to ensure that they aren't too small
15:03:26 <AWK> ... avoiding accidental activation also
15:03:47 <AWK> ... and when running a keyboard and assistive technologies
15:04:35 <AWK> ..input independence is also needed - can't rely on just one way to interact
15:05:47 <AWK> ... for apps running in a closed environment (e.g. kiosk/ATM) may not need to support a keyboard if there is no way to add a keyboard
15:06:29 <AWK> .. The MATF also has SC proposals related to voice interaction
15:07:07 <AWK> ...And related to device sensors
15:09:05 <AWK> ... Some applications may rely on device sensors exclusively in some situations (e.g. a marble game where tilting the device is the game)
15:11:15 <AWK> Non-interference with assistive technologies is the final SC being proposed.
15:11:32 <AWK> IP: question: is that AT-specific?
15:12:17 <AWK> Section 508 has criteria that says to not interfere with user system settings
15:12:34 <AWK> PL: builds on that idea a bit
15:13:25 <AWK> KL: question b/c mobile devices don't have keyboards - how to handle?
15:13:51 <AWK> PL: can connect a keyboard via bluetooth and use it
15:14:58 <chunming> rrsagent, draft minutes
15:14:58 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/21-matf-minutes.html chunming
15:15:19 <chunming> rrsagent, make log public
15:17:54 <AWK> AWK: WCAG covers a lot of what you need to do for mobile device support, but more is needed and that is why we have the task force and the WCAG 2.1 effort
15:19:03 <AWK> PL: there are also issues for users who use mobile OS zoom features - some issues can occur when using mobile zoom and trying to pinch and zoom
15:20:17 <AWK> KL: which issues affect users who are blind or VI?
15:20:41 <AWK> PL: We don't generally differentiate since the success criteria impact more than one user type each
15:21:35 <AWK> JS: China has very active blind user group
15:23:17 <jcraig> jcraig has joined #matf
15:23:34 <patrick_h_lauke> AWK: reiterating that with SCs we try to not differentiate by user group/disability
15:24:21 <jcraig> rrsagent, make minutes
15:24:21 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/21-matf-minutes.html jcraig
15:24:24 <patrick_h_lauke> even if an SC may initially look/sound like it's only targeted at a particular disability, it has benefits well beyond those
15:24:42 <AWK> KL: why have a LVTF?
15:25:09 <patrick_h_lauke> KL: and why not a blind user TF specifically
15:25:39 <patrick_h_lauke> AWK: there was feeling from specifically LV users that felt WCAG 2.0 doesn't address very particular problems of LV
15:25:53 <patrick_h_lauke> which is why there is a user group/disability specific TF
15:26:43 <patrick_h_lauke> jcraig yeah sorry it's not on the grid for some reason
15:26:50 <patrick_h_lauke> in 1.03 if you still want to pop in
15:28:45 <AWK> KL ;question about keyboard trap
15:28:50 <AWK> PL: explained
15:29:06 <AWK> ...that keybaord trap and focus trap are the same issue
15:29:16 <AWK> s/keybaord/keyboard
15:29:31 <AWK> KL: how to contribute?
15:29:43 <AWK> ... will go back to teams for more information
15:32:45 <AWK> AWK: everyone's help is needed!  Welcome to join the group...
15:33:24 <AWK> rrsagent, draft minutes
15:33:24 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/21-matf-minutes.html AWK
15:35:29 <patrick_h_lauke> rssagent, make logs world-visible
15:56:49 <Byungjin> Byungjin has joined #matf
15:59:02 <jeanne> jeanne has joined #matf
16:51:51 <patrick_h_lauke> patrick_h_lauke has joined #matf
17:08:51 <patrick_h_lauke1> patrick_h_lauke1 has joined #matf
17:15:49 <patrick_h_lauke> patrick_h_lauke has joined #matf
17:17:00 <Zakim> Zakim has left #MATF
18:03:13 <jeanne> jeanne has joined #matf
22:03:03 <patrick_h_lauke> patrick_h_lauke has joined #matf
22:06:01 <patrick_h_lauke> patrick_h_lauke has left #MATF