Skip to content

Issues: w3c/captcha-accessibility

Beta
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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
8 Open 1 Closed
8 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Consider distinguishing "legacy" from "state of the art" approaches to allowing only human interaction with an application.
#42 opened Apr 6, 2022 by jasonjgw
What should be the principal conclusions of this version of the document?
#23 opened Feb 10, 2022 by jasonjgw
3
Replace or generalize the example in section 2.2.4
#12 opened Dec 28, 2021 by jasonjgw
Should we cite the WCAG 2.2 "Accessible Authentication" proposal? If so, what should be the approach taken?
#11 opened Dec 28, 2021 by jasonjgw
Consider whether the stand-alone/multi-party dichotomy should still be used as the structure of the document.
#8 opened Dec 8, 2021 by jasonjgw
Consider moving and revising the paragraph on the costs of users' responding to CAPTCHA challenges.
#7 opened Dec 1, 2021 by jasonjgw
Does the "cryptographic attestation of personhood" proposal belong in section 2 ("stand-alone") or section 3 ("multi-party)?
#6 opened Nov 18, 2021 by jasonjgw
Consider whether to revise the conclusions in view of the Cloudflare proposal.
#4 opened Nov 4, 2021 by jasonjgw
ProTip! no:milestone will show everything without a milestone.