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 21:58:59 +0100
Message-ID: <CA+ri+Vko3EF8FuVOfYhZ41LKOQKnb7y3kHrpwGwWL-aOr3N_ZA@mail.gmail.com>
To: Jonathan Avila <jon.avila@ssbbartgroup.com>
Cc: Sailesh Panchang <spanchang02@yahoo.com>, Web Content Accessibility Guidelines Working Group <w3c-wai-gl@w3.org>
sure, use of placeholder alone is problematic for a number of reasons.
that's why I put the following in the HTML spec[1]:

Use of the placeholder attribute as a replacement for a label can reduce
> the accessibility and usability of the control for a range of users
> including older users and users with cognitive, mobility, fine motor skill
> or vision impairments. While the hint given by the control's label is shown
> at all times, the short hint given in the placeholder attribute is only
> shown before the user enters a value. Furthermore, placeholder text may be
> mistaken for a pre-filled value, and as commonly implemented the default
> color of the placeholder text provides insufficient contrast and the lack
> of a separate visible label reduces the size of the hit region available
> for setting focus on the control.


[1]
http://www.w3.org/html/wg/drafts/html/master/forms.html#the-placeholder-attribute


--

Regards

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

On 6 October 2014 21:16, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote:

>  Use of placeholder without other visual label also raises concerns under
> SC.  3.3.2 in my opinion.
>
>  Jon
>
>
> On Oct 6, 2014, at 3:30 PM, Steve Faulkner <faulkner.steve@gmail.com>
> wrote:
>
>   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
> http://www.html5accessibility.com/tests/placeholder-labelling.html
>
>   --
>
> Regards
>
> SteveF
>  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 21:00:06 UTC

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