I expect the 92% number to rise as the number of anti-AI scraping measures and CAPTCHAs that are not compatible with assistive technologies continues to rise.
That's a good point. It wouldn't be the first time security measures created accessibility problems. CAPTCHAs are a classic example. As organizations roll out more anti-scraping and bot-detection mechanisms, there's definitely a risk of introducing new barriers if accessibility isn't part of the design process from the start.
The ideal outcome is being able to stop abuse without making life harder for legitimate users. I see a good number of scans from accesslumens also gets blocked because of anti-scraping and bot detection which is a good measure in this case
Comments
I expect the 92% number to rise as the number of anti-AI scraping measures and CAPTCHAs that are not compatible with assistive technologies continues to rise.
https://www.w3.org/TR/turingtest/
That's a good point. It wouldn't be the first time security measures created accessibility problems. CAPTCHAs are a classic example. As organizations roll out more anti-scraping and bot-detection mechanisms, there's definitely a risk of introducing new barriers if accessibility isn't part of the design process from the start. The ideal outcome is being able to stop abuse without making life harder for legitimate users. I see a good number of scans from accesslumens also gets blocked because of anti-scraping and bot detection which is a good measure in this case