W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2017

Re: Moving Issues 62, 63, 71 to the conformance section

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Sun, 16 Jul 2017 13:58:40 +0100
To: w3c-wai-gl@w3.org
Message-ID: <67acef17-8e13-4211-0f65-dff900e56e62@splintered.co.uk>
On 14/07/2017 17:57, David MacDonald wrote:
>  > Try as I might, I've not gotten VoiceOver to work on my Samsung 
> Galaxy yet, and I don't think I ever will...
> 
> Yes it is shorthand, however, I don't think we can require developers to 
> support every environment. Especially buggy environments ...  (such as 
> Talkback/Android)

A bit of a sweeping statement, considering VO like all other AT also has 
bugs and shortcomings.

In any case yes, as with AT support on desktop, we want to make sure 
that things first and foremost follow standards (correct use of ARIA, 
HTML, CSS, JS, SVG, etc), and secondly that these technologies are 
applied in an accessibility supported way (with all the fuzziness 
surrounding that definition) 
https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head 


I do want to echo John's overall sentiment though that we should be 
careful not to use synecdoche (VoiceOver to stand for "AT on 
mobile/tablet/touch-enabled devices"; "small screen" as a shorthand for 
"mobile touch-screen only device") that comes across as biased, 
limiting, or inaccurate.

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
Received on Sunday, 16 July 2017 12:59:09 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:15 UTC