Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switches on Fabric should be Accessible and Focusable by Default #11857

Closed
chiaramooney opened this issue Jul 7, 2023 · 0 comments · Fixed by #13341
Closed

Switches on Fabric should be Accessible and Focusable by Default #11857

chiaramooney opened this issue Jul 7, 2023 · 0 comments · Fixed by #13341

Comments

@chiaramooney
Copy link
Contributor

Problem Description

The Switch control on Fabric is currently not in the UIA tree and not focusable by default. On Paper, the Switch control was in the UIA tree and focusable by default. The behavior of the Switch control should be the same for both architectures.

Steps To Reproduce

  1. Run playground-composition.sln.
  2. Add a Switch control to a sample page.
  3. Observe that the control cannot be tabbed to by default.
  4. Open AccessibilityInsights and see that the switch control is not in the UIA tree.

Expected Results

Switch control should be able to be tabbed to by default. Control should be seen in the UIA tree as a button control.

CLI version

npx react-native -v

Environment

npx react-native info

Target Platform Version

None

Target Device(s)

No response

Visual Studio Version

None

Build Configuration

None

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

No response

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Jul 7, 2023
@chrisglein chrisglein added Area: Accessibility Area: Switch and removed Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) labels Jul 10, 2023
@chrisglein chrisglein added this to the 0.73 milestone Jul 10, 2023
@YajurG YajurG added the Recommend: Backlog Recommend that issue should be given Backlog milestone. label Aug 31, 2023
@chiaramooney chiaramooney removed the Recommend: Backlog Recommend that issue should be given Backlog milestone. label Sep 19, 2023
@marlenecota marlenecota modified the milestones: 0.73, Backlog Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants