E-mail List Archives
Re: Developers don't detect my screen reader
From: Moore,Michael (HHSC)
Date: Aug 10, 2015 8:40AM
- Next message: Jared Smith: "Re: Developers don't detect my screen reader"
- Previous message: Léonie Watson: "Re: Developers don't detect my screen reader"
- Next message in Thread: Jared Smith: "Re: Developers don't detect my screen reader"
- Previous message in Thread: Léonie Watson: "Re: Developers don't detect my screen reader"
- View all messages in this Thread
In my opinion AT detection would pose several unacceptable risks. First is a privacy issue. Using automated AT detection is requiring someone to make a declaration of a disability without their consent. Would you find it acceptable to deploy something on your that would allow you to automatically detect the race, gender, sexual orientation or age of the site visitor and then make changes based upon those findings?
Second is a security risk. Reliably detecting what software is running on a system involves deeper penetration into the OS layer of the system to detect which process are running. Thus for an OS to allow this creates a dangerous security hole.
Best practice is to design a site that everyone can use. It will work better for everyone. I don't see any problem with allowing users to set preferences and customize the interface for themselves with the option of having those settings be persistent on subsequent site visits.
Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
(512) 574-0091 (Cell)
- Next message: Jared Smith: "Re: Developers don't detect my screen reader"
- Previous message: Léonie Watson: "Re: Developers don't detect my screen reader"
- Next message in Thread: Jared Smith: "Re: Developers don't detect my screen reader"
- Previous message in Thread: Léonie Watson: "Re: Developers don't detect my screen reader"
- View all messages in this Thread