From 927ae90c5078edebc68bbdf7e9f22700995da49f Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Fri, 3 Oct 2025 11:32:01 -0700 Subject: [PATCH 1/2] Update understanding.11tydata.js change ARIA2 from sufficient for 3.3.1 to advisory add ARIA2 as an advisory for 3.3.2 --- understanding/understanding.11tydata.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/understanding/understanding.11tydata.js b/understanding/understanding.11tydata.js index fb9e83a3f1..be902b62d0 100644 --- a/understanding/understanding.11tydata.js +++ b/understanding/understanding.11tydata.js @@ -1141,7 +1141,7 @@ export default function (data) { { title: "Situation A: If a form contains fields for which information from the user is mandatory.", - techniques: ["G83", "ARIA2", "ARIA21", "SCR18", "PDF5"], + techniques: ["G83", "ARIA21", "SCR18", "PDF5"], }, { title: @@ -1149,7 +1149,7 @@ export default function (data) { techniques: ["ARIA18", "ARIA19", "ARIA21", "G84", "G85", "SCR18", "SCR32", "PDF22"], }, ], - advisory: ["G139", "G199"], + advisory: ["G139", "G199", "ARIA2"], }, "labels-or-instructions": { @@ -1170,7 +1170,7 @@ export default function (data) { only used when the other techniques cannot be applied to the page. The earlier techniques are preferred because they increase accessibility to a wider user group. `, - advisory: ["G13"], + advisory: ["G13", "ARIA2"], failure: ["F82"], }, From fe704cf05c3ff1cc24f267fd7dd4f2389bfa62ab Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Fri, 3 Oct 2025 11:57:42 -0700 Subject: [PATCH 2/2] Update ARIA2.html Revised the language to make it clearer why this technique is advisory. --- techniques/aria/ARIA2.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/techniques/aria/ARIA2.html b/techniques/aria/ARIA2.html index 19430cc625..81e4876a9d 100644 --- a/techniques/aria/ARIA2.html +++ b/techniques/aria/ARIA2.html @@ -17,12 +17,12 @@

When to Use

Description

-

The objective of this technique is to provide programmatic indication that a form field (which shown through presentation to be required) is mandatory for successful submission of a form.

-

The fact that the element is required is often visually presented (via a text or non-text symbol, or text indicating input is required or color / styling) but this is not programmatically determinable as part of the field's name.

+

The objective of this technique is to enhance programmatic indication that a form field (which is shown through presentation to be required) is mandatory for successful submission of a form.

+

The fact that the element is required is often visually presented (via a text or non-text symbol, or text indicating input is required or color / styling) but this may not be programmatically determinable as part of the field's name.

The WAI-ARIA aria-required property indicates that user input is required before submission. The aria-required property can have values of true or false. For example, if a user must fill in an address field, then aria-required is set to true.

-

Use of aria-required="true" might be beneficial even when an asterisk or other text symbol is programmatically associated with the field as it may reinforce its required property for some assistive technology users.

-

The fact that the element is required is often visually presented (such as a sign or symbol after the control). Using the aria-required property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to ARIA in HTML for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages.

+

This technique is set as advisory for meeting 3.3.2 Labels or Instructions, because use of aria-required="true" alone, without any visual indicator, would not be perceivable to most users.

+

However, when an asterisk or other text symbol is associated with the field, using the aria-required property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to ARIA in HTML for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages.