Re: CfC: Checkbox and Radio button labels and 1.3.1

CfC is being withdrawn.

I do feel that we could declare consensus at this point since a supermajority of respondents have indicated support for the proposed resolution and I don’t think that new information has come to light, but given that we are headed into a long weekend here in the US and there is appetite for further discussion, I’d like to withdraw this CfC and take a couple more days to allow the discussion to continue.

I do feel that it is important to recognize that the key thing that the group needs to be able to differentiate between is what WCAG says vs. What we wish WCAG said.  There are very clearly some situations where WCAG does not say what everyone wants.  In some cases it is because what is requested is that WCAG contain language that is technology-dependent (e.g. WCAG needs to say that you must use scope=row or col or use for and id attributes to associate table heading cells with table data cells) and in other cases it isn’t strong or flexible enough (e.g. 4.5:1 contrast requirement).

In these situations we can’t change WCAG 2.0 today, but we can keep a running list of issues and concerns about WCAG 2.0 for a future version or for extension work.

Thanks for thinking about this issue.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com
http://twitter.com/awkawk

http://blogs.adobe.com/accessibility


From: Andrew Kirkpatrick
Date: Saturday, November 21, 2015 at 14:34
To: WCAG
Subject: CfC: Checkbox and Radio button labels and 1.3.1
Resent-From: WCAG
Resent-Date: Saturday, November 21, 2015 at 14:35

CALL FOR CONSENSUS – ends Wednesday November 25 at 9am Boston time.

WCAGers,

We have discussed the issue raised in GitHub regarding the need for radio button and checkbox labels to be defined so that the labels are clickable (https://github.com/w3c/wcag/issues/122). It seems that we have arrived at a consensus on this issue.

This was discussed on this thread: https://lists.w3.org/Archives/Public/w3c-wai-gl/2015OctDec/0193.html


We believe that the consensus view is reflected in this response:
https://github.com/w3c/wcag/issues/122#issuecomment-158676010


If you have new concerns that haven’t been already addressed that should make the WG reconsider this decision, please respond to this call before Wednesday November 25 at 9am Boston time.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk

http://blogs.adobe.com/accessibility