You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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'.
Currently all headings have the same announcement - 'heading, level 2'.
Basic Example
No response
Open Questions
No response
The text was updated successfully, but these errors were encountered:
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 hasaccessibilityLabel = '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'.
Currently all headings have the same announcement - 'heading, level 2'.
Basic Example
No response
Open Questions
No response
The text was updated successfully, but these errors were encountered: