diff --git a/docs/next/touchablewithoutfeedback.html b/docs/next/touchablewithoutfeedback.html index 6fb1a4a32c2..eb99f222813 100644 --- a/docs/next/touchablewithoutfeedback.html +++ b/docs/next/touchablewithoutfeedback.html @@ -37,6 +37,8 @@
accessibilityComponentTypeaccessibilityHintaccessibilityLabelaccessibilityRoleaccessibilityStatesaccessibilityTraitsaccessibledelayLongPressaccessibilityComponentType> Note: accessibilityComponentTypewill soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead.
| Type | Required |
|---|
accessibilityRole| Type | Required |
|---|---|
| AccessibilityRoles | No |
accessibilityStates| Type | Required |
|---|---|
| array of AccessibilityStates | No |
accessibilityTraits> Note: accessibilityTraitswill soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead.
| Type | Required |
|---|
accessibilityComponentType> Note: accessibilityComponentTypewill soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead.
| Type | Required |
|---|
accessibilityRole| Type | Required |
|---|---|
| AccessibilityRoles | No |
accessibilityStates| Type | Required |
|---|---|
| array of AccessibilityStates | No |
accessibilityTraits> Note: accessibilityTraitswill soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead.
| Type | Required |
|---|
accessibilityComponentType> Note: accessibilityComponentTypewill soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead.
Indicates to accessibility services to treat UI component like a native one. Works for Android only.
Possible values are one of:
accessibilityRole> Note: AccessibilityRole and AccessibilityStates 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.
Tells the screen reader to treat the currently focused on element as having a specific role.
+Possible values for AccessibilityRole is one of:
'none' - The element has no role.'button' - The element should be treated as a button.'link' - The element should be treated as a link.'header' - The element is a header that divides content into sections.'search' - The element should be treated as a search field.'image' - The element should be treated as an image.'key' - The element should be treated like a keyboard key.'text' - The element should be treated as text.'summary' - The element provides app summary information.'imagebutton' - The element has the role of both an image and also a button.'adjustable' - The element allows adjustment over a range of values.On iOS, these roles map to corresponding Accessibility Traits. Image button has the same functionality as if the trait was set to both 'image' and 'button'. +See the Accessibility guide for more information.
+On Android, these roles have similar functionality on TalkBack as adding Accessibility Traits does on Voiceover in iOS
+| Type | Required |
|---|---|
| AccessibilityRole | No |
accessibilityStates> Note: AccessibilityRole and AccessibilityStates 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.
Tells the screen reader to treat the currently focused on element as being in a specific state.
+You can provide one state, no state, or both states. The states must be passed in through an array. +Ex: ['selected'] or ['selected', 'disabled']
+Possible values for AccessibilityStates are:
'selected' - The element is in a selcted state.'disabled' - The element is in a disabled state.| Type | Required |
|---|---|
| array of AccessibilitStates | No |
accessibilityTraits> Note: accessibilityTraits will soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead.
Provides additional traits to screen reader. By default no traits are provided unless specified otherwise in element.
You can provide one trait or an array of many traits.
Possible values for AccessibilityTraits are:
importantForAccessibilityneedsOffscreenAlphaCompositingrenderToHardwareTextureAndroidaccessibilityRoleaccessibilityStatesaccessibilityTraitsaccessibilityViewIsModalaccessibilityElementsHiddenaccessibilityComponentType> Note: accessibilityComponentTypewill soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead.
Indicates to accessibility services to treat UI component like a native one. Works for Android only.
Possible values are one of:
accessibilityRole> Note: AccessibilityRole and AccessibilityStates 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.
Tells the screen reader to treat the currently focused on element as having a specific role.
+Possible values for AccessibilityRole is one of:
'none' - The element has no role.'button' - The element should be treated as a button.'link' - The element should be treated as a link.'header' - The element is a header that divides content into sections.'search' - The element should be treated as a search field.'image' - The element should be treated as an image.'key' - The element should be treated like a keyboard key.'text' - The element should be treated as text.'summary' - The element provides app summary information.'imagebutton' - The element has the role of both an image and also a button.'adjustable' - The element allows adjustment over a range of values.On iOS, these roles map to corresponding Accessibility Traits. Image button has the same functionality as if the trait was set to both 'image' and 'button'. +See the Accessibility guide for more information.
+On Android, these roles have similar functionality on TalkBack as adding Accessibility Traits does on Voiceover in iOS
+| Type | Required |
|---|---|
| AccessibilityRole | No |
accessibilityStates> Note: AccessibilityRole and AccessibilityStates 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.
Tells the screen reader to treat the currently focused on element as being in a specific state.
+You can provide one state, no state, or both states. The states must be passed in through an array. +Ex: ['selected'] or ['selected', 'disabled']
+Possible values for AccessibilityStates are:
'selected' - The element is in a selcted state.'disabled' - The element is in a disabled state.| Type | Required |
|---|---|
| array of AccessibilitStates | No |
accessibilityTraits> Note: accessibilityTraits will soon be deprecated. When possible, use accessibilityRole and accessibilityStates instead.
Provides additional traits to screen reader. By default no traits are provided unless specified otherwise in element.
You can provide one trait or an array of many traits.
Possible values for AccessibilityTraits are: