[wp-trac] [WordPress Trac] #40462: Add placeholders to wp_login_form()

[WordPress Trac]

#40462: Add placeholders to wp_login_form()
------------------------------------+--------------------------------------
 Reporter:  ramiy                   |       Owner:  voldemortensen
     Type:  enhancement             |      Status:  closed
 Priority:  normal                  |   Milestone:
Component:  Login and Registration  |     Version:
 Severity:  normal                  |  Resolution:  wontfix
 Keywords:  has-patch               |     Focuses:  accessibility, template
------------------------------------+--------------------------------------

Comment (by olligranlund):

 I came across this ticket when looking for ways to add placeholder texts
 to the login form. I feel that the original proposal is valid and should
 be implemented. I see WordPress as a very flexible platform for creating
 all kinds of sites and services, but not implementing this feature will
 probably end up with people doing workarounds, which is even worse. If
 someone really wants to use placeholders, there's always a way, but that
 doesn't mean that it should be "hard".

 You can really easily make really bad sites as a WordPress developer from
 a accessibility perspective. You have already full access to the code and
 you can either take accessibility in account or not. As someone who has
 worked in several agencies, there's always a rush with projects and we are
 cutting corners to produce something viable in time. This is one thing
 that slows us down since we need to look for alternative solutions.

 I feel that WordPress should not limit the HTML-syntax with disallowing
 placeholders. If one wants to have the placeholders, they will eventually
 get them in one way or another. For accessibility concerns, we create
 special workarounds so that users with dissabilities can grasp the
 information from websites in a similar way as normal users. Why is it then
 forbidden to help the normal user with a placeholder as a visual hint?

 Sure there is a risk that the labels will be unused in favor of
 placeholder, but that is a decision that the developer has made. That
 decision is also affected in Google SEO and is alerted about in different
 a11y-plugins like Wave or Axe. One using the placeholder attribute should
 know about the downsides if they remove the label and face the
 consequences. People will circumvent this limitation until you let users
 add it in the right way. Who knows, maybe a11y-tools will at some point
 perceive the placeholder values as a good thing, but certainly, it's never
 going to be a negative one alone.

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