Skip to content

Conversation

@mbgower
Copy link
Contributor

@mbgower mbgower commented Oct 3, 2025

Closes #246

change ARIA2 from sufficient for 3.3.1 to advisory
add ARIA2 as an advisory for 3.3.2
Revised the language to make it clearer why this technique is advisory.
@netlify
Copy link

netlify bot commented Oct 3, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit fe704cf
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/68e01d00ef9f1300082e672f
😎 Deploy Preview https://deploy-preview-4666--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@baldino-m
Copy link

baldino-m commented Oct 10, 2025

I don't get why, in the first line, "provide" has been replaced with "enhance": if a form field is visually identifiable as required (with an asterisk or whatever) and aria-required is required (pun not intended), then no programmatic information is given, so aria-required does actually provide some.

My understanding is also that, if the accessible name of the field contains some "required" wording, such as "First name (required)", then aria-required is redundant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Moving ARIA2 technique from 3.3.3 and putting in 3.3.2; adding ARIA21 to 3.3.3

3 participants