Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Add explanation about the purpose of accessibility heading and use case apps should consider." am: 407d531735 am: afc1b7d01e am: 08ae6de00f am: 389bce3764 am: 8bd8e3ee20

Browse Source 
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2151635

Change-Id: I6122eda7c5b6d4ed8d2da361d6cdaa13129ce12c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
Caren Chang
2022-07-19 23:47:28 +00:00
committed by Automerger Merge Worker
parent a73a3f1e9b 8bd8e3ee20
commit 87939a3e08
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
core/java/android/view/View.java
View File

@@ -13323,6 +13323,10 @@ public class View implements Drawable.Callback, KeyEvent.Callback,
/**
* Set if view is a heading for a section of content for accessibility purposes.
* <p>
* Users of some accessibility services can choose to navigate between headings
* instead of between paragraphs, words, etc. Apps that provide headings on
* sections of text can help the text navigation experience.
*
* @param isHeading {@code true} if the view is a heading, {@code false} otherwise.
*