- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Tue, 17 Jun 2014 20:08:11 -0400
- To: David MacDonald <david100@sympatico.ca>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <f75f44d69851750893c9b7d0d2fcde21@mail.gmail.com>
Ø Some say that since the label disappears on input that the author is "hiding" the label, and it is a failure of SC 3.3.2. I would consider this a failure. I am in favor of the forms where once a field contains non-placeholder text a label appears above the field– this would then meet the SC. On a related note, many browser placeholder implementations tend to also fail contrast requirements. In the H65 example there is also a button that labels example #3’s search field – so we are not promoting a technique that only uses the title. The test steps however, don’t also require a visual label – this is likely because this technique is mapped to 1.3.1 and 1.1.1. So in my opinion we should remove the linkage to SC 3.3.2 from this technique as title attributes are not keyboard accessible. In addition, controls and input are listed as exceptions to 1.1.1 – so I’m not sure why SC 1.1.1 is mapped to H65 either. Jonathan *From:* David MacDonald [mailto:david100@sympatico.ca] *Sent:* Tuesday, June 17, 2014 7:54 PM *To:* WCAG *Subject:* Does placeholder text pass 3.3.2, does disappearing text pass? Recently on Twitter there has been lot's of discussion regarding placeholder text as a label. Some say that since the label disappears on input that the author is "hiding" the label, and it is a failure of SC 3.3.2. H65 seems to indicate that there may be situations where it is ok not to have a visible label. "The objective of this technique is to use the title attribute to label form controls when the visual design cannot accommodate the label (for example, if there is no text on the screen that can be identified as a label) or where it might be confusing to display a label. User agents, including assistive technology, can speak the title attribute." Mobile designers are sometimes quite adamant about the saved screen real estate, but it is clearly worse for cognitive folks, and some low vision, and is strongly criticized in usability circles. Let's assume the placeholder text reports to the API. Do we need a failure, or should it pass? Do we need to revise H65? Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html>
Received on Wednesday, 18 June 2014 00:08:47 UTC