Re: Firefox Accessibility Inspector reports placeholder attribute as eligible for accessible name

Jon’s right – I should have pointed to 3.3.2 instead of 2.4.6!

Thanks,
AWK

Andrew Kirkpatrick
Head of Accessibility
Adobe

akirkpat@adobe.com
http://twitter.com/awkawk


From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Wednesday, August 8, 2018 at 11:13
To: WCAG <w3c-wai-gl@w3.org>
Subject: RE: Firefox Accessibility Inspector reports placeholder attribute as eligible for accessible name
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Wednesday, August 8, 2018 at 11:12

3.3.2 requires visible labels – but there is no requirement for the visible label to be programmatically associated.  That is you can have a visible label and then separately a programmatic label that says the same thing.  Visible labels can also take the form of other controls such as a “search” button or an icon.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access
jon.avila@levelaccess.com<mailto:jon.avila@levelaccess.com>
703.637.8957 office

Visit us online:
Website<http://www.levelaccess.com/> | Twitter<https://twitter.com/LevelAccessA11y> | Facebook<https://www.facebook.com/LevelAccessA11y/> | LinkedIn<https://www.linkedin.com/company/level-access> | Blog<http://www.levelaccess.com/blog/>

Looking to boost your accessibility knowledge? Check out our free webinars!<https://www.levelaccess.com/compliance-resources/webinars/>

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

From: Newton, Brooks (Legal) [mailto:Brooks.Newton@thomsonreuters.com]
Sent: Wednesday, August 08, 2018 10:41 AM
To: Andrew Kirkpatrick; Schnabel, Stefan; Patrick H. Lauke
Cc: w3c-wai-gl@w3.org
Subject: RE: Firefox Accessibility Inspector reports placeholder attribute as eligible for accessible name

I’d like to know more about this WCAG requirement for visible labels…

I know that there is requirement for programmatically determinable labels, but not sure there is consensus that visible labels for inputs are specifically required as part of what is explicitly stated in WCAG.

Brooks

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Wednesday, August 08, 2018 9:34 AM
To: Schnabel, Stefan <stefan.schnabel@sap.com>; Patrick H. Lauke <redux@splintered.co.uk>
Cc: w3c-wai-gl@w3.org
Subject: Re: Firefox Accessibility Inspector reports placeholder attribute as eligible for accessible name

Should this be exposed by the browser to the accessibility API as "foo" or not, if there's nothing else giving the input a programmatic name?

It should. But it violates WCAG requirement for VISIBLE label for input, so it is an authoring error, too.

For the record, there isn’t enough information to say whether this is a violation of WCAG. This certainly meets 4.1.2 (Name Role Value) but there isn’t enough information to say whether it also meets 2.4.6 (Headings and labels).

AWK