Could you explain to me the issues with CAPTCHA for verification can cause users with disabilities

- Visual impairments / blindness - Image and text CAPTCHAs (distorted text, image selection) are unreadable or hard to perceive. Screen readers often cannot interpret images or embedded text. (See WebAIM, WCAG) - Cognitive and learning disabilities - Complex puzzles, time limits, or unclear instructions can overwhelm memory, attention, or processing capacity. - Motor disabilities - Tasks requiring precise mouse clicks, dragging, or quick responses are difficult for users with limited dexterity. - Deafblindness and hearing impairments - Audio CAPTCHAs are inaccessible to deaf users; audio alternatives are often poor quality or require hearing that many lack. - Temporary or situational disabilities - Low lighting, glare, or being in a noisy environment can make CAPTCHAs unusable for anyone in those conditions. - Accessibility workarounds often fail - “Accessibility” alternatives (audio CAPTCHAs, hidden fields) are frequently harder, unreliable, or outright inaccessible; some bypasses break assistive tech. - Disproportionate exclusion and privacy concerns - CAPTCHAs can block essential services (banking, healthcare). Audio CAPTCHAs may reveal private information in public; some systems collect biometric or behavioral data creating privacy risks. - Legal and compliance risks - Use of inaccessible CAPTCHAs can violate accessibility laws and standards (e.g., ADA, WCAG 2.1 AA requirement for alternatives). Better approaches - Use accessible alternatives: invisible or behavior-based risk analysis (reCAPTCHA v3), simple checkbox CAPTCHAs, or backend bot-detection that doesn’t require user interaction. - Always provide true, tested alternatives that work with assistive technologies and follow WCAG guidance (e.g., text alternatives, clear instructions, sufficient time). References: WCAG 2.1 (Success Criterion 1.4.5, 3.3.2), WebAIM resources.