w3c/captcha-accessibility issues and pull requests

#45 - Fix spaces, spelling, punctuation, and wording

Pull Request - State: open - Opened by llzmb over 2 years ago

#44 - Add a brief introductory section summarizing the organizing themes of the document.

Pull Request - State: open - Opened by jasonjgw over 2 years ago - 2 comments

#43 - Minimal reorganization of the document and temporary removal of Conclusion section.

Pull Request - State: closed - Opened by jasonjgw over 2 years ago

#42 - Consider distinguishing "legacy" from "state of the art" approaches to allowing only human interaction with an application.

Issue - State: open - Opened by jasonjgw over 2 years ago

#41 - Movment authentication - another way for CAPTCHA

Issue - State: open - Opened by hbwhzk over 6 years ago - 1 comment

#40 - Provide more detail on accessibility issues related to video game CAPTCHA and multi-device authentication challenges

Issue - State: open - Opened by mraccess77 over 6 years ago - 2 comments

#39 - Google ReCAPTCHA and it's ability to predict if someone is human

Issue - State: open - Opened by Mattcessability over 6 years ago - 1 comment

#38 - Privacy considerations in CAPTCHA recommendations

Issue - State: open - Opened by ysmartin over 6 years ago

#37 - security and privacy properties of biometrics unstated or confused

Issue - State: open - Opened by npdoty over 5 years ago - 1 comment

#37 - security and privacy properties of biometrics unstated or confused

Issue - State: open - Opened by npdoty over 5 years ago - 1 comment

#36 - privacy/accessibility implications of relying on logged-in identity provider

Issue - State: open - Opened by npdoty over 5 years ago

#36 - privacy/accessibility implications of relying on logged-in identity provider

Issue - State: open - Opened by npdoty over 5 years ago

#35 - blinded verifications and related work are currently missing

Issue - State: open - Opened by npdoty over 5 years ago - 1 comment

#35 - blinded verifications and related work are currently missing

Issue - State: open - Opened by npdoty over 5 years ago - 1 comment

#34 - captcha: what is an aggregator?

Issue - State: open - Opened by samuelweiler over 5 years ago - 1 comment

#33 - captcha: is the issue "exposing their data and content"?

Issue - State: open - Opened by samuelweiler over 5 years ago - 1 comment

#33 - captcha: is the issue "exposing their data and content"?

Issue - State: open - Opened by samuelweiler over 5 years ago - 1 comment

#32 - captcha: too long sentence

Issue - State: open - Opened by samuelweiler over 5 years ago - 1 comment

#31 - captcha: multi-device/cross-site paragraph confusing

Issue - State: open - Opened by samuelweiler over 5 years ago

#30 - captcha: confusing sentence

Issue - State: open - Opened by samuelweiler over 5 years ago - 1 comment

#29 - Logic Puzzle section is a bit thin

Issue - State: open - Opened by jspellman over 5 years ago

#28 - Working Draft Feedback: reCAPTCHA selectively blocks audio challenge

Issue - State: open - Opened by dessant over 5 years ago - 7 comments

#27 - Multi-modal approach to accessibility mediated by Privacy Pass

Issue - State: open - Opened by e271828- over 5 years ago - 2 comments

#27 - Multi-modal approach to accessibility mediated by Privacy Pass

Issue - State: open - Opened by e271828- over 5 years ago - 2 comments

#26 - Working Draft Feedback: Missing proof of work based solutions

Issue - State: open - Opened by ukd1 over 5 years ago - 1 comment

#26 - Working Draft Feedback: Missing proof of work based solutions

Issue - State: open - Opened by ukd1 over 5 years ago - 1 comment

#25 - [CAPTCHA] qualifying study with low # of participants

Issue - State: open - Opened by shawna-slh over 5 years ago

#25 - [CAPTCHA] qualifying study with low # of participants

Issue - State: open - Opened by shawna-slh over 5 years ago

#24 - CAPTCHA Conclusion (Editorial comment)

Issue - State: open - Opened by ysmartin over 5 years ago - 1 comment

#23 - What should be the principal conclusions of this version of the document?

Issue - State: open - Opened by jasonjgw almost 3 years ago - 3 comments

#22 - Working Draft Feedback: Positive examples of accessible CAPTCHA

Issue - State: open - Opened by hpetersFC almost 3 years ago

#21 - Working Draft Feedback: More nuanced verdict of the effectiveness of CAPTCHA

Issue - State: open - Opened by hpetersFC almost 3 years ago

#21 - Working Draft Feedback: More nuanced verdict of the effectiveness of CAPTCHA

Issue - State: open - Opened by hpetersFC almost 3 years ago

#20 - Add the example of voice recognition/speaker identification to the Biometrics section.

Pull Request - State: closed - Opened by jasonjgw almost 3 years ago

#20 - Add the example of voice recognition/speaker identification to the Biometrics section.

Pull Request - State: closed - Opened by jasonjgw almost 3 years ago

#19 - Consider adding the example of voice recognition (speaker identification), used as a biometric identifier.

Issue - State: closed - Opened by jasonjgw almost 3 years ago

#19 - Consider adding the example of voice recognition (speaker identification), used as a biometric identifier.

Issue - State: closed - Opened by jasonjgw almost 3 years ago

#18 - Correct missing ReCAPTCHA version numbers. Closes #17.

Pull Request - State: closed - Opened by jasonjgw almost 3 years ago

#18 - Correct missing ReCAPTCHA version numbers. Closes #17.

Pull Request - State: closed - Opened by jasonjgw almost 3 years ago

#17 - Typo "that their goals with v included"

Issue - State: closed - Opened by lwolberg almost 3 years ago - 2 comments

#16 - UA-driven CAPTCHA with Trust Tokens

Issue - State: open - Opened by Malvoz almost 3 years ago - 3 comments

#14 - Mark repo as host of Note-track work

Pull Request - State: closed - Opened by dontcallmedom almost 3 years ago

#13 - Revise the honeypot example so that it no longer makes a claim about a Web site that has changed (and which will continue to evolve) following publication of the Note. John Rochford observes that the text field in question no longer exists.

Pull Request - State: closed - Opened by jasonjgw almost 3 years ago

#12 - Replace or generalize the example in section 2.2.4

Issue - State: open - Opened by jasonjgw almost 3 years ago

#12 - Replace or generalize the example in section 2.2.4

Issue - State: open - Opened by jasonjgw almost 3 years ago

#11 - Should we cite the WCAG 2.2 "Accessible Authentication" proposal? If so, what should be the approach taken?

Issue - State: open - Opened by jasonjgw almost 3 years ago

#11 - Should we cite the WCAG 2.2 "Accessible Authentication" proposal? If so, what should be the approach taken?

Issue - State: open - Opened by jasonjgw almost 3 years ago

#10 - Consider including email address verification under Multi-Party Approaches?

Issue - State: open - Opened by WestonThayer almost 3 years ago

#10 - Consider including email address verification under Multi-Party Approaches?

Issue - State: open - Opened by WestonThayer almost 3 years ago

#9 - fixing some grammatical errors

Pull Request - State: closed - Opened by wonntann almost 3 years ago

#9 - fixing some grammatical errors

Pull Request - State: closed - Opened by wonntann almost 3 years ago

#8 - Consider whether the stand-alone/multi-party dichotomy should still be used as the structure of the document.

Issue - State: open - Opened by jasonjgw almost 3 years ago

#8 - Consider whether the stand-alone/multi-party dichotomy should still be used as the structure of the document.

Issue - State: open - Opened by jasonjgw almost 3 years ago

#7 - Consider moving and revising the paragraph on the costs of users' responding to CAPTCHA challenges.

Issue - State: open - Opened by jasonjgw almost 3 years ago

#7 - Consider moving and revising the paragraph on the costs of users' responding to CAPTCHA challenges.

Issue - State: open - Opened by jasonjgw almost 3 years ago

#6 - Does the "cryptographic attestation of personhood" proposal belong in section 2 ("stand-alone") or section 3 ("multi-party)?

Issue - State: open - Opened by jasonjgw about 3 years ago

#5 - hcaptcha vs Botstop

Issue - State: open - Opened by TzviyaSiegman about 3 years ago - 3 comments

#5 - hcaptcha vs Botstop

Issue - State: open - Opened by TzviyaSiegman about 3 years ago - 3 comments

#4 - Consider whether to revise the conclusions in view of the Cloudflare proposal.

Issue - State: open - Opened by jasonjgw about 3 years ago

#4 - Consider whether to revise the conclusions in view of the Cloudflare proposal.

Issue - State: open - Opened by jasonjgw about 3 years ago

#3 - Captcha causes catastrophic complications, constantly concerning citizens

Issue - State: open - Opened by Myndex about 3 years ago - 2 comments

#3 - Captcha causes catastrophic complications, constantly concerning citizens

Issue - State: open - Opened by Myndex about 3 years ago - 2 comments

#2 - Add a section summarizing the "cryptographic attestation of personhood" proposal by Cloudflare. Add associated bibliography entries.

Pull Request - State: closed - Opened by jasonjgw about 3 years ago

#2 - Add a section summarizing the "cryptographic attestation of personhood" proposal by Cloudflare. Add associated bibliography entries.

Pull Request - State: closed - Opened by jasonjgw about 3 years ago

#1 - add the bibliography, and update the HTML document to refer to it, as it is now in the same directory as the main document, rather than in the parent directory.

Pull Request - State: closed - Opened by jasonjgw about 3 years ago

GitHub / w3c/captcha-accessibility issues and pull requests