Assumptions:

- adding "whitespace via CSS" clause to address review comment #2075 (comment)
- rewording other parts.

Author: dan-tripp-siteimprove

_rules/visible-label-in-accessible-name-2ee8b8.md

@@ -43,9 +43,11 @@ For the target element, the [visible inner text][] is contained within the [acce
 
 ## Assumptions
 
-This rule assumes that the [visible inner text][] is equal to the [label][https://www.w3.org/WAI/WCAG21/Understanding/label-in-name#dfn-label] in most cases (enough cases to be useful) even though "label" is not precisely defined at this point in history.
+This rule assumes that the [visible inner text][] is equal to the [label][https://www.w3.org/WAI/WCAG21/Understanding/label-in-name#dfn-label], even though "label" is not precisely defined at this point in history.
 
-This rule assumes that neither the label nor the [visible inner text][] are rearranged with CSS so that they appear to the user in a different order than they appear in the DOM.
+This rule assumes that the visible label isn't rearranged with CSS so that it appears to the user in a different order than it appears in the DOM.
+
+This rule assumes that the visible label doesn't use CSS to add whitespace where none exists in the DOM.
 
 This rule assumes that for any word which appears in both the accessible name and the visible label, the same spelling and hyphenation is used in both places.  For example: if "non-negative" is used in the accessible name and "nonnegative" is used in the visible label, that would violate this assumption.  Or if "color" is used in the accessible name and "colour" is used in the visible label, that would also violate this assumption.