[AccessFu] When virtual focus is on a button or link, fire actual focus on the element, too

NEW
Unassigned

Status

()

defect
5 years ago
5 months ago

People

(Reporter: MarcoZ, Unassigned)

Tracking

(Blocks 1 bug)

Trunk
ARM
All
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [Chrome-interop Safari-interop], )

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: http://t.co/BObb5THOKC

Benefits:
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.
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). https://patrickhlauke.github.io/touch/tests/results/#mobile-tablet-touchscreen-assistive-technology-events - so it's only iOS/VO that does this at the moment...
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)
Blocks: 1230801
Eitan, will our new implementations have any effect on this bug?
Flags: needinfo?(eitan)
No. At least not the first part.

Regardless, this is not how Chrome/Talkback interoperate these days. Maybe this was the case with ChromeVox, I don't know.

Focus does follow the accessibility focus. That might be different in iOS, but I think our implementation should be closer to Chrome/WebView.

I'm tempted to close this as WONTFIX.
Flags: needinfo?(eitan)
Close at your discretion. :)
On second thought, and after reading the Chrome bug, I think we can do this for non-editable elements. So it might be worth leaving open.
You need to log in before you can comment on or make changes to this bug.