Bruce Blaser

@ahmadabdolsaheb Concerning the success feedback, I think we should continue to have an actual congratulations message in addition to the submit button. This is actually related to an accessibility issue...

I think this might be more of a UI/UX issue than an accessibility issue. I suppose you could make an argument that only using a check mark icon to signal...

This particular issue is sort of a thorn in the side of accessibility because HTML doesn't offer a great way to solve it. Setting one of the buttons to `checked`...

> because, without JavaScript, the form would still be submit-able without having any selected Ya, there are some accessibility fixes that basically require JS to implement "properly". But I see...

> None of the options are ever marked by default and yet when the user tries to submit the form without selecting one, it doesn't allow them to. This is...

In addition to @ShaunSHamilton's four steps above, I think we need a fifth step to pull the terms and conditions checkbox out of the fieldset it is currently in. The...

> The three sections doesn't have any heading to them. Sections do not require headings. > The fields are not marked whether they are required or not. This is a...

The more I think about this, I don't think that zoom is actually necessary to demonstrate the second bug. With the default 100% zoom it is still possible to have...

I think PR #46272 would technically be enough to address Bug 1. While the user would not be able to use the arrow keys to scroll down to see the...

PR #46272 did not address Bug 1 sufficiently since the "Ask for Help" and "Reset Step" buttons do not appear until after a certain amount of failed checks.