[wp-trac] [WordPress Trac] #49608: Implementing HTML 5.2 into the user create and edit forms.

[WordPress Trac]

#49608: Implementing HTML 5.2 into the user create and edit forms.
-------------------------------+--------------------------------
 Reporter:  derweili           |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Users              |     Version:  trunk
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui, accessibility
-------------------------------+--------------------------------
Changes (by afercia):

 * keywords:  2nd-opinion needs-patch => reporter-feedback


Comment:

 This ticket was discussed two weeks ago during the weekly accessibility
 bug-scrub on Slack. Sorry I missed to report some feedback. Here it is :)

 @derweili thanks for your report. While leveraging auto-fill is a
 recommended WCAG technique and addresses [https://www.w3.org/TR/WCAG21
 /#identify-input-purpose Success Criterion 1.3.5 Identify Input Purpose],
 some considerations were made regarding the actual usefulness of
 autocomplete in the context of the various WordPress forms that relate to
 information about the user. We'd like to ask you for more details, when
 you have a chance.

 Going through your points:

 1
 **Login Form**

 Username/Email and Password are already provided by the browsers built-in
 password manager. Not sure autocomplete would help users. Also, I'd tend
 to think password managers are more secure. For example, they provide the
 ability to set a master password.

 2
 **Lost password form**

 Whether users used a username or their email, looks like
 [https://github.com/whatwg/html/issues/4445 the correct value to use is
 autocomplete="username"]. Regardless, not sure it actually works with
 usernames. Quickly testing, I see only Chrome auto-fills using the
 ''email''?

 3
 **Password Reset Form**

 WordPress already fills the new password field with a suggested "strong"
 password. As the field is already "filled" autocomplete doesn't do
 anything. Seems that the autocomplete attribute would actually do
 something only when JavaScript is off. See screenshot attached below,
 where I added `autocomplete="new-password"` for testing purposes.


 4
 **Add new User / Edit User**

 It is unlikely users would save in their browsers data of ''other'' users?
 How autocomplete would help when creating or editing other users?

 5
 **Edit Profile (own profile)**

 This could be one of the few cases where autocomplete would be useful.
 Worth noting that:

 {{{
 - username: cannot be changed
 - nickname: it's prefilled with the username thus preventing autocomplete
 from working
 - email:    it's prefilled with the email used during registration thus
 preventing autocomplete to work
 }}}

 Ultimately, it would work only for the following fields, unless I'm
 missing something:

 {{{
 first name: `given-name `
 last name:  `family-name`
 website:    `url`
 }}}


 6
 **Register form**

 Does this relate to `wp-signup.php` on multisite? Yep, maybe it would be
 useful for the `email` field. Not sure it would work for the username
 field.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49608#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform