W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > May 2017

Re: please can you update your vote

From: John Foliot <john.foliot@deque.com>
Date: Wed, 3 May 2017 09:19:24 -0500
Message-ID: <CAKdCpxwFbpNfu0sfo4kvkuG==fBejWWxU-6Scw_Z1X-7iPtngw@mail.gmail.com>
To: "lisa.seeman" <lisa.seeman@zoho.com>
Cc: "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Hi Lisa,

*Re: Timeouts*

Reviewing that GitHub issue, and the final language being proposed remains
unclear (to me).  Are we now being asked to vote on the following text as
the new proposed Success Criteria:

"Where data can be lost due to timeouts, users are warned at the start of a
process about the length of inactivity that generates the timeout, unless
submitted data is preserved for a minimum of a 24 hours." (Level A)

If that is the case, I support this new language - *This SC is ready to go*.


************

*Re: Minimize User Errors*

"The user can select from a choice of valid input values, unless there are
more than thirty one valid values for any section of the input field or
unless this interferes with the main purpose of the content (such as an
evaluation application).

Alternative formats of separator characters such as dash, dots, bracket and
spaces are accepted in numerical inputs except for the use of a dot as a
decimal mark."

I am concerned that this SC has lost its way, and morphed into something
different.

What started as a requirement to Minimize User Errors has now devolved to a
SC that appears to target the <select> element only, by setting a maximum
number of child <option> values (i.e. 31).

While I can see the value in limiting or constraining choices/options to
aid with memory and other coga issues, I question whether the current
language is sufficient to address the core issue originally articulated:

"The intent of this Success Criteria is to minimize user generated errors
by detecting, and when reliable and possible, automatically correcting
common input errors."


One possible "Technique" to avoid/meet this new SC would be to simply not
use <select> elements in your forms (and thus avoiding *any* quantity of
values being offered) - which I do not think is the intent of the Coga TF,
nor something that I could support.

As such, while I strongly support the intent of this proposed SC, I reject
that current revised language as "missing the mark", and request further
editorial revisions.

JF

On Wed, May 3, 2017 at 8:06 AM, lisa.seeman <lisa.seeman@zoho.com> wrote:

> Hi
>
> I have edited the time outs and Minimize user errors  drafts. I think we
> may be very near consensus. Please can you update your vote
> 1) Timeouts: https://www.w3.org/2002/09/wbs/35422/Timeouts_Issue14/
> 2) Minimize user errors: https://www.w3.org/2002/09/wbs/35422/minimize-
> user-errors-13/
>
>
> For Minimize user errors we need to point out in the understanding
> section that the user can also enter free form text and that if any section
> of the input field is like a field record (so if each digit going up to 9
> in a large number is not included)
>
> You will also find in the github issue some more notes. please feel free
> to add there more clarifications that may be needed.
>
> All the best
>
> Lisa Seeman
>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
>
>
>


-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion
Received on Wednesday, 3 May 2017 14:19:59 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:58 UTC