[core-aam]: add Android to sections 1.1 and 1.2.

Author: dtsengchromium

core-aam/index.html

@@ -250,6 +250,7 @@ <h3>Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></
           <li><cite>User Interface Automation</cite> [[UI-AUTOMATION]]</li>
           <li><cite>ATK - Accessibility Toolkit</cite> [[ATK]] and <cite>Assistive Technology Service Provider Interface</cite> [[AT-SPI]], referred to hereafter as "ATK/AT-SPI"</li>
           <li><cite>macOS Accessibility Protocol</cite> [[AXAPI]]</li>
+          <li><cite>Android</cite> [[AccessibilityNodeInfo]]</li>
         </ul>
         <p>
           The <cite><a href="http://www.w3.org/TR/wai-aria-implementation/">WAI-ARIA 1.0 User Agent Implementation Guide</a></cite> included mappings for [[UIA-EXPRESS]], also known as IAccessibleEx,
@@ -332,6 +333,15 @@ <h5>UIA (UI Automation)</h5>
             or cached values using conventions described above, depending on specific needs and coding style conventions.
           </p>
         </section>
+        <section>
+          <h5>Android Accessibility API</h5>
+          <p>
+            Android accessibility services and applications both express user interface elements as a tree of <code>AccessibilityNodeInfo</code> objects. Accessibility services receive events, traverse the <code>AccessibilityNodeInfo</code> tree, retrieve properties, and perform actions on a node. Conversely, Android applications build the <code>AccessibilityNodeInfo</code> tree indirectly by constructing views or composables, or directly via an <code>AccessibilityNodeProvider</code>. They then subsequently fire events, and handle actions.
+          </p>
+          <p>
+            For WAI-ARIA implementers, of particular interest is the mapping into properties, actions, and events on <code>AccessibilityNodeInfo</code> and <code>AccessibilityEvent</code>.
+          </p>
+        </section>
         <section>
           <h5>Accessible Names and Descriptions</h5>
           <p>
@@ -357,6 +367,7 @@ <h5>Accessible Names and Descriptions</h5>
             <a class="state-reference" href="#aria-description"><code>aria-description</code></a> or <a class="state-reference" href="#aria-describedby"><code>aria-describedby</code></a
             >, should be exposed in the <code>accessibilityCustomContent</code> API. Otherwise, it should be exposed as <code>AXHelp</code>.
           </p>
+          <p>In Android, accessible names map to a number of properties defined on <code>AccessibilityNodeInfo</code> such as content description, supplemental description, and text.</p>
           <p>For more detail, see the <a class="accname" href="">Accessible Name and Description Computation</a> specification.</p>
         </section>
       </section>