diff --git a/comments/2.5.3.md b/comments/2.5.3.md
index e97b0ee..73b592e 100644
--- a/comments/2.5.3.md
+++ b/comments/2.5.3.md
@@ -6,3 +6,11 @@
[wcag2ict:applying-sc-2-5-3-label-in-name-to-non-web-documents-and-software]
This applies directly as written, and as described in Intent from [Understanding Success Criterion 2.5.3](https://www.w3.org/WAI/WCAG22/Understanding/label-in-name#intent).
+
+**2.5.3 Label in Name:** For [user interface components](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components) with [labels](https://www.w3.org/TR/WCAG22/#dfn-labels) that include [text](https://www.w3.org/TR/WCAG22/#dfn-text) or [images of text](https://www.w3.org/TR/WCAG22/#dfn-images-of-text), the [name](https://www.w3.org/TR/WCAG22/#dfn-name) contains the text that is presented visually.
+
+[note:A best practice is to have the text of the label at the start of the name. This is particularly important for voice control users who rely on speaking the visible text to interact with user interface components.]
+
+[note:Some user interface components such as tiles, cards, or list items may include multiple text components. The text that serves as the primary label must be contained in the name. Other visible text components may be exposed through other accessibility properties.]
+
+[note:Custom accessibility actions that group multiple functions may use descriptive names like "actions available" for assistive technologies.]
diff --git a/index.html b/index.html
index b56bc7a..6a6d909 100644
--- a/index.html
+++ b/index.html
@@ -3170,6 +3170,12 @@ Success Criterion 2.5.3 Label in Name
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.3.
+
+
+
When user interface components have nested controls, the name should include the primary visible label but is not required to contain all presented text.
+
+