You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two notes about this from my test with our screen reader user in the past:
the aria-label of the button has to be customizable, otherwise it's another a11y/i18n problem
is it possible that the reveal button could work different depending how it was triggered?
Triggered by mouse: no change needed
Triggered by keyboard: the reveal/un-reveal mechanism should not be triggered by focus change, instead it should only be done manually by another click on the reveal button (Reasoning: screen reader have to change focus from the button to the input field, to read it.. this changes the type to password again and the screen reader can't read the value)
Edit: another idea; instead of changing the behavior depending on the trigger.. could the field value be announced like we did with the a11y announcer in vaadin avatar group?
Motivation
This is a pre-requisite for adding slotted
<input>
support tovaadin-password-field
.Depends on #2189 (needs text-field base class)
Part of #84
Proposed solution
@vaadin/password-field
for a base classvaadin-password-field
test suite, excluding tests covered by@vaadin/field-base
mixins tests.Related a11y issues
Reveal button not keyboard accessible (#120).
The text was updated successfully, but these errors were encountered: