Investigate use of different ARIA roles and attributes on password input

[querkmachine]

What

Investigate whether we could enhance the password input component by using:

1. aria-pressed on the toggle button; or
2. role="switch" and aria-checked on the toggle button

This was a late stretch goal that we didn't have time to complete during #4442, though some initial screen reader testing was carried out. See 'testing variants' tab in the testing spreadsheet (internal only).

Why

To see if we can provide more context to assistive technology users about the state of password visibility and the toggle button.

Assumptions

The original contribution passed scrutiny by accessibility specialists and auditors without using these ARIA attributes, so we assume the password input does not require either of these to be considered acceptably accessible.

Making any changes would purely aim to enhance the user experience of screen reader users. We have the option of not making any changes if they don't meaningfully improve anything.

Timebox

1 day(?)

We should review progress after this period of time has elapsed, even if the spike has not been 'completed'

Who is working on this?

Spike lead:

Spike buddy:

Questions to answer

• Do either of these approaches provide a meaningful improvement for screen reader users?
• Are the different approaches well supported by different screen readers?
• Are there any approaches that haven't been considered that may be a better fit?
• Do any of the approaches provide enough additional value to be worth adding to the password input component? If so, which one?

Done when

• Questions have been answered or we have a clearer idea of how to get to our goal
• Findings have been reviewed and agreed with at least one other person
• Findings have been shared, e.g: via a write-up on the ticket, at a show & tell or team meeting