W3C home > Mailing lists > Public > public-silver@w3.org > May 2021

Request from Conformance Options

From: Sajka, Janina <sajkaj@amazon.com>
Date: Tue, 25 May 2021 08:48:23 +0000
To: Sarah Horton <sarah.horton@gmail.com>
CC: "public-silver@w3.org" <public-silver@w3.org>
Message-ID: <1d09520201c34726a5c62d371b482d7e@EX13D28UWC001.ant.amazon.com>
Hi, Sarah:

Conformance Options subgroup has asked that I contact you and your Errors
subgroup regarding the following use case, which comes under our draft
Principle #2.

We are concerned that the use case itself is important, but arguably not the
best fit for illustrating our Principle #2. Does it fall within the kinds of
errors your group is addressing?

Herewith the principle and use case from our Google Doc at:

https://docs.google.com/document/d/1GyUYTnZp0HIMdsKqCiISCSCvL0su692dnW34P81kbbw/

2.  The solution should enable website visitors with disabilities to
accomplish what they want on the site with a minimum of difficulty.\

Use case** **D** \[discussed 4Feb21\]: A user is trying to log in,
and there is an error on login. The user doesn't receive an error
message - they are simply prompted again to log in at the login
prompt. The context indicates what should be done next - to correctly
enter their username/password - even without an explicit error
message. \[Concern that for people with cognitive impairments, the
context isn't enough, and this isn't a good example of "minimum of
difficulty" for these individuals\]

On the other hand it would seem that too much specificity would likely violate
reasonable security considerations, e.g. you wouldn't want to tell the user
"The third character in your password is incorrect."

Best,

Janina
On behalf of Conformance Options subgroup



----------------------------------

Janina Sajka
Accessibility Standards Consultant
sajkaj@amazon.com<mailto:sajkaj@amazon.com>
Received on Tuesday, 25 May 2021 08:48:39 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 25 May 2021 08:48:40 UTC