- From: Andrew Kirkpatrick <akirkpat@adobe.com>
- Date: Tue, 8 Dec 2015 18:06:59 +0000
- To: John Foliot <john.foliot@deque.com>, "'Makoto UEKI - Infoaxia, Inc.'" <makoto.ueki@gmail.com>
- CC: 'WCAG' <w3c-wai-gl@w3.org>, 'Sailesh Panchang' <sailesh.panchang@deque.com>, 'Steve Faulkner' <faulkner.steve@gmail.com>, 'Paul Adam' <paul.adam@deque.com>, "josh@interaccess.ie" <josh@interaccess.ie>, 'Detlev Fischer' <detlev.fischer@testkreis.de>, "'David MacDonald'" <david100@sympatico.ca>, "jon.avila@ssbbartgroup.com" <jon.avila@ssbbartgroup.com>
>... etc. As for the onscreen text and the aria-label string being identical: I believe this should be true, but it is currently unclear in WCAG whether or not this is an actual requirement. It is, I think, something that the WG should take up separately, as has been suggested elsewhere. I am wary of requiring that these be identical and am suggesting that people consider “equivalent”. In technique H65 (http://www.w3.org/WAI/GL/WCAG20-TECHS/H65.html) there are some examples where you meet 1.3.1/3.3.2/4.1.2 and the title doesn’t match the label and it is very difficult because the “label” is interpreted from additional information on the page so it is difficult to match exactly. In example 2 (“phone number” as the fieldset legend but with 3 small text inputs) each section has a title with additional information that references the legend but provides the additional information that is needed. I don’t think that anyone is saying that this isn’t ok, but I have to wonder whether people would say that this example actually fails 3.3.2 because there isn’t a label or if it fails 1.3.1 because the title attribute doesn’t match the legend that is used as the label. I believe that the “label” for this example comes from the legend text and the fact that there are 3 adjacent inputs that would be clear and familiar to any north american user, and the title is doing an adequate job of providing equivalent but not identical information. AWK
Received on Tuesday, 8 December 2015 18:07:30 UTC