WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Placeholder and Accessible Name Computation

for

From: Steve Green
Date: May 8, 2019 2:38PM

There are documents called "HTML Accessibility API Mappings 1.0" on GitHub and on the W3C website, but their content is different. The latter is called a Working Draft and appears to be the authoritative version at this time (the accessible name computation also aligns with the Accessible Name and Description Computation 1.1). The version on GitHub is called an Editor's Draft and I assume it will become the authoritative version and be migrated to the W3C website at some point.

If I am correct, the "placeholder" attribute is not currently included in the accessible name computation, but it will be in the future.

Steve

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of <EMAIL REMOVED>
Sent: 08 May 2019 21:12
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Placeholder and Accessible Name Computation

Hi All,

According to Scott O'hara, Steve Faulker hasn't comment yet, but the answer is yes it is included as stated in the HTML Accessibility API Mappings 1.0 doc.

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

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Detlev Fischer
Sent: Wednesday, May 8, 2019 3:29 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Placeholder and Accessible Name Computation

I seemed to remember placeholder has been included in the native HTML input name calc https://w3c.github.io/html-aam/#input-type-text-input-type-password-input-type-search-input-type-tel-input-type-url-and-textarea-element <https://w3c.github.io/html-aam/#input-type-text-input-type-password-input-type-search-input-type-tel-input-type-url-and-textarea-element> which @stevefaulkner has just confirmed - while the doc Accessible Name and Description Computation 1.2 https://w3c.github.io/accname/ <https://w3c.github.io/accname/> doesn't list it. So I am not sure why these sources are out of sync and which one should be considered authoritative...

> Am 08.05.2019 um 20:16 schrieb Steve Green < <EMAIL REMOVED> >:
>
> Chrome's browser developer tools contain an Accessibility tab that calculates the accessible name. That can be very helpful when testing convoluted code you didn't write yourself, but the computation appears to contain an error insofar as it uses the "placeholder" attribute.
>
> Bryan Garaventa's tool https://whatsock.github.io/w3c-alternative-text-computation/Editable%20Live%20Input%20AccName%20Test.html does not use the "placeholder" attribute, and since he was an author of the Accessible Name and Description Computation 1.1 I am inclined to trust his implementation rather than Chrome's.
>
> It seems that the computation rules are ambiguous when they say "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, return that alternative in the form of a flat string". Chrome is interpreting the "placeholder" attribute as a text alternative but Bryan's tool isn't.
>
> Any thoughts on this?
>
> Regards,
> Steve Green
> Managing Director
> Test Partners Ltd
> 020 3002 4176 (direct)
> 0800 612 2780 (switchboard)
> 07957 246 276 (mobile)
> 020 7692 5517 (fax)
> Skype: testpartners
> <EMAIL REMOVED>
> www.testpartners.co.uk
>
> Connect to me on LinkedIn - http://uk.linkedin.com/in/stevegreen2
>
> > > archives at http://webaim.org/discussion/archives
>