Skip to content

Specify keyboard focus separately from Screen Reader focus #34737

Open

Description

@aliossam

Description

On Android keyboard focus and accessibility focus are handled separately at the system level. Often these match, as many accessibility services use the “focusable” property (which informs keyboard focus), to also inform them where to focus. In API 28 however, Android added the setScreenReaderFocusable property to View (https://developer.android.com/reference/android/view/View#setScreenReaderFocusable(boolean)) which allows you to flag a view as being focusable only for screen readers, without making that same view focusable by keyboards.

This is useful since screen readers often want to focus on views that are content only, but not actionable (so their users can hear the content), but focusing on these content elements is not useful for keyboard navigation users, who only need to be able to move between interactive elements.

Right now in React Native, the accessible prop maps to focusable on Android, making the element focusable by both screen readers and keyboard users.

There are a few different approaches we could take here. We could surface a new prop called screenReaderFocusable, that sets focusable to false but screenReaderFocusable to true, we could adjust the accessible prop to only set screenReaderFocusable to true, and add a new prop for keyboardFocusable which sets focusable to true, or we could have the accessible prop contextually set either focusable (if the element is interactive by having a click handler) or screenreaderFocusable (if it’s content only).

Version

0.66

Output of npx react-native info

see description

Steps to reproduce

see description

Snack, code example, screenshot, or link to a repository

see description

Activity

  1. github-actions commented on Mar 20, 2023

    @github-actions

    This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

  2. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Mar 20, 2023
  3. lindboe commented on Mar 20, 2023

    @lindboe
    Contributor

    This is still relevant! Keyboard navigation (or TV remote navigation) users have different needs than screen-reader users.

  4. removed
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Mar 21, 2023
  5. github-actions commented on Sep 27, 2023

    @github-actions

    This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

  6. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Sep 27, 2023
  7. frankcalise commented on Oct 2, 2023

    @frankcalise
    Contributor

    Still relevant, please keep open

  8. added
    Never gets stalePrevent those issues and PRs from getting stale
    and removed
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Oct 2, 2023
  9. trcoffman commented on Jul 16, 2024

    @trcoffman

    Yeah this would be awesome to get resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions