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

Accessibility: Flyout Automatically Reads All Elements on Open #10303

Open
Yajur-Grover opened this issue Jan 15, 2025 · 0 comments
Open

Accessibility: Flyout Automatically Reads All Elements on Open #10303

Yajur-Grover opened this issue Jan 15, 2025 · 0 comments
Labels
accessibility Narrator, keyboarding, UIA, etc bug Something isn't working

Comments

@Yajur-Grover
Copy link

Describe the bug

Transfer of issue microsoft/react-native-gallery#524 to mirror internal bug logged.

When the Flyout menu is opened in screen reader mode (e.g., Windows Narrator), the screen reader automatically reads out all accessible elements within the Flyout without waiting for user interaction. This behavior can overwhelm users and prevent them from navigating through the menu items at their own pace.

Steps to reproduce the bug

  • Enable a screen reader, such as Windows Narrator.
  • Open the Flyout menu.
  • Observe that the screen reader automatically starts reading all accessible elements in the Flyout sequentially.
  • Note that users cannot interrupt the reading to focus on a specific item or interact with the menu at their own pace.

Expected behavior

  • The screen reader should announce the Flyout as a modal dialog or menu when it opens.
  • Only the first actionable element (e.g., the first menu item or header) should be read out automatically.
  • Users should have control over the navigation and reading of other elements using keyboard or screen reader gestures.

Screenshots

No response

NuGet package version

None

Windows version

No response

Additional context

No response

@Yajur-Grover Yajur-Grover added the bug Something isn't working label Jan 15, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Jan 15, 2025
@karkarl karkarl added accessibility Narrator, keyboarding, UIA, etc and removed needs-triage Issue needs to be triaged by the area owners labels Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Narrator, keyboarding, UIA, etc bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants