- From: Michael A. Peters <mpeters@domblogger.net>
- Date: Thu, 25 Jan 2018 10:10:18 -0800
- To: w3c-wai-ig@w3.org
I agree 110% Web applications should be developed to accommodate assistive technology without the web application knowing if the user is using assistive technology. That is inclusive without violating privacy. As much as I see the benefits of responsive design, a downside is it makes browser fingerprinting way too easy. Whether the user likely has a disability or not should never be part of the browser fingerprint. On 01/25/2018 09:35 AM, Glenda Sims wrote: > Danger. Danger. Privacy Concern. > > Goodwitch steps up on a privacy soapbox to say: > > Answering the question on screen reader detection and privacy concerns. > In the old days, it was impossible to detect if a screen reader was > running. But times they are a changing. For example, Apple now > provides a way for developers to know if VoiceOver is running. > > * *UIAccessibilityIsVoiceOverRunning()* > o https://developer.apple.com/documentation/uikit/1615187-uiaccessibilityisvoiceoverrunnin > <https://developer.apple.com/documentation/uikit/1615187-uiaccessibilityisvoiceoverrunnin> > > So...it comes down to...is detection of the use of screen reader (or > other assistive technology) a violation of privacy? The prevailing > answer (in the a11y community is...this is a violation of privacy. > > A few articles you might want to read for context: > > * *Detecting screen readers in analytics: Pros and cons *by Heather > Burns > 20160817* *https://www.powermapper.com/blog/accessibility-analytics/ <https://www.powermapper.com/blog/accessibility-analytics/> > * *On Screen Reader Detection *by Adrian Roselli written in 2014 but > updated as recently as 20170577 > * http://blog.adrianroselli.com/2014/03/on-screen-reader-detection.html <http://blog.adrianroselli.com/2014/03/on-screen-reader-detection.html> > * *Detecting Screen Readers: No *by Dennis Lembree > 20140314 http://www.webaxe.org/detecting-screen-readers-no/ > <http://www.webaxe.org/detecting-screen-readers-no/> > > Last but not least, the W3C is developing a spec called *IndieUI* which > currently has "screen reader settings" as restricted (private) data. > See W3C Editors Draft of IndieUI: User Context 1.0 > at https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html#userScreenReaderSettings > <https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html#userScreenReaderSettings> > This is not a final spec...nor is it a law...but to be on the safe side, > I advise not collecting this type of data or making decisions with it. > > ADA requirements are not based on statistics. It only takes one user > with a disability to result in an ADA compliant. > > Peace out, > Goodwitch > > glenda sims | team a11y lead | deque.com <http://deque.com> > | 512.963.3773 > *web for everyone. web on everything.* - w3 goals > > IAAP International Association of Accessibility Professionals: Certified > Professional in Accessibility Core Competencies (CPACC) > <http://www.accessibilityassociation.org/certification> > > > > > On Thu, Jan 25, 2018 at 11:22 AM, Lovely, Brian > <Brian.Lovely@capitalone.com <mailto:Brian.Lovely@capitalone.com>> wrote: > > Here’s a two-step answer: 1) Not yet, although the accessible object > model will likely allow this when it is implemented. 2) It’s a > slippery slope that should be navigated thoughtfully and carefully. > If you want to deliver equivalent experiences to all users, > detecting some and shunting them to an alternate experience is not > the best way to do that. Since ensuring accessibility generally > improves overall usablility, you would want to incorporate > accessibility in the application/website, and not in some accessible > ghetto.____ > > __ __ > > *From:* Patti Burke Lund [mailto:pburkelund@yahoo.com > <mailto:pburkelund@yahoo.com>] > *Sent:* Thursday, January 25, 2018 12:04 PM > *To:* w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> > *Subject:* Assistive Technology Detection____ > > __ __ > > Hello Everyone! I had a question come in today from a student. I'm > hoping this group might be able to provide some insight...____ > > __ __ > > 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?"____ > > __ __ > > Thank you!____ > > __ __ > > Best,____ > > Patti____ > > ____ > > __ __ > > *Patti Burke Lund*____ > > Colorado State University | Journalism & Media Communication____ > > patricia.burke-lund@colostate.edu > <mailto:patricia.burke-lund@colostate.edu> | pburkelund@yahoo.com > <mailto:pburkelund@yahoo.com> | www.colostate.edu > <http://www.colostate.edu>____ > > LinkedIn <https://www.linkedin.com/in/pburkelund/>____ > > __ __ > > > ------------------------------------------------------------------------ > > The information contained in this e-mail is confidential and/or > proprietary to Capital One and/or its affiliates and may only be > used solely in performance of work or services for Capital One. The > information transmitted herewith is intended only for use by the > individual or entity to which it is addressed. If the reader of this > message is not the intended recipient, you are hereby notified that > any review, retransmission, dissemination, distribution, copying or > other use of, or taking of any action in reliance upon this > information is strictly prohibited. If you have received this > communication in error, please contact the sender and delete the > material from your computer. > >
Received on Thursday, 25 January 2018 18:10:48 UTC