WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Placeholder and Accessible Name Computation

for

From: Steve Green
Date: May 9, 2019 3:18AM

The change log at https://w3c.github.io/html-aam/#a-1-change-log shows that placeholder was removed from the computation in 2016 and reintroduced this year. This change does not yet appear on the W3C website, so I guess it's not official yet, but I don't really understand the status of the GitHub website.

Steve


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: 09 May 2019 00:22
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Placeholder and Accessible Name Computation

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
>
>