3 ms·

Your CAPTCHA accessibility leaves much to be desired. You require screen reader users to register an account to create a magic cookie that itself requires Safar

Your CAPTCHA accessibility leaves much to be desired. You require screen reader users to register an account to create a magic cookie that itself requires Safari users to disable security protections in their browser in order to use -- and then it doesn't actually work. Please do better. You're blocking off a non-trivial amount of the Internet to blind users. You will eventually be sued for this.

eatbots 6y ago
We actually spend quite a lot of time on this, and regularly work with blind users to test and improve these flows. Most vision-impaired users have no issue in our testing, and it is a much more accessible option than audio challenges, which discriminate against those with auditory processing impairments. (disclosure: work there.)
- disgrunt 6y ago
  Your cookie approach requires: > If you are using the very latest version of Safari on either the recently released OS X 10.15 or iOS 13.4, Apple has just changed the behavior of Safari related to third-party cookies, blocking all of them by default. We are implementing a solution, but in the meantime please visit Safari Preferences, Privacy section, and uncheck "Website tracking: Prevent cross-site tracking" to enable the accessibility cookie to function as expected. [0] [0]: https://www.hcaptcha.com/accessibility https://www.hcaptcha.com/accessibility So while you're patting yourself on the back for not "being like Google", your accessibility workaround exposes blind users to third party trackers like Google.
  - thewebcount 6y ago
    > uncheck "Website tracking: Prevent cross-site tracking" Holy moley! Yeah, that's a deal-breaker. I agree that this is entirely unacceptable.
  - eatbots 6y ago
    Using any kind of privacy/adblock extension that supports domain-level whitelisting (e.g. uBlock Origin) works fine, and this is what we suggest in the accessibility FAQ. Apple didn't build fine-grained controls into their browser before making this recent change, unfortunately. That said, we're working with the browser makers on native support for our next gen privacy-preserving approach to this via Privacy Pass.

eatbots 6y ago

We actually spend quite a lot of time on this, and regularly work with blind users to test and improve these flows. Most vision-impaired users have no issue in our testing, and it is a much more accessible option than audio challenges, which discriminate against those with auditory processing impairments. (disclosure: work there.)

disgrunt 6y ago
Your cookie approach requires: > If you are using the very latest version of Safari on either the recently released OS X 10.15 or iOS 13.4, Apple has just changed the behavior of Safari related to third-party cookies, blocking all of them by default. We are implementing a solution, but in the meantime please visit Safari Preferences, Privacy section, and uncheck "Website tracking: Prevent cross-site tracking" to enable the accessibility cookie to function as expected. [0] [0]: https://www.hcaptcha.com/accessibility https://www.hcaptcha.com/accessibility So while you're patting yourself on the back for not "being like Google", your accessibility workaround exposes blind users to third party trackers like Google.
- thewebcount 6y ago
  > uncheck "Website tracking: Prevent cross-site tracking" Holy moley! Yeah, that's a deal-breaker. I agree that this is entirely unacceptable.
- eatbots 6y ago
  Using any kind of privacy/adblock extension that supports domain-level whitelisting (e.g. uBlock Origin) works fine, and this is what we suggest in the accessibility FAQ. Apple didn't build fine-grained controls into their browser before making this recent change, unfortunately. That said, we're working with the browser makers on native support for our next gen privacy-preserving approach to this via Privacy Pass.