W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2020

RE: SC 2.2.1 Extend (NOT Adjust!!) (Re: SC 2.2.1 Extend "at least ten times")

From: Bruce Bailey <Bailey@Access-Board.gov>
Date: Tue, 11 Feb 2020 16:57:16 +0000
To: WCAG <w3c-wai-gl@w3.org>
Message-ID: <MN2PR22MB17768C348419DAA3B3CC43908C180@MN2PR22MB1776.namprd22.prod.outlook.com>
Sorry to have missed this thread last week.

My recollection is that the Adjust and Extend exceptions are distinct from each other.  For example, if the original timeout is pretty long (could be days even), then the automatic sign-out process (Extend) would not be expected to be ten times the original duration.

I am all for an editorial review.  In particular, I would like for us to propose dropping the explicit “Essential” requirement.  I feel like the several choices more than sufficiently provide for the flexibility needed by security folks.

I put a few more comments in the pull request:
https://github.com/w3c/wcag/pull/1040



From: Alastair Campbell <acampbell@nomensa.com>
Sent: Thursday, February 6, 2020 5:22 AM
To: WCAG <w3c-wai-gl@w3.org>
Subject: Re: SC 2.2.1 Extend (NOT Adjust!!) (Re: SC 2.2.1 Extend "at least ten times")

Interesting,

I’d read it the same way as Patrick, although I have to admit it has only come up in a real scenario a couple of times since 2008!

G180 [1] sort of explains that, but it could be clearer, perhaps in the understanding doc rather than a technique.

Cheers,

-Alastair

1] https://www.w3.org/WAI/WCAG21/Techniques/general/G180<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FWCAG21%2FTechniques%2Fgeneral%2FG180&data=02%7C01%7Cbailey%40access-board.gov%7C319b74fad848450d97c508d7aaee8356%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637165813689143919&sdata=%2BPYRGaG83jO7F0TSjQ7xZs16eYlcCJM3Ihzu7epUZV4%3D&reserved=0>


From: David MacDonald

Hi Makoto

I was present for all of the discussions around that Success Criteria when it was created back in about 2004. The intention was flexibility for the developer. The dev could provide one opportunity of 10 times the default amount of time, OR 10 opportunities to extend it by the default time OR any combination. It could be implemented in any way, either by dialog, or by a personalization setting in the person's account, or by any other means as long as the mechanism to extend it was conforming to WCAG's other SCs (properly labelled, sufficient contrast, etc.)

I hope that helps.


Cheers,
David MacDonald



On Thu, Feb 6, 2020 at 3:40 AM Patrick H. Lauke <redux@splintered.co.uk<mailto:redux@splintered.co.uk>> wrote:
On 06/02/2020 03:14, Makoto Ueki wrote:
[...]
> The point is " extend the time limit at least ten times".

They are given at least 10 opportunities to extend (by whatever time
amount).

P
--
Patrick H. Lauke
Received on Tuesday, 11 February 2020 16:57:22 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:34 UTC