Re: question on 1.10.1

Hi Jeanne,

What do you mean by "form fields"? I think of "controls" as including form fields and all other input elements. (The term "control" is not really defined, although one occurrence links to the entry for "user interface control", which merely says "A component of the user agent user interface <http://jspellman.github.io/UAAG/Implementing-UAAG20/#def-ua-ui> or the content user interface <http://jspellman.github.io/UAAG/Implementing-UAAG20/#def-content-ui>, distinguished as necessary.")

Regarding the suggestion that images may be covered by Guideline 1.1, I don't think they are: 1.1 covers alternative content (e.g. attributes such as "alt" that are normally not rendered), while 1.10.1 is about separate elements that the markup says are explicitly related (e.g. by aria-labelledby, usually where both elements are rendered). If an image is labeled using area-labelledby or by an associated figcaption, those would not be alternative content and thus not covered by 1.1.

     Greg

-------- Original Message --------
Subject: question on 1.10.1
From: Jeanne Spellman <jeanne@w3.org>
To: UAWG <w3c-wai-ua@w3.org>
Date: 8/21/2014 1:10 PM
> I'm working on the substantive changes list since Last Call and spotted this potential problem with the rewording of 1.10.1.  My bad for not looking at this carefully when I got back from vacation.
>
> 1.10.1 Show Related Elements:
>
> The user can access the information from explicitly-defined relationships in the content, including at least the following: (Level AA)
>
>    a. label for a control or image
>    b. caption for a table
>    c. row and column labels for a table cell
>
> Bullet (a) does not include form fields, which I remember as the main use case in 1.10.1. Images would be covered by Guideline 1.1 and it could confuse the issue by also putting it in 1.10.1.
>
>
>
> propose:
> a. label for form field or control
>