W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > May 2018

Re: Funka comments on 1.4.11

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Thu, 31 May 2018 14:39:02 +0000
To: Susanna Laurin <susanna.laurin@funka.com>, Shadi Abou-Zahra <shadi@w3.org>, "<public-comments-wcag20@w3.org>" <public-comments-wcag20@w3.org>
CC: Frida Westholm <frida.westholm@funka.com>, Lina Larsson <lina.larsson@funka.com>, Johan Kling <johan.kling@funka.com>, AGWG Chairs <group-ag-chairs@w3.org>
Message-ID: <3100B96D-7D09-407D-BAE5-5153C0164425@adobe.com>
We are not 100% sure we understand, but the fact that you now seem to accept buttons without boundaries is certainly a step in the right direction.
What is the testable definition of a button? I mean how do we test that users understand what a button is?

We don’t define a testable definition of a button, this SC is about User Interface Controls broadly – it is up to the author to determine whether a control should have a button or link role, but both are UI Components so both need to meet 1.4.11.

Would our example buttons below comply with the SC?

My interpretation is that these would. The contrast of the text on the color backgrounds is all well above 3:1.

[cid:image001.png@01D3F8C2.4AE6F430]

AWK


//Susanna

Från: "akirkpat@adobe.com" <akirkpat@adobe.com>
Datum: onsdag 30 maj 2018 20:43
Till: Susanna Laurin <susanna.laurin@funka.com>, Shadi Abou-Zahra <shadi@w3.org>, "<public-comments-wcag20@w3.org>" <public-comments-wcag20@w3.org>
Kopia: Frida Westholm <frida.westholm@funka.com>, Lina Larsson <lina.larsson@funka.com>, Johan Kling <johan.kling@funka.com>, AGWG Chairs <group-ag-chairs@w3.org>
Ämne: Re: Funka comments on 1.4.11

Susanna,
Replying again because I neglected to include the public comments list.

I also wanted to clarify is that we are near the end of our process, we ask that you think about this change and whether you support it, and that you please respond back in the next 24 hours.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

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

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Tuesday, May 29, 2018 at 13:42
To: Susanna Laurin <susanna.laurin@funka.com>, Shadi Abou-Zahra <shadi@w3.org>
Cc: Frida Westholm <frida.westholm@funka.com>, Lina Larsson <lina.larsson@funka.com>, Johan Kling <johan.kling@funka.com>, AGWG Chairs <group-ag-chairs@w3.org>
Subject: Re: Funka comments on 1.4.11

Susanna,
Thank you for your comments. Your email (and comments from others) has stimulated discussion with the Working Group and what seemed to be very clear language at the time clearly is causing some misunderstanding.

The Working Group discussed this at length in email/survey and on a call and believes that the intent of what it was trying to require is better captured with the following:

Non-text Contrast:
The visual <a>presentation</a> of the following have a <a>contrast ratio</a> of at least 3:1 against adjacent color(s):

User Interface Components
Visual information required to identify <a>user interface components</a> and <a>states</a>, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
Graphical Objects
Parts of graphics required to understand the content, except when a particular presentation of graphics is <a>essential</a> to the information being conveyed.

The previous version stated (under User Interface Components):
Visual information used to indicate <a>states</a> and boundaries of <a>user interface components</a>, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;

We think that this will help address your concerns – for example, if a link or button can be identified as an actionable item by a user without information provided by a background color then the contrast of that background color isn’t presenting a barrier for users and isn’t required to meet the 3:1ratio. This text would still require that information about controls meet 3:1,  such as graphical elements used to indicate that a set of targets are a tab control, or the mark indicating that a radio button is selected.

Does this make sense? Would this address your concerns?

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

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

From: Susanna Laurin <susanna.laurin@funka.com>
Date: Wednesday, May 23, 2018 at 12:21
To: Shadi Abou-Zahra <shadi@w3.org>, Andrew Kirkpatrick <notifications@github.com>, "public-comments-wcag20@w3.org" <public-comments-wcag20@w3.org>
Cc: Frida Westholm <frida.westholm@funka.com>, Lina Larsson <lina.larsson@funka.com>, Johan Kling <johan.kling@funka.com>
Subject: Funka comments on 1.4.11
Resent-From: "public-comments-wcag20@w3.org" <public-comments-wcag20@w3.org>
Resent-Date: Wednesday, May 23, 2018 at 12:21

Good morning,

Miscommunication internally led us to miss the f----ng deadline ☺

But here are our comments!

//Susanna



image001.png
(image/png attachment: image001.png)

Received on Thursday, 31 May 2018 14:39:37 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 31 May 2018 14:39:38 UTC