Re: Proposed response to Issue 836

The response contains this line: "In 10 years we've never seen instructions
replacing labels"

​I am concerned our response is using anecdotal information, and question
the value of adding that remark. At a minimum, in 10 years *David* may
never have seen this, but a blanket statement on behalf of the entire WG
is​ going a tad far IMO. I'd prefer the following edit (but not a hill to
die on):

WCAG is generally interpreted to require visible labels as per 3.3.2. Its
true that there is an OR statement in 3.3.2 (labels OR Instructions),
however there is a distinction between Label and Name, which is also
defined in the specification. A Label is presented to ALL users, and
therefore is visible. Anecdotally, most evaluators when queried, have
consistently required visible labels.
label

text or other component with a text alternative that is presented to a user
to identify a component within Web content

Note 1: A label is presented to all users whereas the name may be hidden
and only exposed by assistive technology. In many (but not all) cases the
name and the label are the same.

Note 2: The term label is not limited to the label element in HTML.




JF

On Tue, Apr 3, 2018 at 9:08 PM, Andrew Kirkpatrick <akirkpat@adobe.com>
wrote:

> How does this sound to people?
>
> https://github.com/w3c/wcag21/issues/836#issuecomment-378314671
>
>
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion