Focusable elements should fire focus event / receive :focus styling when they receive Narrator/accessibility focus
This issue relates to a current inconsistency among different AT, particularly evident on touchscreen devices. See https://patrickhlauke.github.io/touch/tests/results/#mobile-tablet-touchscreen-assistive-technology-events / https://twitter.com/patrick_h_lauke/status/788496138966106112
This has been brought up in the past with Mozilla with regards to Android/TalkBack/Firefox (xref https://bugzilla.mozilla.org/show_bug.cgi?id=1000082) and just now with Google for Android/TalkBack/Chrome (xref https://bugs.chromium.org/p/chromium/issues/detail?id=657157)
Thank you for the feedback and suggestion.
We will investigate this further with your help to see what might be possible.
Patrick H. Lauke commented
At a very high level, the request here is "cursor/focus should follow narrator/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)"