W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

RE: Remove "placeholder" attribute from HTML and turn it into a CSS feature

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Tue, 30 Apr 2013 10:34:59 -0400
Message-ID: <dfa0bfc7b6e855f16c44f8b21ba6efd1@mail.gmail.com>
To: Ian Yang <ian@invigoreight.com>, w3c-wai-ig@w3.org
> How do disabled people browse the internet if they don't use AT?

To name a few - large text, low resolution, css disabled, different
colors, browser zoom, adapted keyboards, trackballs, joysticks,
non-mainstream browsers, OS features like voice recognition, etc.

Jonathan

-----Original Message-----
From: Ian Yang [mailto:ian@invigoreight.com]
Sent: Tuesday, April 30, 2013 9:29 AM
To: w3c-wai-ig@w3.org
Subject: Re: Remove "placeholder" attribute from HTML and turn it into a
CSS feature

On Tue, Apr 30, 2013 at 8:46 PM, Jonathan Avila
<jon.avila@ssbbartgroup.com> wrote:
> When something is moved from HTML to CSS you are saying that is not
> necessary to understanding the page and it could be removed and the
> content would keep its meaning.  You then indicate people can use
> off-screen labels.  I'm concerned that people with disabilities that
> do not use assistive technology (AT) will run into issues.

>From time to time, I see website designs which use off-screen labels
and placeholders. What's wrong with that?

How do disabled people browse the internet if they don't use AT?


> Examples of Success Criterion 3.3.2
> A field for entering a date contains initial text which indicates the
> correct format for the date.
> http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html

Now that's a valuable point. In that context I'm willing to think
placeholder is helpful.


Kind Regards,
Ian Yang
Received on Tuesday, 30 April 2013 14:35:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:48 UTC