W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

RE: Target Size and Target Size (no exception) SC

From: Repsher, Stephen J <stephen.j.repsher@boeing.com>
Date: Tue, 23 May 2017 20:16:33 +0000
To: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
Message-ID: <e86bc465de734572b63cc5f59b29d9cf@XCH15-08-08.nw.nos.boeing.com>
Before joining the consensus, I’d like to get clarification on 2 points:

1.       Can I assume that the CSS padding & negative margin technique<http://codepen.io/patrickhlauke/pen/aBNREe> that had been proposed to meet this SC for links within blocks of text is being abandoned?  For the AA version we have the exception, but for AAA I’d like to understand the expected technique.  If it will be simply to adjust font size and/or line height, then I’m okay.  Otherwise, I cannot support this CFC because such a technique decreases  accessibility by causing expanded visual focus indicators for some UA/AT, and the issue of overlap is also not dealt with in any way.

2.       The re-worded exception for user agent control, now meant to exempt controls without styling, reads: “the target is determined by the user agent and is not modified by the author”.  I feel like this was accepted pretty hastily without clarification on where the line in the CSS sand actually lies.  I take this to mean that if any style properties are specified that cascade to a target, then the exception no longer applies.  Is that correct?  For example, if my CSS has a single line to specify a font and nothing else, am I expected now to add more properties to make my “Send” button bigger because “Send” will take the new font?

Steve

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Tuesday, May 23, 2017 12:47 PM
To: WCAG <w3c-wai-gl@w3.org>
Subject: CFC: Target Size and Target Size (no exception) SC
Importance: High

Call For Consensus — ends Thursday May 25rd at 1:00pm Boston time.

The Working Group has reviewed and approved two new Success Criteria for inclusion in the Editor’s Draft: Target Size and Target Size (no exception), at AA and AAA respectively, with the goal of obtaining additional input external to the working group.

Survey results: https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/#wbsq4/results

Call minutes: https://www.w3.org/2017/05/23-ag-minutes.html#item04


The new SC can be reviewed here, in the context of the full draft:
https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/#target-size

https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/#target-size-no-exception<https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/#target-size-all>

If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Standards and Accessibility
Adobe

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

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

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

Received on Tuesday, 23 May 2017 20:17:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 08:04:10 UTC