diff --git a/html-aam/html-aam.html b/html-aam/html-aam.html
index 49d3559c3..39d30c7d2 100644
--- a/html-aam/html-aam.html
+++ b/html-aam/html-aam.html
@@ -166,8 +166,22 @@
HTML Element Role Mappings
HTML elements with default WAI-ARIA role semantics must be mapped to platform accessibility APIs according to those WAI-ARIA roles' mappings as defined in the Core Accessibility API Mappings [[!CORE-AAM]] specification.
A '?' in a cell indicates the data has yet to be provided.
"Not mapped" (Not Applicable) means the element does not need to be exposed via an accessibility API. This is usually because the element is not displayed as part of the user interface.
- User agents should return a user-presentable, localized string value for the Mac Accessibility AXRoleDescription.
- All elements having an accessible object in IAccessible2 mapping are supposed to implement IAccessible, IAccessible2 and IAccessible2_2 interfaces.
+ IAccessible2:
+
+ - All elements with accessible objects should implement the IAccessible, IAccessible2 and IAccessible2_2 interfaces.
+
+
+ UIA:
+
+ - When a labelable element is referenced by a
label
element's for
attribute, or a descendant of a label
element, the labelable element's UIA LabeledBy
property points to the UIA element for the label
element.
+ - Elements mapped to the
Text
Control Type are not generally represented as accessible objects in the accessibility tree, but are just part of the Text
Control Pattern implemented for the whole HTML document. However, if they have any aria-
attributes or an explict tabindex
specified, elements mapped to the Text
Control Type will be represented as accessible objects in the accessibility tree.
+
+
+ AXAPI:
+
+ - User agents should return a user-presentable, localized string value for the Mac Accessibility AXRoleDescription.
+
+