Last Comment Bug 1000082 - [AccessFu] When virtual focus is on a button or link, fire actual focus on the element, too
: [AccessFu] When virtual focus is on a button or link, fire actual focus on th...
Status: NEW
[Chrome-interop Safari-interop]
Product: Core
Classification: Components
Component: Disability Access APIs (show other bugs)
: Trunk
: ARM All
-- normal with 2 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: accessibility-apis
: alexander :surkov
Depends on:
Blocks: 1230801
  Show dependency treegraph
Reported: 2014-04-23 03:59 PDT by Marco Zehe (:MarcoZ)
Modified: 2016-11-06 13:52 PST (History)
4 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image Marco Zehe (:MarcoZ) 2014-04-23 03:59:36 PDT
This is a request brought to our attention by Patrick Lauke from the TPG. Both VoiceOver on iOS and ChromeVox on Android set focus on buttons and links (but not text fields) when users explore or swipe to them. On the desktop, NVDA does this, too, when the virtual cursor lands on such an element. In fact, NVDA does it with all focusable elements, but because on mobile devices, setting focus to text fields would immediately bring up the keyboard, text fields are excluded.

Reference/research done by Patrick:

1. Interoperability with iOS/VoiceOver+Safari and Chrome, and Android/ChromeVox+Chrome, therefore providing web developers with a more consistent experience.
2. Not taking away the ability from web developers to know when an element is focused when user visits their mobile app using FF/Android or Firefox OS.
Comment 1 User image Eitan Isaacson [:eeejay] 2014-04-23 15:15:26 PDT
Comment 2 User image Patrick H. Lauke 2016-10-18 14:51:09 PDT
Any movement on this? It now seems that TalkBack/Chrome have changed their behavior (focusing with TalkBack does NOT fire focus event / apply :focus styles), and the same happens with Windows 10 / Narrator (on desktop and phone/tablet, using touchscreen reading gestures). - so it's only iOS/VO that does this at the moment...
Comment 4 User image Patrick H. Lauke 2016-10-18 15:55:48 PDT
At a very high level, the request here is probably "cursor/focus should follow accessibility focus (with slight exceptions/special-casing for touch devices where a 'real' focus on a text entry field or similar triggers special behavior/interactions like on-screen keyboards)" (this would not only apply to Android/TalkBack/Firefox, but possibly more fundamentally on desktop etc as well)

Note You need to log in before you can comment on or make changes to this bug.