I suggest you ...

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

In iOS/VoiceOver/Safari, when a focusable element (link, button...but some special casing seems to happen for text entry fields and similar) receives VO focus, the JavaScript focus event is fired and CSS :focus styles apply. In most other OS/AT/browser combinations, this is currently not the case - accessibility focus does not trigger focus() / :focus.

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)

12 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Patrick H. LaukePatrick H. Lauke shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Patrick H. LaukePatrick H. Lauke commented  ·   ·  Flag as inappropriate

        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)"

      Feedback and Knowledge Base