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

Password fields #59

Open
allanj-uaag opened this issue Apr 14, 2016 · 8 comments
Open

Password fields #59

allanj-uaag opened this issue Apr 14, 2016 · 8 comments

Comments

@allanj-uaag
Copy link
Contributor

Recently, on a WAI call the topic of Password Fields came up. The Cognitive Taskforce (COGA) has a paper explaining the cognitive issues around passwords https://rawgit.com/w3c/coga/master/issue-papers/privacy-security.html.

Are there any low vision issues related to passwords and security?

@lauracarlson
Copy link
Contributor

Distorted photographs used for CAPTCHA (No alternative provided) from our use cases:

A person with low vision wants to write a research paper and use a scholar service to alert her of new information. When attempting to sign up she is initially presented with a check box, which says "I'm not a bot". She checks the box.

Then she is presented with a modal dialog, which states "Select all images with street name signs" along with nine photographs (street sign screen capture #1 (.png file)). She has difficulty in identifying the images so she tries again.

Another group of photos appear with the same instruction, "Select all images with street name signs" (street sign screen capture #2 (.png file)).

After voluminous attempts, an error dialog box appears (error screen capture #3 (.png file)).

This experience of numerous, steadfast yet unsuccessful attempts to prove she is a human results in fatigue, frustration, being unable to sign up for the Web service independently, and ultimately having to ask for assistance from another person.

@allanj-uaag
Copy link
Contributor Author

excellent discussion https://www.w3.org/2016/04/27-lvtf-minutes.html

@shawna-slh
Copy link
Collaborator

somewhat related to CAPTCHA

@samccormack
Copy link

We should require masking characters to meet WCAG size and contract requirements for text. Additionally we need to make sure there is a 1 to 1 ratio of masking characters to password characters.

@allanj-uaag
Copy link
Contributor Author

Proposal
User Need - Password: Users need to be able to see the entire password as text before it is submitted.

@shawna-slh
Copy link
Collaborator

discussed in June 2 telecon.
Action: Shawn try putting it in the revised 3.7.1 and ask TF to review it.

@shawna-slh
Copy link
Collaborator

shawna-slh commented Apr 18, 2017

These password issues are usability issues for everyone, more significant for many people with cognitive disabilities, and seem only somewhat more of an issue for people with low vision. I'm not convinced that it warrants adding a low vision user need/requirement.

I propose that it doesn't quite meet the threshold for including in this LV user needs doc at this time, and we mark it as a Best Practice. (Hopefully before too long we'll get to working more on Best Practice doc!) We can add it to the LV user needs doc later if warranted.

@lauracarlson
Copy link
Contributor

+1 to marking as a best practice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants