Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication #1452

Closed
dshoukry opened this issue Sep 19, 2020 · 7 comments · Fixed by #1508
Closed

[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication #1452

dshoukry opened this issue Sep 19, 2020 · 7 comments · Fixed by #1508
Labels
3.3.7 Accessible Authentication deprectated - use 3.3.8 Accessible Authentication (Minimum) Member Comment Survey - Added WCAG 2.2
Projects

Comments

@dshoukry
Copy link

dshoukry commented Sep 19, 2020

“Success Criterion 3.3.7 Accessible Authentication (Level A): If an authentication process relies on a cognitive function test, at least one other method must also be available that does not rely on a cognitive function test.”

Most of our comments/proposals are requests to: explicitly clarify some of the definitions, explicitly define how security plays into this topic, add federated identity as an acceptable solution, revise some of the success examples provided, add a section for failure examples, and update some links that 404.

Please find detailed specifics covered in our 3.3.7 Accessible Authentication (Level A) Google Doc.

@alastc alastc added 3.3.7 Accessible Authentication deprectated - use 3.3.8 Accessible Authentication (Minimum) Member Comment WCAG 2.2 labels Sep 19, 2020
@alastc alastc added this to To do in WCAG 2.2 via automation Sep 19, 2020
@cwadamsoforacle
Copy link
Contributor

dshoukry, the link you provide above resolves to a document on 2.5.8 Pointer Target Spacing. I suspect this is not the intended link. Can you update and provide the intended content?

@alastc
Copy link
Contributor

alastc commented Nov 4, 2020

The doc link above has been updated now, thanks @dshoukry

@alastc
Copy link
Contributor

alastc commented Nov 5, 2020

PR #1508 makes some of the updates identified in the document.

In addition, for some of the other comments this is a draft reply to be discussed by the group:


  • The addition of "federated identity" to the note under the SC text does not support the intent of the note. The note is to notify people who have been thinking the SC bans username/passwords, but that is not the case.
  • Adding "It is also important that the success or error messages are accessible and easy to understand" is covered by other success criteria, it is best not to create too much overlap.
  • Adding that "The field labels should clearly identify the name of the website or company requesting the user credentials" is not supported by the SC text, it should not be included in the examples.
  • The audio output of pin numbers (via WebAuth) is not in scope of the SC, it is up to the user's device as to how that is conveyed.
  • "Patterns" in the cognitive functional test definition could refer to either pattern gestures or other patterns, we would rather not restrict it to just gestures.

@alastc
Copy link
Contributor

alastc commented Nov 10, 2020

The group agreed with the PR and the response above.

I'm going to leave this open until I can do another pass and check everything was responded to.

WCAG 2.2 automation moved this from To do to Done Nov 11, 2020
@alastc alastc reopened this Nov 11, 2020
WCAG 2.2 automation moved this from Done to To do Nov 11, 2020
@alastc
Copy link
Contributor

alastc commented Nov 11, 2020

For reference, there have been quite a few changes to the document, from this and other issues. Accessible Auth understanding.

@dshoukry
Copy link
Author

dshoukry commented Jan 9, 2021

Thanks for the updates and for accepting some of the suggestions. I'm gathering internal feedback about the main points and the new updated versions and will provide an update soon.

@alastc
Copy link
Contributor

alastc commented Jan 31, 2021

Hi @dshoukry,

We're going to do another round of review as several SCs have changed significantly. I'll close this as we've dealt with, or replied to, the comments raised. For new feedback, please open a new issue.

Kind regards,

-Alastair

@alastc alastc closed this as completed Jan 31, 2021
WCAG 2.2 automation moved this from To do to Done Jan 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.3.7 Accessible Authentication deprectated - use 3.3.8 Accessible Authentication (Minimum) Member Comment Survey - Added WCAG 2.2
Projects
WCAG 2.2
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants