From 9c31a5ad67c818d6ce7eb3eef4a7ca8ee752ff51 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Tue, 21 Apr 2020 12:50:07 +0000 Subject: [PATCH] Deploy website Deploy website version based on 95447533459f466daf15e6a804775f3871faec19 --- docs/next/accessibility.html | 10 +++++----- docs/next/accessibility/index.html | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/next/accessibility.html b/docs/next/accessibility.html index 0d9ae4cdc6c..a6cc27ad7ae 100644 --- a/docs/next/accessibility.html +++ b/docs/next/accessibility.html @@ -187,7 +187,7 @@

onAccessibilityEscape (iOS)

Assign this property to a custom function which will be called when someone performs the "escape" gesture, which is a two finger Z shaped gesture. An escape function should move back hierarchically in the user interface. This can mean moving up or back in a navigation hierarchy or dismissing a modal user interface. If the selected element does not have an onAccessibilityEscape function, the system will attempt to traverse up the view hierarchy until it finds a view that does or bonk to indicate it was unable to find one.

accessibilityLiveRegion (Android)

-

When components dynamically change, we want TalkBack to alert the end user. This is made possible by the ‘accessibilityLiveRegion’ property. It can be set to ‘none’, ‘polite’ and ‘assertive’:

+

When components dynamically change, we want TalkBack to alert the end user. This is made possible by the accessibilityLiveRegion property. It can be set to none, polite and assertive: