W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2016

Re: Placeholder text instead of Labels

From: Mitchell Evan <mtchllvn@gmail.com>
Date: Wed, 16 Mar 2016 00:34:37 +0000
Message-ID: <CAK=xW6vk_uLdJ2DKJyBoyTxk5f7xeHhwKKUGgKWGS3d=ZQq43A@mail.gmail.com>
To: Herin Hentry <hhentry@planittesting.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Yes, "placeholder instead of label" is a failure of WCAG Success Criterion
4.1.2 Name, Role, Value.

These links further describe the problem and solutions:

   - Maxability: Placeholder attribute and Why it is not accessible
   <http://www.maxability.co.in/2016/01/placeholder-attribute-and-why-it-is-not-accessible/>
   - WebAIM Thread: Name, Role, Value and Labels or Instructions techniques
   <http://webaim.org/discussion/mail_thread?thread=6858>

We should also remember to design an inclusive experience for voice control
users. The technical details in this PDF are incomplete, but the use cases
are good:

   - Guidelines For Speech-Accessible HTML for Dragon (PDF)
   <http://www.nuance.com/ucmprod/groups/healthcare/documents/webasset/nd_004979.pdf>

Cheers,
Mitchell Evan

On Tue, Mar 15, 2016 at 3:48 PM Herin Hentry <hhentry@planittesting.com>
wrote:

> Hi,
>
> Using placeholder texts instead of Labels, the screen reader announces the
> placeholder texts. But, then it’s not good for older people and people with
> memory issues.
>
> Will this be accessibility failure?
>
> Thank you,
>
> Herin
>
-- 

Mitchell Evan
mtchllvn@gmail.com
+1 (510) 375-6104
Received on Wednesday, 16 March 2016 00:35:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 16 March 2016 00:35:18 UTC