[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 richardkentgates):

 Replying to [comment:45 afercia]:
 > @richardkentgates that's not really the point being discussed here :)
 Placeholders are supported by assistive technologies. The real point is
 that the proposed usage is against the specification and harmful for
 usability and accessibility. So far, there are no valid use cases.

 The intended use IS the use case. I don't understand the insistence that
 there are no valid uses for this.

 I'll give you the use case I come across at least once a week...

 Users enter (555) 555-5555 but the form is only designed to use
 555-555-5555. Or so.and.so at mail.com when the form only accepts
 soandso at mail.com. Mc'Deal when it will only accept McDeal.

 This assistance, or "hinting" or "additional information" is the intended
 purpose. That's why it's called a placeholder. It holds the place of
 actual data entry, by example.

 I work with seniors every day that cannot understand why forms fail/error
 and the errors that report aren't always clear enough to help, if any
 errors actually report aside from a red border. As it is now, tomorrow, I
 have to drive 45 minutes to Milton Fl so I can help a client get their CPA
 logged in because they just can't figure ot out.

 I think there is a lack of understanding here about how confusing the web
 still remains for some segments of the population. I don't agree with
 ignoring those users because a hanful of people have poor practices. Any
 and all aditional information to users is a good thing, even if some
 developers/designers choose to break their own websites.

 > WordPress shouldn't encourage bad accessibility practices. For this
 reason, I'd propose to close this ticket as "wontfix", also considering
 there's a pending effort to review all the placeholders used in core, see
 #40331.

 I think the logic behind the decision here is flawed. If this really is
 about accecibility and proper use, than maybe the solution should be for
 WP to manage the placeholder text based on predetermined criteria, rather
 than just tossing it out completely.


 This is pretty much all I can say about this.

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