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

CAPTCHAs often block people with disabilities because they assume visual, auditory, motor, or cognitive abilities that not all users have. Common problems: - Visual CAPTCHAs (distorted text, images) are unreadable for users who are blind, have low vision, or have cognitive processing differences. - Audio CAPTCHAs can be unusable for users who are deaf or hard of hearing, and noisy audio or speech distortions make them hard for many others. - Time limits and complex interactions (dragging, clicking small targets) exclude users with motor or cognitive impairments. - Lack of clear instructions or no text alternatives prevents screen reader users from understanding required tasks. Selection rationale and required approach Always provide true, tested alternatives that work with assistive technologies and follow WCAG guidance. That means: - Offer accessible text alternatives and clear instructions that a screen reader can read (WCAG 2.1 SC 1.4.5, 3.3.2). - Avoid reliance on sensory characteristics alone; provide an alternative that does not require specific visual or auditory skills. - Allow sufficient time and simple, keyboard-accessible controls for completing verification. - Test alternatives with real assistive technologies (screen readers, voice control, switch devices) and real users with disabilities. Practical, tested alternatives - Use invisible risk-based or behavioral bot detection (server-side heuristics or device fingerprinting) that does not require user interaction. - Implement simple, accessible challenge alternatives: plain-language questions with text alternatives, or one-click verification links sent via email/SMS. - Use WCAG-compatible secondary checks: e.g., accessible logic challenges that are keyboard and screen-reader friendly, with clear instructions and no strict time-outs. - Provide multiple verification channels (email, SMS, authenticator apps) and ensure each channel is accessible. References - WCAG 2.1: Success Criterion 1.4.5 Images of Text; Success Criterion 3.3.2 Labels or Instructions. (W3C) - WebAIM: CAPTCHA and Accessibility guidance and testing resources. (Short, tested alternatives above should be implemented and validated with assistive technologies and users with disabilities.)