E-mail List Archives
Re: Placeholder
From: Yoandry Collazo
Date: Mar 12, 2019 9:14AM
- Next message: Karlen Communications: "Re: Artifacting visual labels in PDF forms"
- Previous message: Philip Kiff: "Re: Artifacting visual labels in PDF forms"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Placeholder"
- Previous message in Thread: Isabel Holdsworth: "Re: Placeholder"
- View all messages in this Thread
Hi, I'm not an expert, I hope this helps you.
1.
Placeholders
According to HTML5 specifications
<https://developer.paciellogroup.com/blog/2011/02/html5-accessibility-chops-the-placeholder-attribute/>,
The placeholder
<https://www.w3.org/TR/html/sec-forms.html#the-placeholder-attribute> attribute
should not be used as an alternative to a label
<https://www.w3.org/TR/html/sec-forms.html#the-label-element>.
Placeholder text disappears when a text box receives focus:
-
For keyboard users, this can be problematic
<http://mentalized.net/journal/2010/08/05/dont_use_placeholder_text_as_labels/>
as they must read ahead of current focus when filling in forms.
-
Users, especially those with memory impairments will not have the text
label available for reference at the same time as filling in a field.
Other issues with placeholders
-
Users may think a text field is already filled in and skip over it. Data
suggests
<http://www.uxmatters.com/mt/archives/2010/03/dont-put-hints-inside-text-boxes-in-web-forms.php>
that this can be an issue.
-
If the placeholder hint text is useful information it should be
available while the user is filling in the field.
On Mon, Mar 11, 2019 at 3:01 PM Eilana Benish < <EMAIL REMOVED> >
wrote:
> hello, my name is Eilana from Israel. Currently, I work with organizations
> required to make their websites accessible in Israel.
>
> We are working on developing a new website.
>
> We have a very serious disagreement about the place-holder as a method to
> label forms fields.
>
> I know that the popular screen reader reads the place holder. But this is
> mey not be accessible to users with cognitive disabilities.
>
> The development team thought otherwise and implemented the place holder.
> When I told them to change to standard labels â I got the answer that using
> the Placeholder is WCAG 2 compliant.
>
> I have also tried to find information on the W3C accessibility resources â
> Without success.
>
> So, is the place holder WCAG 2 compliant
>
> And what the WCAG 2 working group has to say about that topic?
>
>
>
>
>
>
>
>
>
> --
>
> *×××××× ×¨×, ×××× × ×× ×ש, ×××¨×©× × ××ש×ת ש×ר×ת (2200)*
>
> *××××× ×× ×××× ×¤×¨××ק×××: × ××ש×ת ×ש××ש×ת ××× ××¨× × ×××× ××××××ת ××××¢*
>
> *A.D.N: Accessible digital knowledge 2009 â 2019*
>
> *××פ×× 050-7100367 ×××"× ** <EMAIL REMOVED> *
> < <EMAIL REMOVED> >
> *×תר ×××× ××¨× × × ××ש×ת ×ש××ש×ת ××× ××¨× × ×××× ××××××ת ××××¢*
> <https://adn-accesstime.com/2018/12/12/%d7%a9%d7%99%d7%9e%d7%95%d7%a9-%d7%93%d7%a4%d7%95%d7%a1%d7%99%d7%9d-%d7%90%d7%a4%d7%9c%d7%99%d7%9d-%d7%91%d7%90%d7%aa%d7%a8%d7%99-%d7%90%d7%99%d7%a0%d7%98%d7%a8%d7%a0%d7%98/> * â
> **IOS*
> <https://itunes.apple.com/app/id1438649378?fbclid=IwAR2xQt2j9TXnIBdOVz1oY3T0oBPTepgWndQIlruALWr4q7T4gTZ1mUJAmCQ> * â
> **×× ×ר××××*
> <https://play.google.com/store/apps/details?id=com.adn_accesstime.presspadnews&fbclid=IwAR2KslNcOzRqC8zD_Dpr9qI5EvHFjKAQK2-lCwFoMLVgVHw-M34OZIuUTDo>
>
>
> > > > >
- Next message: Karlen Communications: "Re: Artifacting visual labels in PDF forms"
- Previous message: Philip Kiff: "Re: Artifacting visual labels in PDF forms"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Placeholder"
- Previous message in Thread: Isabel Holdsworth: "Re: Placeholder"
- View all messages in this Thread