From 02bbf4b30c45e1b813c2ff61692472685bfdbce5 Mon Sep 17 00:00:00 2001
From: Caren Chang <carenc@google.com>
Date: Wed, 13 Jul 2022 23:27:21 +0000
Subject: [PATCH] Add explanation about the purpose of accessibility heading
 and use case apps should consider.

Change-Id: I01bdd1fc89d54e62e9ce1f8dc15a58d13c56fabc
Test: N/A, documentation chang
---
 core/java/android/view/View.java | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/core/java/android/view/View.java b/core/java/android/view/View.java
index ffa577a47c886..271d7ba9cdd34 100644
--- a/core/java/android/view/View.java
+++ b/core/java/android/view/View.java
@@ -12810,6 +12810,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.
      *