- From: Ash Ta <duc.ta.740@gmail.com>
- Date: Thu, 25 Jan 2018 09:55:57 -0800
- To: tink@tink.uk
- Cc: Patti Burke Lund <pburkelund@yahoo.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <CACsk6Exm9i25tqyFi3m0g9i41RALW-A2Fw_RBGPHeMgQbCZpiA@mail.gmail.com>
I would rather go to general concept in developing universal accessible website than tailoring to certain specific. It is certain that it is not impossible to detect AT (JAWS or NVDA) in the website. I think I read something called detecting something running using host via IE and X-content or something. It is a really long time I read that. I used to have the same thought like you until we tried to develop universal accessible content Best, Duc Ta On Thu, Jan 25, 2018 at 9:41 AM, LĂ©onie Watson <tink@tink.uk> wrote: > > On 25/01/2018 17:04, Patti Burke Lund wrote: > >> Question: >> "I understand accessibility needs to be integrated into every aspect of >> your website. I was wondering if there is any way to detect whether a user >> is using support for their disability and then adjust your website to >> support them even more? Kind of similar to the way Responsive Web Design >> detects browser window size then adjusts accordingly?" >> > > It's possible to do this with native apps on mobile platforms, but not > with websites and webapps. > > It's also an extremely controversial idea because it has implications for > privacy, quality, maintenance, and a few other things besides. Here's my > take on it as a screen reader user: > https://tink.uk/thoughts-on-screen-reader-detection/ > > > > >> Thank you! >> >> Best, >> Patti >> >> Patti Burke Lund >> Colorado State University | Journalism & Media Communication >> patricia.burke-lund@colostate.edu | pburkelund@yahoo.com | >> www.colostate.edu >> LinkedIn <https://www.linkedin.com/in/pburkelund/> >> >> > -- > @LeonieWatson @tink@toot.cafe Carpe diem > > -- ---------------------------- Duc Ta IT Consultant Tel: (323) 412-4894 www.dtaconsulting.org
Received on Thursday, 25 January 2018 17:56:20 UTC