Update Form field has non-empty accessible name [e086e5]: Added secondary requirements for 1.3.1 and 2.5.3 (#2188)

* Added secondary requirements

* Update _rules/form-field-non-empty-accessible-name-e086e5.md

Co-authored-by: Jean-Yves Moyen <jym@siteimprove.com>

* Update _rules/form-field-non-empty-accessible-name-e086e5.md

Co-authored-by: Jean-Yves Moyen <jym@siteimprove.com>

* Update _rules/form-field-non-empty-accessible-name-e086e5.md

Co-authored-by: Kathy Eng <kengdoj@users.noreply.github.com>

---------

Co-authored-by: Jean-Yves Moyen <jym@siteimprove.com>
Co-authored-by: Kathy Eng <kengdoj@users.noreply.github.com>

Author: 3 people

_rules/form-field-non-empty-accessible-name-e086e5.md

@@ -10,6 +10,10 @@ accessibility_requirements:
     failed: not satisfied
     passed: further testing needed
     inapplicable: further testing needed
+  wcag20:1.3.1: # Info and Relationships (A)
+    secondary: This success criterion is **more strict** than this rule. This is because 1.3.1 Info and Relationship requires that information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text, while 4.1.2 Name, Role, Value only requires an accessible name.
+  wcag20:2.5.3: # Label in Name (A)
+    secondary: This success criterion is **more strict** than this rule. This is because 2.5.3 Label in Name requires that if a label is visible, the accessible name contains the label that is presented visually, while 4.1.2 Name, Role, Value only requires an accessible name.
 input_aspects:
   - Accessibility Tree
   - CSS styling