E-mail List Archives
Re: Placeholder and Accessible Name Computation
From: Birkir R. Gunnarsson
Date: May 14, 2019 1:10PM
- Next message: chagnon@pubcom.com: "Re: [WebAim] Whither /TOC and /TOCI in PDF 2.0? PDF accessibility question."
- Previous message: Karlen Communications: "Whither /TOC and /TOCI in PDF 2.0? PDF accessibility question."
- Next message in Thread: None
- Previous message in Thread: Mallory: "Re: Placeholder and Accessible Name Computation"
- View all messages in this Thread
Typically placeholder text with proper color contrast looks like
actual input. That creates significant usability issues because people
think they've already filled in the field or that the webpage has
filled it in for them.
This is one of the primary reasons placeholder is widely discouraged
On 5/14/19, Mallory < <EMAIL REMOVED> > wrote:
> I can't hover most touchscreens (luckily I can on this laptop).
>
> On Tue, May 14, 2019, at 4:09 PM, Jim Homme wrote:
>> Hi,
>> It is possible to use the :hover pseudo class to bring the contrast of
>> the placeholder into the right contrast range. Also, if you are helping
>> your client conform to WCAG 2.1, you need to deal with the Label In
>> Name success criterion.
>>
>> Thanks.
>>
>> Jim
>>
>>
>>
>> ==========
>> Jim Homme
>> Digital Accessibility
>> Bender Consulting Services
>> 412-787-8567
>> https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> > > > >
--
Work hard. Have fun. Make history.
- Next message: chagnon@pubcom.com: "Re: [WebAim] Whither /TOC and /TOCI in PDF 2.0? PDF accessibility question."
- Previous message: Karlen Communications: "Whither /TOC and /TOCI in PDF 2.0? PDF accessibility question."
- Next message in Thread: None
- Previous message in Thread: Mallory: "Re: Placeholder and Accessible Name Computation"
- View all messages in this Thread