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

Deafblindness - Screen reader and audio CAPTCHAs: Many CAPTCHAs rely on audio alternatives when visual tests fail. For people who are deafblind, audio CAPTCHAs are inaccessible because they cannot both see and hear the challenge, and some screen readers cannot interact properly with these audio controls. - Tactile/alternative options lacking: Few sites provide tactile or braille alternatives, leaving users without any usable method to prove they are human. - Cognitive and time pressure: Navigating complex keyboard-only flows and switching between assistive devices (refreshing, downloading, or playing audio) can be slow and difficult, and CAPTCHAs often impose time limits or require rapid responses. Hearing impairments - Audio-only CAPTCHAs: CAPTCHAs that provide only spoken challenges exclude users with severe or total hearing loss. Even partial hearing loss can make understanding distorted audio difficult. - Poor captioning/transcripts: When an audio alternative is provided, it may lack clear captions or text transcripts, or the on-screen controls are not accessible to assistive tech. - Reliance on sound cues: Some verification flows use short sound cues or beep-based progress signals; these are meaningless for users who cannot hear them. Practical implications and fixes - Provide multiple accessible options: visual, text-based, and accessible keyboard flows; avoid audio-only solutions. - Use accessible, frictionless alternatives: invisible CAPTCHAs, risk-based detection, device/browser signals, or simple challenge questions that comply with WCAG. - Ensure compatibility with assistive tech: ARIA labels, keyboard navigation, and clear transcripts/captions for any audio content. References - Web Content Accessibility Guidelines (WCAG) 2.1, Success Criterion 1.1.1 and 1.4.2. - W3C WAI guidance on CAPTCHAs and accessible alternatives.