- From: Mark Weiler <mweiler@alumni.sfu.ca>
- Date: Fri, 26 Jan 2018 00:36:34 +0000 (UTC)
- To: David Woolley <forums@david-woolley.me.uk>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Received on Friday, 26 January 2018 00:48:29 UTC
Related to AT detection is how can a site or app know what web content technologies to serve up that are accessibly supported without knowing the user agents and AT the user is using? Accessibility supported is a requirement for conformance. And research findings show differences in how browsers and ATs are supporting web content technologies. On Thursday, January 25, 2018 7:08 PM, David Woolley <forums@david-woolley.me.uk> wrote: The dangers I see are: 1) this will reinforce the idea that the only disabled people are those that use JAWs. 2) it will probably have a similar effect to early mobile web sites, which tended to be cleaner, and easier to use that the main web site. That may mean that the main web site gets more difficult to use, and you won't be able to do the equivalent of using wap instead of www. On 25/01/18 19:18, accessys@smart.net wrote: > > counter to concept of accessibility, one should not need to identify > and personally I would be ,opposed to it.
Received on Friday, 26 January 2018 00:48:29 UTC