Aria2 as advisory technique for 3.3.2 and 3.3.1

[mbgower]

Closes #246

[netlify]

❌ Deploy Preview for wcag2 failed.

Name	Link
🔨 Latest commit	4faa56d
🔍 Latest deploy log	https://app.netlify.com/projects/wcag2/deploys/690910053b78a9000894b850

[baldino-m]

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.

[mbgower]

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.

@baldino-m the technique has been changed from sufficient to advisory for 3.3.1, and it has also been added as advisory for 3.3.2. As such, the technique is intentionally not sufficient for any of these requirements. In that context, changing the preamble from "provide" to "enhance" hopefully makes more sense.

Please have a look at the preview of the updated document, including its unmodified examples, and let us know if all the changes together, provide sufficient context to answer your comments.
https://deploy-preview-4666--wcag2.netlify.app/techniques/aria/aria2

One option could be to make it "provided or enhanced"