Skip to content

Revise accessibility actions and label field description#5035

Open
aryanchoudharypro wants to merge 2 commits intofacebook:mainfrom
aryanchoudharypro:patch-1
Open

Revise accessibility actions and label field description#5035
aryanchoudharypro wants to merge 2 commits intofacebook:mainfrom
aryanchoudharypro:patch-1

Conversation

@aryanchoudharypro
Copy link
Copy Markdown

PR Description

Summary

This PR modernizes the accessibilityActions documentation by correcting outdated Android TalkBack interaction patterns and clarifying the functionality of the label field for standard actions.

The Problem

  1. Outdated Gestures (TalkBack 9.1+):** The current documentation incorrectly states that Android users must use physical volume buttons to trigger increment and decrement actions. This behavior was replaced by the "Adjust Reading Control" vertical swipe gestures in TalkBack 9.1 (released in early 2021). The legacy behavior is nearly five years out of date.
  2. Misleading label Documentation: The docs previously claimed the label field for standard actions is "generally unused." This is incorrect; TalkBack uses this field to override the default "Double tap to activate" hint with a custom, context-specific description (e.g., "Double tap to open chat").

The Fix

  • Updated increment/decrement: Reflected the shift from hardware volume keys to vertical swipe gestures for TalkBack 9.1 and later, while maintaining the historical context for older versions.
  • Clarified label Usage: Revised the description to explain how the label field is utilized by assistive technologies to provide specific action results to the user, particularly in overriding the default activation hint.

Updated accessibility actions for iOS and Android to reflect changes in TalkBack versions and improved clarity on the 'label' field usage.
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Apr 3, 2026

Hi @aryanchoudharypro!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@netlify
Copy link
Copy Markdown

netlify bot commented Apr 3, 2026

Deploy Preview for react-native ready!

Name Link
🔨 Latest commit ceaf6ce
🔍 Latest deploy log https://app.netlify.com/projects/react-native/deploys/69d2a27c56eab400082e1343
😎 Deploy Preview https://deploy-preview-5035--react-native.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@meta-cla meta-cla bot added the CLA Signed label Apr 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant