add aria-invalid when fields are invalid

[kintner]

What are you trying to accomplish?

During an accessibly review of https://github.com/github/github/pull/283228 it was noted that when we add the invalid attribute to an input element we should also be adding the aria-invalid attribute.

Integration

N/A

Risk Assessment

• Low risk the change is small, highly observable, and easily rolled back.
• Medium risk changes that are isolated, reduced in scope or could impact few users. The change will not impact library availability.
• High risk changes are those that could impact customers and SLOs, low or no test coverage, low observability, or slow to rollback.

What approach did you choose and why?

I modified Primer::Forms::Dsl::Input to include aria-invalid as needed.

Anything you want to highlight for special attention from reviewers?

Are there other places I should be adding tests for this?

Accessibility

• No new axe scan violation - This change does not introduce any new axe scan violations.

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Lookbook)
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

[changeset-bot]

🦋 Changeset detected

Latest commit: afda32b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/view-components	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[camertron]

Cool, thanks!