[wp-trac] [WordPress Trac] #33952: get_search_form() accessibility improvements

[WordPress Trac]

#33952: get_search_form() accessibility improvements
---------------------------+--------------------------------
 Reporter:  afercia        |       Owner:
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:  4.3
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  ui, accessibility
---------------------------+--------------------------------

Comment (by GaryJ):

 Replying to [ticket:33952 afercia]:
 > We're also a bit concerned about the usage of the placeholder attribute
 as "visual label" while, according to the specs, its purpose is to give an
 hint about the type of data to enter. In fact, some screen readers
 announce the placeholder as "hint". By the way we understand this would
 require some discussion in the community so let's focus on the redundant
 info for now.

 Relevant: [http://www.nngroup.com/articles/form-design-placeholders/
 Placeholders in Form Fields are Harmful].

 > Additionally, it would be preferable to associate the label explicitly
 using a `for` attribute, this would need a unique identifier but it
 shouldn't be too hard to have a counter or some clever solution in case of
 multiple search forms on the same page.

 One suggestion, originally by @rianrietveld, is `uniq_id()`, easy if used
 in a [https://gist.github.com/GaryJones/a2756ebe6ba340689b13 search form
 class].

 > Side note: there's a space before the ellipsis in the placeholder, not
 sure if that's intentional, doesn't look right to me :)

 British English and US English differ on the opinion for whether there
 should be a space or not before a trailing ellipses.

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