4 ms·
> well, the fact is the use of a screen reader (or at least most) can be detected relatively easily by having an element in the screen reader flow that is hidde
by jscholes 6y ago
> well, the fact is the use of a screen reader (or at least most) can be detected relatively easily by having an element in the screen reader flow that is hidden from sighted users
This isn't true, at least not enough to be useful. The majority of screen readers present web pages in a kind of virtual buffer, which users can browse with the arrow keys and other shortcuts (e.g. H to jump by heading). In this mode, the majority of screen readers don't fire focus events to let you know, "hey, your screen-reader-only element has been hit". You would be limited to:
1. users operating a screen reader which does fire focus events;
2. trying to highjack scroll events for this purpose; and
3. less technically-inclined users (read: beginners) who move through the page with Tab/Shift+Tab before they've learned the other keystrokes their screen reader offers.
- bryanrasmussen 6y agoI guess #3 explains my confusion, as whenever I use a screenreader it's for testing and I just tab through. I suppose each screen reader then has its own hotkey shortcuts? Do you know of any resource that puts shortcuts of most popular screen readers together?
- mwcampbell 6y agoIf you happen to be using Windows, Narrator has a well-written tutorial (no, I didn't write it) that goes into the most common shortcuts, and you can get a complete list with Narrator+F1 (the "Narrator" key is either Caps Lock or Insert). I believe VoiceOver on Mac also has a tutorial.