Re: 1.1.1 Non-text content which controls input

On 06/10/2021 10:20, Ms J wrote:
> Hi
> 
> Please can you provide some clarification on 1.1.1 Non-text content 
> which controls input.
> 
> If a <input> has no visible label and no accessible name, I would assume 
> that fails 4.1.2 and 3.3.2 only, but I have just noticed H44 refers to 
> 1.1.1? (ARC Chrome plugin also cites ‘no accessible name’ as 1.1.1.)
> 
> It seems to me that the SC specifically excludes user interface controls 
> as they are specifically covered elsewhere. In what situations would H44 
> apply?

If a control/input uses something like an icon/image, but the latter 
lacks a text alternative and there's no other way that the control/input 
gets an accessible name, it would fail 1.1.1, 3.3.2, and 4.1.2.

For instance, something like

<button>
   <img src="...">
</button>

The reference in H44 to 1.1.1 seems a bit vague to me (noting that some 
of the techniques are quite badly in need of update). I'm 
guessing/hoping that it was mentioned there mainly for situations where 
there's a graphical button/control, and how giving a label to it can 
also satisfy the 1.1.1 requirement of acting as a text alternative for 
the icon/image of the control, something like

<input type="image" src="..." id="foo">
<label for="foo">The label text acting as text alternative</label>

I do hope the intent there wasn't to treat things like native 
checkboxes, radio buttons, etc as "non-text content" in general, as that 
would make this an overly-stuffed SC.

P
-- 
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Wednesday, 6 October 2021 11:14:41 UTC