- From: Joanmarie Diggs <jdiggs@igalia.com>
- Date: Wed, 8 Jun 2016 17:20:31 -0400
- To: Rich Schwerdtfeger <richschwer@gmail.com>
- Cc: Accessible Rich Internet Applications Working Group <public-aria@w3.org>
Hey Rich. The native HTML password input supports readonly, so whatever those use cases are. ;) As for a practical example: An interface for admins to modify the accounts of users, including user passwords. All of the fields are read-only until the admin clicks on the "unlock" button. --joanie On 06/08/2016 04:57 PM, Rich Schwerdtfeger wrote: > What is the use case for having a read only password? > > Rich > > Sent from my iPhone > >> On Jun 7, 2016, at 5:40 PM, Joanmarie Diggs <jdiggs@igalia.com> wrote: >> >> Proposed text: >> >> Authors SHOULD limit the use of the password role to single-line >> elements which are editable. Authors MAY use the password role on >> elements which are not currently editable due to application-specific >> conditions. However, in that instance, authors MUST indicate that the >> element is read only by setting aria-readonly to true or using the >> appropriate native host language attribute. User agents MUST ignore the >> password role when it is applied to elements which are neither editable >> nor explicitly marked as read only. >> >> * https://github.com/w3c/aria/commit/fe849c8c >> * https://rawgit.com/w3c/aria/action-2080/aria/aria.html#password >> >> --joanie >> >> >
Received on Wednesday, 8 June 2016 21:21:13 UTC