- From: Detlev Fischer <detlev.fischer@testkreis.de>
- Date: Sun, 22 Nov 2015 12:41:16 +0100
- To: Andrew Kirkpatrick <akirkpat@adobe.com>
- Cc: WCAG <w3c-wai-gl@w3.org>
I responded on Github.H ere is what I wrote: " I think that in cases where individual labels are used next to checkboxes or radio buttons, they constitute a part of the respective control. That's why I think it is fair to mandate an explicit association for those cases to aid the many users with motor impairments that find it hard to place a mouse click on the control itself. I would allow for exceptions only in cases where the design does not allow for sufficient space for individual visible labels, as in the case of checkboxes placed within tables. Here, the title attribute, aria-label attribute of some accessibility`supported programmatic association with table headers via aria-labelledby can be used. So like Adam, I think it fair to define a failure for cases where the label is adjacent to the control but authors have failed to make the connection programmatically determinable. " I'd add that the minimal requirement expressed in the proposed consensus focuses unduly on the needs of screen reader users for whom markup would work either way. From the perspective of the many visually impaired and motor-impaired users, having clickable visual labels is to something I would not be shy to mandate. It's very easily done natively and has been good practice for many years. On 21 Nov 2015, at 20:34, Andrew Kirkpatrick <akirkpat@adobe.com> wrote: > https://github.com/w3c/wcag/issues/122#issuecomment-158676010 -- Detlev Fischer testkreis - das Accessibility-Team von feld.wald.wiese c/o feld.wald.wiese Thedestraße 2 22767 Hamburg Mobil +49 (0)157 57 57 57 45 Fax +49 (0)40 439 10 68-5 http://www.testkreis.de Beratung, Tests und Schulungen für barrierefreie Websites
Received on Sunday, 22 November 2015 11:41:42 UTC