RE: Objection to password role

 

From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: 17 June 2016 15:08

“If those who are raising concerns have concrete design changes to suggest that would address their issues, then these should be considered, perhaps for the next version of ARIA. However, I’m not supportive of the argument that this functionality should simply not be supported in ARIA. If people are creating custom password widgets, then surely they need to be made accessible, and currently there is no means besides an input element of informing a screen reader that it shouldn’t, for example, echo the characters typed into a password field.”

Can you point to some custom password fields in the wild, especially where accessibility is broken?

 

I’ve looked back through the discussions on this, and can’t seem to find any concrete examples of the problem we’re trying to fix. The nearest I can find is the discussion on the 31st March call [1].

 

Where is the original proposal for this role and the use cases and/or examples? Assume it must exist somewhere.

 

Léonie.