Skip to content

Aria2 as advisory technique for 3.3.2 and 3.3.1 #4666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Aria2 as advisory technique for 3.3.2 and 3.3.1 #4666

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
927ae90
Update understanding.11tydata.js
mbgower Oct 3, 2025
fe704cf
Update ARIA2.html
mbgower Oct 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions techniques/aria/ARIA2.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,12 +17,12 @@ <h2>When to Use</h2>
</section>
<section id="description">
<h2>Description</h2>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>The WAI-ARIA <code>aria-required</code> property indicates that user input is required before submission. The <code>aria-required</code> property can have values of <code>true</code> or <code>false</code>. For example, if a user must fill in an address field, then <code>aria-required</code> is set to <code>true</code>.</p>
<div class="note">
<p>Use of <code>aria-required="true"</code> might be beneficial even when an asterisk or other text symbol is programmatically associated with the field as it may reinforce its <code>required</code> property for some assistive technology users.</p>
<p>The fact that the element is required is often visually presented (such as a sign or symbol after the control). Using the <code>aria-required</code> 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 <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> 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. </p>
<p>This technique is set as advisory for meeting 3.3.2 Labels or Instructions, because use of <code>aria-required="true"</code> alone, without any visual indicator, would not be perceivable to most users.</p>
<p>However, when an asterisk or other text symbol is associated with the field, using the <code>aria-required</code> 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 <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> 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. </p>
</div>
</section>
<section id="examples">
Expand Down
6 changes: 3 additions & 3 deletions understanding/understanding.11tydata.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1141,15 +1141,15 @@ 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:
"Situation B: If information provided by the user is required to be in a specific data format or of certain values.",
techniques: ["ARIA18", "ARIA19", "ARIA21", "G84", "G85", "SCR18", "SCR32", "PDF22"],
},
],
advisory: ["G139", "G199"],
advisory: ["G139", "G199", "ARIA2"],
},

"labels-or-instructions": {
Expand All @@ -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"],
},

Expand Down