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

Re: [w3c/wcag21] Minimize User Errors (#13)

From: John Foliot <john.foliot@deque.com>
Date: Thu, 11 May 2017 08:59:30 -0500
Message-ID: <CAKdCpxzPCUXL6Jm5UE2mdF8vb3bGADhcqs88SP5_SOFESNyahA@mail.gmail.com>
To: "w3c/wcag21" <reply+0012be73ebbcc40336a0c45d9db82e358150dfda7caf5f9c92cf00000001152c164292a16>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Cc: "w3c/wcag21" <wcag21@noreply.github.com>, Subscribed <subscribed@noreply.github.com>
> Where it is possible to provide pre-defined choices, the user can select
from a list of valid input values.

Hi Mike,

Playing devil's advocate here, would the following meet this new SC?

"Pick a number between 1 and 20: <input type="text">"

In the example above, I have suggested / requested-one-of a possible 20
"pre-defined" choices as valid input values that you can select from (with
me assuming you can count from one to twenty << the weak link here).
However, I have not actually provided you with a "list" of those options,
as my example question presumes that you already know what those 20 options
may be.

If it is deemed non-compliant, would providing an external list
<http://www.manythings.org/vocabulary/lists/b/words.php?f=numbers_1-20> (or
similar <https://nicholasacademy.com/numbers1to20chart.gif>) meet the
requirement?

If my example passes (and I will argue that it does meet the
"letter-of-the-law" w.r.t. the actual current wording) then it strikes me
then that the current wording really isn't addressing the issue (as I
understand it), which is that we want the content author to present
specific choices, rather than expect the user to be able to 'contain' the
possible answers in short or long-term memory (am I understanding the gist
of the issue correctly? Lisa?)

JF

On Thu, May 11, 2017 at 7:08 AM, mapluke <notifications@github.com> wrote:

> @marcjohlic <https://github.com/marcjohlic> No, you are quite right -
> "where it is possible" will not be accepted. Here is a suggested way to
> overcome this problem:
>
>    - Where only one member of a set of discrete data values is an
>    acceptable input, the user can select from a list of those valid input
>    values.
>    - Where numerical data can be manually entered, alternative separator
>    characters are accepted.
>
> Exceptions:
>
>    - Where the set of discrete data values is larger than thirty-one
>    valid values, it is not necessary to provide pre-defined choices. For
>    example, a piece of data with more then 31 choices could be a year in a
>    date field.
>    - Where limiting input values to a set of discrete values interferes
>    with the main purpose of the content.
>    - Where alternative separator characters could alter the numeric
>    value, such as substituting commas with periods.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/wcag21/issues/13#issuecomment-300769872>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ABK-c6MSb3z-ugCc7cIcnyRDIVBOeIptks5r4vpCgaJpZM4J_16g>
> .
>



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

Advancing the mission of digital accessibility and inclusion
Received on Thursday, 11 May 2017 14:00:05 UTC

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