feat: [#186324885] agent information checkbox missing proper notifica…

[adidner]

…tion

Description

We have a checkbox on step 3 of formation that locks some fields and pre populates them. This isn't announced and should be instead moving forward.

Ticket

This pull request resolves #186324885.

Approach

Steps to Test

Go to step 3 of formation, turn on screen reader cmd + F5

Navigate to the checkbox,

Check it,

See that it announces additional context regarding what happened

Notes

This was a whole mess and a half.

We wanted to announce the change and I was super on the fence about just trying to have context visible on the page be enough vs announcing and leaving that aria live region on the page to then later be discovered and having that aria-live region disappear after a few seconds so as to not confuse a screen reader user when they returned.

I went with the second option and I think in our case it is quite clear but I still don't love it and am not 100% confident I've made best decision.

At a minimum I did do research, and consulted a number of people so I think I've done the best I could with the context available to me at the moment.

(The change text is discoverable and divides the UX of the page for screen reader users in that their note block changes to be the alert message whereas a sighted user doesn't have this experience, I think this is reasonable and clear if not a little less than idea in that it's a bit complex and dividing UX is not a great practice. )

Code author checklist

• [X] I have rebased this branch from the latest main branch
• [X] I have performed a self-review of my code
• [X] I have created and/or updated relevant documentation on the engineering documentation website
• [X] I have not used any relative imports
• [X] I have pruned any instances of unused code
• [X] I have not added any markdown to labels, titles and button text in config
• [X] If I added/updated any values in userData (including profileData, formationData etc), then I added a new migration file
• [X] I have checked for and removed instances of unused config from CMS
• [X] If I added any new collections to the CMS config, then I updated the search tool and cmsCollections.ts (see CMS Additions in Engineering Reference/FAQ on the engineering documentation site)
• [X] I have updated relevant .env values in both .env-template and in Bitwarden

[adidner]

LGTM! I think you should do a show and tell on this, it can help us include these notifications in the initial iteration instead of going back to it. Good job, Aaron! good to merge after fixing the failing integration tests

A good suggestion, I think that would be great to talk about aria-live and making sure dynamic changes are announced.

Although to be completely honest I'm not as confident as I'd like to be that this is 100% the best way to do this. This is kind of an area where the guidelines haven't really fully caught up to how normal apps work and I'm not sure I understand edge cases well enough to advise on general best practices.

I do want to learn and perhaps I'll consult an expert as digging hasn't gotten me much further recently