- From: ALAN SMITH <alands289@gmail.com>
- Date: Tue, 28 Jun 2016 13:14:35 -0400
- To: David MacDonald <david100@sympatico.ca>, John Foliot <john.foliot@deque.com>
- Cc: "Patrick H. Lauke" <redux@splintered.co.uk>, WCAG <w3c-wai-gl@w3.org>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <5772b07a.51e10d0a.7b57d.ffffdfa6@mx.google.com>
Another thing to consider is that from my experience in the business world, mobile specific apps have far less functionality, information and clutter and a link to a desktop website will give them a totally different experience with far too much informational differences. From a cognitive standpoint it will be overwhelming what they will have to go through to get to the same places and same information or same functionality as they would on the mobile specific app. We perform a function point analysis and give numbers of additional clicks, links, etc. to go through a pay your bill online app on a mobile device versus a desktop version of the same functionality. Alan Smith, CSTE, CQA Sent from Mail for Windows 10 From: David MacDonald Sent: Tuesday, June 28, 2016 1:08 PM To: John Foliot Cc: Patrick H. Lauke; WCAG; public-mobile-a11y-tf@w3.org Subject: Re: Conforming alternative for mobile should not be Desktop >>>David, can you provide us with an example of this use-case? I would like to understand how a change in viewport size would affect a blind person. They will be on their mobile device, and not likely have a keyboard. Swiping through a mega menu designed for a desktop site with VoiceOver is a degraded experience when the mobile menu has been optimized for the mobile experience for sighted users... The other consideration is that most blind people have some sight and use it in conjunction with VoiceOver, and using VoiceOver without using their sight because the desktop view is too small for them, is a degraded experience for them. Cheers, David MacDonald CanAdapt Solutions Inc. Tel: 613.235.4902 LinkedIn twitter.com/davidmacd GitHub www.Can-Adapt.com Adapting the web to all users Including those with disabilities If you are not the intended recipient, please review our privacy policy On Tue, Jun 28, 2016 at 12:53 PM, David MacDonald <david100@sympatico.ca> wrote: I don't agree ... I don't think sticking a link to a desktop site at the bottom of the mobile view is the spirit of the alternate version provision as we created it. This is a hugely degraded experience for a low vision user and also a blind person who is going to be accessing a desktop site in a mobile browser ... this is not at all what we intended with the alternate version exemption. The alternate version exemption came from the old alternative text version provision in WCAG 1.1. We didn't want to forbid people from making an alternative like that if it was kept up to date and had all the information. WCAG 2.1 will be out in 2018. I do not want to tell my clients, in age where we fly to mars, "don't worry about mobile accessibility, just put a link to the desktop version in all your responsive designs." If we do that, let's just close up the Mobile task force now and not waste our time. People with disabilities deserve better. Cheers, David MacDonald CanAdapt Solutions Inc. Tel: 613.235.4902 LinkedIn twitter.com/davidmacd GitHub www.Can-Adapt.com Adapting the web to all users Including those with disabilities If you are not the intended recipient, please review our privacy policy On Tue, Jun 28, 2016 at 11:04 AM, John Foliot <john.foliot@deque.com> wrote: Hi Patrick, I think we are agreeing. JF On Tue, Jun 28, 2016 at 9:09 AM, Patrick H. Lauke <redux@splintered.co.uk> wrote: On 28/06/2016 14:13, David MacDonald wrote: not forcing blind people to go home and use their desktops because the mobile view doesn't work. To be absolutely clear on where I'm coming from: IF a site, when viewed on a mobile/tablet/small screen viewport is inaccessible, and it does NOT provide a mechanism for the user to reach (on that same device/viewport) the accessible "desktop" version, then it fails under WCAG 2.0 (for all the bits where it's inaccessible), and can't claim to be an "alternate version" as, per point 4 of the definition, it's not allowing the user to reach the desktop version. This is why I don't think specifically calling out "the mobile version/view needs to be accessible" is needed, and it feels wrong/weird to single it out. P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke -- John Foliot Principal Accessibility Strategist Deque Systems Inc. john.foliot@deque.com Advancing the mission of digital accessibility and inclusion
Received on Tuesday, 28 June 2016 17:15:10 UTC