🤓 For SC 3.3.2: Does every input field need a persistent visual label?

#WCAG #accessibility #nerdVana

https://github.com/w3c/wcag/issues/4088

Clarification on 3.3.2: Does every input field need a persistent visual label? · Issue #4088 · w3c/wcag

For SC 3.3.2: Does every input field need a persistent visual label? What about cases where a input field is used in a particular context, which might not be a form? For example the WYSIWYG Text Ed...

GitHub

To paraphrase Crass:

'Course they fucking do.

@SteveFaulkner

@SteveFaulkner I would say: visual, yes; persistent, no.
@SteveFaulkner Ok, and now that I've seen the issue, I would say that "label" is anything that visually (or by other means for non-sighted users)clarifies the purpose of a control, so for a chat field the visual presentation acts as a label even if there is no visual "text label"

@SteveFaulkner This is an issue that has been rearing its' ugly head in our product recently — ie. having a search field with an icon (magnifying glass) and relying on that as the visual label. Or having a button right next to it with the word "Search". I also would argue that whether someone would mark that as a violation is very much a subjective call.

(and just to be clear: I personally prefer a visual, text-based label near ALL input fields, so not arguing against that)

@therealkimblim

"I also would argue that whether someone would mark that as a violation is very much a subjective call."

agreed