We are active participants in the IETF working group standardizing this new technology.
We believe combining our current a11y approach with Privacy Pass issuance will allow a11y users to browse safely, secure in the knowledge that their traffic is more private, while restricting the abuse by bot operators that inevitably occurs when a11y options are available. However, we are very interested in Privacy Pass for the Accessibility use case.
avoiding the challenge altogether, but will consider it if there is demand from the a11y community. We are thus less enthusiastic about this approach vs. This has forced current audio challenges to become more and more difficult, introducing noise, odd timing, unusual word combinations, and so on to defeat attackers. Q: Are you working on other accessibility ("a11y") options, like audio?Ī: Previously popular options like audio captchas discriminate against many a11y users and are easily defeated by modern machine learning techniques. However, this is not legal advice: you should perform your own evaluation, taking into consideration your particular implementation to ensure this is the case for your deployment. Q: Is hCaptcha Section 508 + WCAG 2.1 AA compliant?Ī: We believe so: all users with any form of impairment who are able to browse the web and enter text on forms can access services protected by hCaptcha upon registration.
0 kommentar(er)
