E-mail List Archives
Re: Web development; How to identify if a screen reader is in use
From: Jonathan C. Cohn
Date: May 12, 2017 6:44PM
- Next message: Bryan Garaventa: "The Screen Curtain Bookmarklet"
- Previous message: Birkir R. Gunnarsson: "Re: Web development; How to identify if a screen reader is in use"
- Next message in Thread: Jeremy Echols: "Re: Web development; How to identify if a screen reader is in use"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: Web development; How to identify if a screen reader is in use"
- View all messages in this Thread
Thinking about it, Google captua algorithm needs to be able to detect these patterns also. Otherwise AT users would be complaining that they always get visual or audio captures while AT users will automatically be verified.
Best wishes,
Jonathan Cohn
On May 12, 2017, at 8:06 PM, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> Are you suggesting then that any time a person is using the keyboard only, that there is likely a screen reader involved there somewhere?
>
> No I am not. In fact I didn't say keyboard -- I said navigation with a screen reader. I can't go into details but I'd say that when a screen reader is active there are clues related to events and interactions, etc. that can accurately predict this. Similarly when only the keyboard is used or when speech recognition is used there are certain patterns of events and interactions that provide clues. For high contrast and zoom there are similar clues when you insert content and you see the aspects of that content changed by the user's browser settings.
>
>> I think we both know that's not always true - people with mobility issues will also likely be using a keyboard only (or speech input), and / or power-users who have a preference for the keyboard.
>
> And this is important information as well. Seeing power users use keystrokes can be motivation to add or tweak settings -- and it has nothing to do with disability.
>
>> WCAG says that all content must be accessible to the keyboard for that specific reason, so meeting that requirement ensures that the content remains accessible to all of those users.
>
> I agree that all content should be fully keyboard accessible. But there is more to keyboard access than simply being keyboard accessible. The discussions currently surrounding single key shortcuts and there benefits or detriment to speech recognition users is one example.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> <EMAIL REMOVED>
> 703.637.8957 (Office)
>
> Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
> Download our CSUN Presentations Here!
>
> The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.
>
>
- Next message: Bryan Garaventa: "The Screen Curtain Bookmarklet"
- Previous message: Birkir R. Gunnarsson: "Re: Web development; How to identify if a screen reader is in use"
- Next message in Thread: Jeremy Echols: "Re: Web development; How to identify if a screen reader is in use"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: Web development; How to identify if a screen reader is in use"
- View all messages in this Thread