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

Add different heading level announcements for Narrator for different types of Headings #11847

Closed
YajurG opened this issue Jul 6, 2023 · 3 comments · May be fixed by #11885
Closed

Add different heading level announcements for Narrator for different types of Headings #11847

YajurG opened this issue Jul 6, 2023 · 3 comments · May be fixed by #11885

Comments

@YajurG
Copy link
Contributor

YajurG commented Jul 6, 2023

Summary

Currently, there is only support for one type of 'header' announcement within narrator, as the accessibilityLabel prop only takes one type of 'header' property. Because of this, we are announing 'heading, level 2' for any Text component that has accessibilityLabel = 'header'. Ideally, we will have a different heading announcement in Narrator for different types of headings e.g the title of a page would have a different announcement than the sub-headings of sections on the same page.

Motivation

There is currently an issue on Gallery where different header announcements are needed for different types of headings. In the below example, 'Button' would be a different heading announcement from 'A simple button' or 'A colored button'.
image
Currently all headings have the same announcement - 'heading, level 2'.

Basic Example

No response

Open Questions

No response

@YajurG YajurG added enhancement Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) Area: Accessibility labels Jul 6, 2023
@AgneLukoseviciute
Copy link
Contributor

One option would be to add a windows-specific accessibilityLevel: number prop that would allow for customizing the value. This would be aligned with: https://github.com/react-native-community/discussions-and-proposals/blob/fd64774e8161973b87b8f0a27587fa039eb7b43b/proposals/0000-accessibility-apis.md

@chrisglein chrisglein added this to the 0.73 milestone Jul 10, 2023
@chrisglein chrisglein removed the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Jul 10, 2023
@chrisglein
Copy link
Member

Maybe related: #11772
Check in with Andrew about what's done on Paper.

@Yajur-Grover
Copy link
Contributor

This is no longer an accessibility issue, so marking as closed.

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