E-mail List Archives
Re: Placeholder and Accessible Name Computation
From: Patrick H. Lauke
Date: May 8, 2019 1:50PM
- Next message: joe@a11yeval.com: "Re: Placeholder and Accessible Name Computation"
- Previous message: Steve Green: "Re: Placeholder and Accessible Name Computation"
- Next message in Thread: joe@a11yeval.com: "Re: Placeholder and Accessible Name Computation"
- Previous message in Thread: Steve Green: "Re: Placeholder and Accessible Name Computation"
- View all messages in this Thread
On 08/05/2019 20:34, Jonathan Avila wrote:
> I am generally opposed to the placeholder being used as the accessible name because I believe it will lead to the sole use of it as an accepted way of providing a name rather than a fallback. The placeholder should not act as a label and should act as a hint. By including it in the name it encourages it's acceptance as a label rather than a placeholder. It's called placeholder for a reason and not a label.
For what it's worth, an input relying purely on placeholder will still
fail "Labels and Instructions" (because once filled in there's no more
"label or instruction" there at all) and arguably "Label in Name"
(again, once filled in, it has no apparent label but just its entered
value, and that's not part of the accessible name).
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
- Next message: joe@a11yeval.com: "Re: Placeholder and Accessible Name Computation"
- Previous message: Steve Green: "Re: Placeholder and Accessible Name Computation"
- Next message in Thread: joe@a11yeval.com: "Re: Placeholder and Accessible Name Computation"
- Previous message in Thread: Steve Green: "Re: Placeholder and Accessible Name Computation"
- View all messages in this Thread