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
announceForAccessibility is effectively an escape hatch for developers to tell the system screen reader to read out some piece of information. On android, this depends on announceForAccessibility, which is deprecated.
Should react native deprecate this method as well, or should the Android implementation change to use a live region to generate the same effect (similar to usage of aria-live on the web for announcers like the NextJS route announcer)?
I can see arguments for either. There are good reasons to deprecate the method entirely, mainly that there is foot-gun potential to directly sending announcements through the screen reader and instead things like accessibilityState and live regions should be used. On the other hand, it has legitimate uses as a stop-gap for when real system functionality impacts users in negative ways, such as the use in react native itself to announce unselections of views.
There may be other options as well, like expanding the accessibility props to allow for communicating error states.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
announceForAccessibility
is effectively an escape hatch for developers to tell the system screen reader to read out some piece of information. On android, this depends onannounceForAccessibility
, which is deprecated.Should react native deprecate this method as well, or should the Android implementation change to use a live region to generate the same effect (similar to usage of
aria-live
on the web for announcers like the NextJS route announcer)?I can see arguments for either. There are good reasons to deprecate the method entirely, mainly that there is foot-gun potential to directly sending announcements through the screen reader and instead things like accessibilityState and live regions should be used. On the other hand, it has legitimate uses as a stop-gap for when real system functionality impacts users in negative ways, such as the use in react native itself to announce unselections of views.
There may be other options as well, like expanding the accessibility props to allow for communicating error states.
Beta Was this translation helpful? Give feedback.
All reactions