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
React Native version 0.57 introduced two accessibility properties, accessibilityRole and accessibilityStates, as "replacement" for accessibilityComponentType and accessibilityTraits.
And this is what we have in the docs:
Note: Accessibility Role and Accessibility States are meant to be a cross-platform solution to replace accessibilityTraits and accessibilityComponentType, which will soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead of accessibilityTraits and accessibilityComponentType. https://facebook.github.io/react-native/docs/accessibility
I wonder if it's already right moment to remove those old properties from the codebase, as part of 0.60, or if there's a plan to remove it in some specific version.
React Native version
0.57
introduced two accessibility properties,accessibilityRole
andaccessibilityStates
, as "replacement" foraccessibilityComponentType
andaccessibilityTraits
.And this is what we have in the docs:
I wonder if it's already right moment to remove those old properties from the codebase, as part of
0.60
, or if there's a plan to remove it in some specific version.Would be good to remove those properties, making the accessibility props lean, and also because there's an approved plan to add more roles and states into the new props, which would make those props more useless.
According to this announcement post, Facebook is already using those new methods.
In case it's time to remove it, I can help with it.
cc @cpojer
The text was updated successfully, but these errors were encountered: