[wp-trac] [WordPress Trac] #39909: Make title behaviours consistent across all widgets on first load

WordPress Trac noreply at wordpress.org
Mon Mar 13 22:08:45 UTC 2017


#39909: Make title behaviours consistent across all widgets on first load
-------------------------------------------------+-------------------------
 Reporter:  karmatosed                           |       Owner:
     Type:  enhancement                          |  westonruter
 Priority:  normal                               |      Status:  reopened
Component:  Widgets                              |   Milestone:  4.7.4
 Severity:  normal                               |     Version:  2.8
 Keywords:  has-patch has-screenshots fixed-     |  Resolution:
  major 2nd-opinion a11y-placeholder             |     Focuses:
                                                 |  accessibility
-------------------------------------------------+-------------------------
Changes (by afercia):

 * keywords:  has-patch commit has-screenshots fixed-major => has-patch has-
     screenshots fixed-major 2nd-opinion a11y-placeholder
 * focuses:   => accessibility


Comment:

 We've discussed a bit this change during today's accessibility meeting,
 and we wouldn't recommend to use the placeholder attribute for this
 purpose.

 [https://www.w3.org/TR/html5/forms.html#the-placeholder-attribute
 According to the spec], the placeholder attribute should be used to:
 > represents a short hint (a word or short phrase) intended to aid the
 user with data entry when the control has no value. A hint could be a
 sample value or a brief description of the expected format

 Also, from a usability point of view, this change visually matches the
 placeholder with the widget title shown in the Customzer preview, but in
 the Widget screen doesn't help so much.

 Since we're dealing with the default value, wouldn't be better to populate
 the field with the default value instead of using it as placeholder?

 Adding an `a11y-placeholder` keyword since we're planning to use it for
 other cases related to placeholders.

 Please, for any UI important change or changes to interactive controls,
 form fields, and so on, please always set the "accessibility" focus. 🙂

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


More information about the wp-trac mailing list