E-mail List Archives
Re: Placeholder and Accessible Name Computation
From: glen walker
Date: May 8, 2019 5:21PM
- Next message: glen walker: "Re: Placeholder and Accessible Name Computation"
- Previous message: Detlev Fischer: "Re: Placeholder and Accessible Name Computation"
- Next message in Thread: glen walker: "Re: Placeholder and Accessible Name Computation"
- Previous message in Thread: Detlev Fischer: "Re: Placeholder and Accessible Name Computation"
- View all messages in this Thread
Joe, I think you need to finish the sentence from the spec regarding native
markup.
"Otherwise, if the current node's native markup provides an attribute (e.g.
title) or element (e.g. HTML label) **that defines a text alternative**..."
(emphasis mine)
So, yes, the placeholder attribute is a native markup attribute but it is
not an attribute that defines a text alternative. As several have noted,
it's hint and not a text alternative so shouldn't be included in the name
calculation.
On Wed, May 8, 2019 at 2:12 PM < <EMAIL REMOVED> > wrote:
>
> The Accessible Name and Description Computation 1.2 does not mention it
> specifically, but it mentions " Otherwise, if the current node's native
> markup provides an attribute (e.g. title)" from Step D.
>
> The placeholder attribute is a native HTML attribute for <input> elements.
>
> Thankx,
> Joe Humbert
>
>
- Next message: glen walker: "Re: Placeholder and Accessible Name Computation"
- Previous message: Detlev Fischer: "Re: Placeholder and Accessible Name Computation"
- Next message in Thread: glen walker: "Re: Placeholder and Accessible Name Computation"
- Previous message in Thread: Detlev Fischer: "Re: Placeholder and Accessible Name Computation"
- View all messages in this Thread