-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
Distorted photographs used for CAPTCHA (No alternative provided) from our use cases:
|
excellent discussion https://www.w3.org/2016/04/27-lvtf-minutes.html |
somewhat related to CAPTCHA |
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. |
Proposal |
discussed in June 2 telecon. |
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. |
+1 to marking as a best practice. |
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?
The text was updated successfully, but these errors were encountered: