microsoft / microsoft/react-native-gallery

[React Native Gallery -> Permissions]: Keyboard focus and Narrator focus are not on sync when user navigate to 'Request' button.

Open
#313 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11ySev3 Area: Accessibility enhancement
Dominant language
TypeScript
Stars
257
Forks
57
Avg merge
18h 19m
Merged PRs (30d)
10

Description

Repro-Steps:
Launch the React Native Gallery app.
Navigate to ‘Permissions’ button and invoke it.
Navigate to ‘Request’ button and invoke it.
Now renavigate to the invoked Request button and observe the keyboard and narrator focus.

Actual Result:
While renavigating to “Request” button narrator focus is not moving with kb focus hence these controls are not announced by the narrator. Narrator focus stays on the last interacted element.

Expected Result:
While navigating to “Request” button narrator should announce the proper information to the user as “Request windows.permission.appCaptureServices, button, disabled”.

User Impact:
Users with visual impairment who rely on screen reader will get confused if narrator focus and Keyboard focus are not sync.

Internal bug link: https://microsoft.visualstudio.com/DefaultCollection/OS/_workitems/edit/43361620

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the React Native Gallery app by following the Permissions and Request button steps, then inspect the Permissions screen and Request button focus behavior. Done means keyboard and Narrator focus stay synchronized and Narrator announces the expected Request permission text.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, typescript
Domain
accessibility, mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.