WordPress.org

Make WordPress Core

Changes between Initial Version and Version 9 of Ticket #40331


Ignore:
Timestamp:
02/16/2019 11:53:20 AM (2 years ago)
Author:
afercia
Comment:

Update: in the latest HTML Accessibility API Mappings Editor's Draft (14 February 2019), the use of HTML placeholder attribute content as a fallback source of accessible name has been updated to reflect browser implementations. This point, previously removed, has been reintroduced:

  1. Otherwise if the control has a placeholder attribute, use its value to provide an accessible name.

Still a draft though, pending final approval.

References:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #40331

    • Property Milestone changed from Awaiting Review to Future Release
  • Ticket #40331 – Description

    initial v9  
    1212In the accessibility team we've discussed this issue a few times, and we'd like to propose to make an effort to change the current approach when using placeholders. Basically, the only use case when a placeholder used as a visual label can be considered acceptable, is when there's just one, simple, form field and its purpose is made very clear by the context. For example, a search field.
    1313
    14 [https://make.wordpress.org/core/handbook/best-practices/coding-standards/accessibility-coding-standards/ WordPress aims to be as much accessible as possible], I'd say a good first step would be striving to conform to the WCAG and HTML5 specifications. One more good step would be avoiding to introduce new cases where the placeholder attribute is misused 🙂 .
     14[https://make.wordpress.org/core/handbook/best-practices/coding-standards/accessibility-coding-standards/ WordPress aims to be as much accessible as possible], I'd say a good first step would be striving to conform to the WCAG and HTML5 specifications. One more good step would be avoiding to introduce new cases where the placeholder attribute is misused .
    1515
    1616There are lots of resources online about the placeholder issue, so I'd prefer to keep this ticket description short and refer to them, starting with what the HTML5 specification says: