15:02:55 RRSAgent has joined #mobile-a11y 15:02:55 logging to http://www.w3.org/2016/06/30-mobile-a11y-irc 15:02:57 RRSAgent, make logs public 15:02:57 Zakim has joined #mobile-a11y 15:02:59 Zakim, this will be WAI_MATF 15:02:59 ok, trackbot 15:03:00 Meeting: Mobile Accessibility Task Force Teleconference 15:03:00 Date: 30 June 2016 15:03:59 Agenda+ Patrick's comments: https://github.com/w3c/Mobile-A11y-Extension/issues 15:04:01 Agenda+ Comments from WCAG: Finish survey: https://www.w3.org/2002/09/wbs/66524/MATF-062116/ 15:04:02 Agenda+ Next Steps – next meeting July 7 15:04:06 jon_avila has joined #mobile-a11y 15:04:11 present+jon_avila 15:04:14 chair: Kathleen_Wahlbin 15:05:06 Regrets+ Patrick, Henny 15:05:08 present+ Shadi 15:05:43 Present+ Kim 15:05:53 https://www.w3.org/WAI/GL/wiki/WCAG_2.1_timeline 15:06:42 Kathy: Deadline for 2.1. Coordination call with the other two taskforces 15:07:50 Kathy: crossover with low vision – affordances and contrast. Mobile drop these do not duplicate work – low vision take the lead on these and we will review 15:08:01 Present+ Detlev 15:09:31 Kathy: timeline – proposal for 2.1 must be into WCAG working group by December 1. Format same as for touch and pointer – success criteria, understanding paragraph, one sentence of what the techniques would be. Techniques don't have to be written, just proposed 15:09:54 Kathy: goal for December one is to have that for any other success criteria we want to propose and any changes to touch and pointer 15:10:46 Kathy: keyboard proposal definition change back and forth in email. Answer from chairs as we can propose anything, doesn't mean it will go through. So will go ahead with that 15:11:43 Kathy: WCAG 2.1 2018 we are two years away from getting this officially out and launched 15:12:13 Kathy: if we don't have it in by December 1 will not get into WCAG 2.1, will have to wait until 3.0 15:13:21 Kathy: David on the mailing list success criteria we don't have in here – have to talk about where it fits in. Conforming with breakpoints, not enough to work on desktop, must work on mobile 15:14:14 Detlev: interaction with other task forces logistics? 15:16:03 present+ jeanne 15:17:08 Kathy: wiki page that the coordinators have access to – Task Force exchange 15:17:15 Issues in GH -> https://github.com/w3c/Mobile-A11y-Extension/issues 15:19:35 https://github.com/w3c/Mobile-A11y-Extension/issues/2 15:21:09 This is what the entire 75 email thread to the list has been about for me, summed up in one sentence. This is what I would like to see in WCAg 2.1 That is not in 2.0 and is not in any 2.1 workup documents I've seen in COGA, LVTF, or MATF. 15:21:39 Kim_ has joined #mobile-a11y 15:22:02 https://github.com/w3c/Mobile-A11y-Extension/issues/2 15:22:12 This is what the entire 75 email thread to the list has been about for me, summed up in one sentence. This is what I would like to see in WCAg 2.1 That is not in 2.0 and is not in any 2.1 workup documents I've seen in COGA, LVTF, or MATF. 15:23:41 +1 15:24:15 Marc: move to 1.3 adaptable? 15:25:11 davidmacdonald has joined #mobile-a11y 15:25:16 sorry late 15:25:39 1.3 15:25:54 Kathy: did make this constrained. Wondering based on David's point if we need to revise this and talk about it in more general terms and have it move on different breakpoint and orientation 15:28:52 WCAG allows alternatives under the conformance requirements 15:29:12 David: the whole crux of the problem to me – different breakpoints will shift different components even if it's the same content. 15:30:06 You can also have a progressive enhancement site where minimal site is accessible but enhanced is not as long as you get to non-enhanced site 15:30:40 David: if I'm wrong, whole thread is necessary. Where in WCAG does it say two components to the same thing. You don't have to do anything as long as the link is accessible. I would say there's nothing in WCAG that says you have to have two components work if you have one component work and they do the same thing 15:31:54 You can conform without making a conformance statement 15:32:25 David: under WCAG you can say our site is conforming – just go home and use your desktop just like you don't have to say it works in any one browser 15:33:12 Detev: very common error people design hamburger menus and assume they don't have to be keyboard accessible. I've always assumed that if you do provide specific layouts than all those WCAG success criteria also apply to that view 15:34:08 David: we have different interpretation of what WCAG is… my interpretation just one view one stack that conforms 15:34:15 +1 to david 15:34:22 Kathy: in the US driven by a lot of legal requirements 15:34:40 David: I would love this to be wrong – I would love someone to prove me wrong because I don't want this to be true 15:35:28 q+ 15:35:36 Detlev: explicit requirements 15:36:20 2. Full pages: Conformance (and conformance level) is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded. 15:36:24 David: people just claim the minimum. Not very many people see this hole – want to see how I'm wrong 15:36:46 q+ 15:37:10 Jeanne: conformance requirement number 2 15:37:11 You can meet with alternatives. +1 to david 15:37:54 David: I want that conformance requirement to block it in but I don't think it does. I think we have lots of precedent and language where it says you can find an alternate component that can meet your requirement if that requirement works. 15:38:30 There are notes that apply to LongDesc 15:38:33 Full pages: Conformance (and conformance level) is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded. 15:38:33 Note 1: For the purpose of determining conformance, alternatives to part of a page's content are considered part of the page when the alternatives can be obtained directly from the page, e.g., a long description or an alternative presentation of a video. 15:38:33 Note 2: Authors of Web pages that cannot conform due to content outside of the author's control may consider a Statement of Partial Conformance. 15:38:36 I disagree 15:38:45 Detlev: you could only claim that for Internet sites you could not claim that general-purpose websites accessible for jaws. I think conformance requirement 2 would cover including things that are shown only at particular breakpoints 15:39:42 David: John doesn't think so, I don't really think so. If that's true – I hope it is, I wanted to be. But maybe we should make it explicit. Six of the people who know WCAG best in disagreement about this. We need to be clear and make it explicit. 15:39:59 +1 to adding a note to Conformance #2 15:40:02 Kathy: we can make a proposal to add to conformance number 2 15:40:28 +1 to david 15:40:52 David: every breakpoint – I think John, Patrick, Jason might answer no. I don't want to but I would answer no 15:41:13 If doing to right it is the width of window not device 15:41:21 David: big thing is components that shift are different based on the size of your screen. Will change the layout of that one page, same content 15:42:00 https://www.w3.org/TR/WCAG20/#conforming-alternate-versiondef 15:42:41 +1 to Marc 15:42:43 Marc: when we do this make it accessible for mobile too, I think how they back that up is same functionality. Mobile get same exact thing that desktop gets that's fine but as soon as the developers try to make it work for mobile you're now targeting a mobile platform 15:43:13 We agree with policy but WCAG doesn't clarify that. 15:43:17 David: conforming to alternative link – that was lots of conversation yesterday. If you shift page, link to bottom of page that says desktop site conforms you would meet WCAG 15:43:39 David: link at the bottom of the page, takes 10 minutes to find that link, have to go through that terrible mobile menu that is not working… 15:44:01 Kathy: low-vision perspective as well – might want to coordinate about what they're thinking as far as breakpoints as well 15:44:13 WCAG defintion: functionality processes and outcomes achievable through user action 15:44:50 https://www.w3.org/TR/WCAG20/#conforming-alternate-versiondef 15:44:58 David: one of their provisions is they want to be able to move it to one column. I would suggest ensure that all functionality in that view meets WCAG. There's nothing that I can see in the gap analysis that plugs that hole 15:45:50 Marc: you could extrapolate that you couldn't just tell someone go use the desktop version because then their process is completely different someone else's on that device. 15:45:57 Example 1: Successful use of a series of Web pages on a shopping site requires users to view alternative products, prices and offers, select products, submit an order, provide shipping information and provide payment information. 15:45:59 q? 15:46:18 Kathy: to complicate that further certain functions you provide different from mobile and desktop 15:46:22 ack jea 15:46:25 ack jon 15:48:45 A responsive site is not an alternative on another page, it is a single page with different display modes. 15:49:07 Jon: when I use 100% resolution I get multiple views on my desktop – when I zoom in I can't get to the other view and I have limited functionality and that's a problem for me on the desktop. We agree it's a problem, but I don't think it's addressed by the current WCAG 15:49:43 q+ 15:49:54 Jon: we believe that if we put these new mobile requirements in we can address it in a success criteria for WCAG 2.1 without modifying 15:50:00 q- 15:50:05 we still can't hear you 15:50:58 https://www.w3.org/WAI/GL/wiki/Components_delivered_as_part_of_the_initial_page_load_conform 15:51:43 Detlev: I agree with Jon. Good use cases for when you might want to see different things – people use mobile versions because they are simplified, much easier to do because they are different from the desktop sites. The whole idea that everything should be accessible in all versions is complicated by the fact that we won't be able to prescribe the same sets of functionality are offered. That... 15:51:45 ...also relates to the distinction that Alistair made in the mailing list. Same URL, different sites These two things we need to separate out somehow 15:52:10 This is what the entire 75 email thread to the list has been about for me, summed up in one sentence. This is what I would like to see in WCAg 2.1 That is not in 2.0 and is not in any 2.1 workup documents I've seen in COGA, LVTF, or MATF. 15:52:12 [Jason] What you’re arguing for, then, is the following: 15:52:13 If different user interface components or different versions of the content are provided, each customized for a distinct type of device or user agent, then the content only conforms to WCAG 2.1 if 15:52:15 (1) Each of the different user interface components or versions of the content conforms to WCAG 2.1 or 15:52:16 (2) A conforming alternate version is provided of each version of the content that does not conform, where the conforming alternate version is customized for the same type of device or user agent as the corresponding non-conformant version. 15:53:14 Not sure on word customized 15:55:00 Kathy: #2 what he's saying as you need to have some sort of version that works on that particular user agent device. So if you had a desktop version wouldn't that still conform because you could just go to the desktop version even though your default is going to show the mobile version? 15:55:29 What if the components can't be made accessible? 15:55:36 on one platform 15:55:47 q+ 15:55:51 David: based on viewport size so very specific type of customization Very thin net. Each one of those components needs to meet WCAG 15:55:54 q- 15:56:19 Jon: another concern – aria you menu keyword based won't work on iOS? 15:56:41 David: if you ship a menu your menu is now I custom version of that menu – might be different but shipped specifically for mobile device, that particular component that were shipped for mobile should work – that's what I'm saying 15:57:10 Jon: same functionality: 15:57:49 David: no. doesn't have to provide equivalent functionality of the desktop menu, but does have to conform to WCAG. 15:58:17 David: a component that we shipped based on viewport size. So each one of those components that shipped at a different viewport size has to be compliant. It doesn't have to do the same thing as the other breakpoints, just has to meet WCAG 15:58:49 q+ to say I asked Patrick's opinion. 15:58:55 Jon: worry that it's overly broad. Might work for a menu, but other components… 15:59:12 Jon: have to think about it more 15:59:56 Jeanne: Patrick said when we are talking about responsive design it's not an alternate page it's the same page. 16:00:19 David: but there's another component on this page which now is not showing that actually does work and if you just get yourself to a device that can show that then you've met WCAG 16:00:20 for responsive -- but I'm thinking of non-responsive sites 16:00:32 Kathy: lots of pages these days that have things that you can't see that are still part of the page 16:01:44 Jeanne: but it's still a part of the page. Have to be careful about writing ourselves into a corner about a situation that is still in flux. More important related issue: people be able to choose which they get on their device 16:02:12 David: as long as we can ensure that. but we are three experts who have different opinions on this 16:02:35 For responsive pages you have a strong case I agree. But david's desktop site example was not a responsive site example 16:02:40 Kathy: out of time – I have to think through this more in detail. 16:02:56 David: I think there's still lots of confusion. 16:03:19 Kathy: I'll talk to Andrew and Josh and see if we can get clarity as far as other opinions 16:03:36 Kathy: if we take it up in the working group call, more clarity as to what we should do in the task force 16:04:08 David: key question: three different breakpoints on your website does your menu have to meet WCAG get every breakpoint 16:04:42 Kathy: David to ask others as well 16:04:55 Kathy: good conversation – will get clarity and figure out direction 16:05:53 rrsagent, make minutes 16:05:53 I have made the request to generate http://www.w3.org/2016/06/30-mobile-a11y-minutes.html Kim 16:07:16 Present+ Marc, David, Kathy, 16:07:24 rrsagent, make minutes 16:07:24 I have made the request to generate http://www.w3.org/2016/06/30-mobile-a11y-minutes.html Kim