WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Placeholder and Accessible Name Computation

for

From: Birkir R. Gunnarsson
Date: May 8, 2019 9:08PM

That discussion doesn't make sense to me. They even talk about what
hapens if an element has title, placeholder and a non-empty value
attribute. I thought an input could never have both a visible
placeholder and a value and the placeholder attribute should not be
exposed by a screen reader as the input's accessible name when it is
not visible.
For one thing it creates a major inconsisency between the visible and
screen reader experience, for another, the recommended use of the
placeholder attribute makes it unsuitable for the element's accessible
name, for a third, an input with placeholder only text fails WCAG
3.3.2 (visible label) except in the rare cases where the field is
sufficiently labeled visually by an adjacent control (e.g. a search
input labeled by a search button).
I just don't like where this discussion is going, oh no precious, not
at all, Gollum.


On 5/8/19, glen walker < <EMAIL REMOVED> > wrote:
> That sentence in step D has always bothered me.
>
> "Otherwise, if the current node's native markup provides an attribute (e.g.
> title)"
>
> Why is the TITLE attribute given as an example in step D as a text
> alternative? If you continue through the calculation to step I (eye), you
> finally get to the lonely tooltip attribute, which is also the TITLE
> attribute. So it's a bit confusing on when the TITLE attribute should be
> used. Step D or step I?
> > > > >


--
Work hard. Have fun. Make history.