Update Form field has non-empty accessible name [e086e5]: Added secon…

…dary 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 <[email protected]> * Update _rules/form-field-non-empty-accessible-name-e086e5.md Co-authored-by: Jean-Yves Moyen <[email protected]> * Update _rules/form-field-non-empty-accessible-name-e086e5.md Co-authored-by: Kathy Eng <[email protected]> --------- Co-authored-by: Jean-Yves Moyen <[email protected]> Co-authored-by: Kathy Eng <[email protected]>
w3c · Aug 1, 2024 · a293945 · a293945
1 parent 67d33f3
commit a293945
Show file tree

Hide file tree

Showing 3 changed files with 22 additions and 3 deletions.
diff --git a/content-assets/wcag-act-rules/testcases.json b/content-assets/wcag-act-rules/testcases.json
@@ -19543,6 +19543,12 @@
           "failed": "not satisfied",
           "passed": "further testing needed",
           "inapplicable": "further testing needed"
+        },
+        "wcag20:1.3.1": {
+          "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": {
+          "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."
         }
       },
       "expected": "passed",

diff --git a/content/rules/e086e5/proposed.md b/content/rules/e086e5/proposed.md
@@ -9,7 +9,7 @@ github:
 feedbackmail: [email protected]
 footer: |
   <p><strong>Rule Identifier:</strong> e086e5</p>
-  <p><strong>Date:</strong> Updated 25 January 2024</p>
+  <p><strong>Date:</strong> Updated 1 August 2024</p>
   <p><strong>Authors:</strong> <a href="https://github.com/annethyme">Anne Thyme Nørregaard</a>, <a href="https://github.com/brynanders">Bryn Anderson</a>. Contributors: <a href="https://www.w3.org/community/act-r/participants">Participants of the ACT Rules Community Group (CG)</a>.</p>
   <p>This rule was written in the <a href="https://w3.org/community/act-r/">ACT Rules Community Group</a>. It is written as part of the EU-funded <a href="https://www.w3.org/WAI/about/projects/wai-tools/">WAI-Tools Project</a>. Implementations are part of the EU funded <a href="https://www.w3.org/WAI/about/projects/wai-coop/">WAI-CooP Project</a>. It will be reviewed by the Accessibility Guidelines Working Group (<a href="https://www.w3.org/groups/wg/ag">AG WG</a>).</p>
 proposed: true
@@ -20,7 +20,7 @@ rule_meta:
   original_file: form-field-non-empty-accessible-name-e086e5.md
   description: |
     This rule checks that each form field element has a non-empty accessible name.
-  last_modified: 25 January 2024
+  last_modified: 1 August 2024
   scs_tested:
     - handle: Name, Role, Value
       num: 4.1.2
@@ -79,6 +79,17 @@ This rule does not map to [3.3.2 Labels or Instructions](https://www.w3.org/TR/W
   </details></li>
 </ul>
 
+### Secondary Requirements
+
+This rule is related to the following accessibility requirements, but was 
+not designed to test this requirements directly. These 
+[secondary requirements](https://w3c.github.io/wcag-act/act-rules-format.html#secondary-requirements)
+can either be stricter than the rule requires, or may be satisfied in ways 
+not tested by the rule:
+
+- [1.3.1 Info and Relationships (Level A)](https://www.w3.org/TR/WCAG21/#info-and-relationships): 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.
+- [2.5.3 Label in Name (Level A)](https://www.w3.org/TR/WCAG21/#label-in-name): 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
 
 The following aspects are required in using this rule.

diff --git a/wcag-mapping.json b/wcag-mapping.json
@@ -96,7 +96,9 @@
       "title": "Form field has non-empty accessible name",
       "permalink": "/standards-guidelines/act/rules/e086e5/",
       "successCriteria": [
-        "name-role-value"
+        "name-role-value",
+        "info-and-relationships",
+        "label-in-name"
       ],
       "wcagTechniques": [],
       "deprecated": false,