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
This is a feature request. <Switch /> components do not support the accessibilityLabel prop.
Motivation: I am using the Appium testing framework as it is the preferred framework for integrating with BrowserStack. Appium highly recommends using accessibilityLabel to identify components, allowing developers to fallback on XPath as a last resort.
<android.widget.Switch> has no content-desc property. This property should have the same value as the accessibilityLabel prop.
Expected Results
When viewed in Appium or another app view source explorer, the <android.widget.Switch> node in the rendered tree will have a content-desc="test" (see the ViewGroup for reference). The correct corresponding property will be set on iOS.
Snack, code example, screenshot, or link to a repository:
Description
This is a feature request.
<Switch />
components do not support theaccessibilityLabel
prop.Motivation: I am using the Appium testing framework as it is the preferred framework for integrating with BrowserStack. Appium highly recommends using
accessibilityLabel
to identify components, allowing developers to fallback on XPath as a last resort.React Native version:
I am currently using
react-native@0.62.1
but looking at the online docs for<Switch />
I see that the prop is still not supported in latest (0.63).Steps To Reproduce
<Switch accessibilityLabel="test" />
<android.widget.Switch>
has nocontent-desc
property. This property should have the same value as theaccessibilityLabel
prop.Expected Results
When viewed in Appium or another app view source explorer, the
<android.widget.Switch>
node in the rendered tree will have acontent-desc="test"
(see the ViewGroup for reference). The correct corresponding property will be set on iOS.Snack, code example, screenshot, or link to a repository:
The text was updated successfully, but these errors were encountered: