W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2014

Re: Placeholder behavior

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Mon, 6 Oct 2014 20:28:18 +0100
Message-ID: <CA+ri+VkwuPFLSGYnFSoo9hz5Zfcv7vp_cSGHrXJZ=MkCDpDANQ@mail.gmail.com>
To: Sailesh Panchang <spanchang02@yahoo.com>
Cc: Web Content Accessibility Guidelines Working Group <w3c-wai-gl@w3.org>
hi sailesh,

although placeholder should not be used as a label it sometimes is. For the
purpose of accessible name calculation in browsers placeholder is used as a
fallback accessible name in accessibility APIs when other names sources are
not provided.

here are some results of browser testing from late last year



HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>

On 6 October 2014 20:08, Sailesh Panchang <spanchang02@yahoo.com> wrote:

> JAWS 14/15 and NVDA  read the placeholder label even after entering text
> into the text field  in Firefox32 and IE11. VoiceOver in Ios 7 does not do
> so.
> So for instance in the following code, the placeholder "Account number:"
> though not visible, is announced by JAWS and NVDA even when some text is
> present in the field.
> <p><input type="text" placeholder="Account Number:" size="7" /></p>
> (Note: There is no text  outside the input element that funtcions  like a
> label).
> NVDA does not read it  when arrowing through the content (i.e. out of
> forms mode) when there's data in the field.
> HTML5 specs clearly states using placeholder as a label poses
> accessibility problems.
> But thought I'll note this interesting behavior with screen readers.
> Sailesh
Received on Monday, 6 October 2014 19:29:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:16 UTC