Name of Product/Version: CaptchaText: Captcha Widget (v5)
Product Description: CaptchaText's Captcha Widget (v5) is a JavaScript-based web component that provides CAPTCHA verification functionality for websites and web applications. This standalone widget can be embedded into any HTML-based platform regardless of the underlying technology stack or framework. It offers both visual and audio verification methods to distinguish human users from automated bots, while maintaining strong accessibility features.
Unlike traditional captchas that add background noise to audio challenges or present completely different challenges between visual and audio modes, CaptchaText maintains security through an innovative approach where users identify specific words within clearly spoken phrases that match the text shown in the visual challenge. This synchronized approach allows users with partial vision to benefit from both modalities simultaneously, reducing cognitive load and creating a more inclusive experience. The system offers three difficulty levels: Level 1 requires identifying a single specific word from the phrase, Level 2 requires two specific words, and Level 3 requires three specific words - all while maintaining excellent audio clarity.
The widget provides clear feedback mechanisms to assist users with disabilities and elderly individuals with slower typing speeds. When users enter the correct verification text, the system provides immediate confirmation through both visual indicators (checkmark icons and color changes) and an audio success tone. For incorrect entries, visual feedback is provided to indicate the error, allowing users to easily identify and correct mistakes. This multi-modal feedback system significantly enhances usability for people with visual impairments, cognitive limitations, and motor challenges. The progressive difficulty system ensures both robust security and exceptional accessibility. The widget is designed to be lightweight, customizable, and seamlessly integrates with existing form elements across desktop and mobile interfaces.
Date: 8th March 2025
Contact information: https://www.captchatext.com/support
Notes: This report covers the accessibility conformance of CaptchaText web-based captcha widget (Version 5) only. It does not cover any companion services, developer documentation websites, or account management interfaces.
Evaluation Methods Used: Conformance to the listed accessibility standards has been evaluated by CaptchaText using a combination of manual testing with multiple browser types and assistive technologies, automated accessibility testing tools, and user testing with individuals with disabilities.
Comprehensive Compliance: CaptchaText meets all three conformance levels (A, AA, and AAA) across WCAG 2.0, 2.1, and 2.2 standards, setting a high benchmark for accessibility in the CAPTCHA industry.
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes) Level AA (Yes) Level AAA (Yes) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) Level AA (Yes) Level AAA (Yes) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) Level AA (Yes) Level AAA (Yes) |
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | (Yes) |
| EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03) | (Yes) |
The terms used in the Conformance Level information are defined as follows:
Tables 1 and 2 also document conformance with:
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) |
Supports | All non-text content (captcha image) and controls (buttons) have text alternatives. - Image (captcha) has audio alternative accessible via the audio button. - Controls (buttons) have aria/alternative text that describes their purpose (e.g., "Audio Captcha", "Refresh Captcha"). - Input (forms) has aria/alternative text providing instructions and dynamic status. - CAPTCHA includes aria/alternative text explaining its purpose with "Check to verify if Human" for the checkbox. - Two verification modes are provided: visual (image) and audio (sound playback). - Pure decoration elements can be ignored by assistive technology. - Verification feedback is provided through multiple channels: visual indicators (checkmark for success, X for error) that complement the audio success tone for correct verification, helping both visually impaired and elderly users with processing challenges. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) |
Supports | Unlike most captcha systems that provide completely different challenges for visual and audio modes, CaptchaText's audio alternative directly matches the visual captcha content. This synchronized approach allows users with partial vision to benefit from both modalities simultaneously, reducing cognitive load and creating a more inclusive experience. The audio is provided as an alternative that reinforces rather than replaces the visual captcha. |
| 1.2.2 Captions (Prerecorded) (Level A) |
Supports | Audio is a media alternative for captcha text in image format and does not require captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) |
Supports | Not applicable. CaptchaText does not include video content. |
| 1.3.1 Info and Relationships (Level A) |
Supports | Visually, all controls and information are grouped within a single widget design, making relationships clear. The structure uses proper semantic HTML elements with appropriate ARIA attributes. Input, controls, and status can all be managed within a single input form element. The synchronization between visual captcha text and audio challenge maintains consistent information relationships across modalities, allowing users to seamlessly switch between or simultaneously use both visual and audio modes without losing context. |
| 1.3.2 Meaningful Sequence (Level A) |
Supports | Correct reading/tabbing sequence can be programmatically determined. Focus order follows a logical sequence that preserves meaning and operability as detailed in the documentation section on "Focus Order". |
| 1.3.3 Sensory Characteristics (Level A) |
Supports | Instructions contain clear labels and titles, and do not rely solely on sensory characteristics such as shape, size, visual location, orientation, or sound. Information is conveyed using multiple methods. |
| 1.4.1 Use of Color (Level A) |
Supports | For Controls, Text, and Input, color is only used as assistance and not the only indicator. Visual indicators such as checkmarks and X-marks are used alongside color changes. For verification feedback, successful validation uses a green checkmark icon alongside the color change, while errors use a red X icon, ensuring that the status is conveyed through multiple visual means beyond color alone. Captcha Image is designed to be colorblind-safe, ensuring sufficient contrast for most types of colorblindness. Audio captcha is also provided as an alternative. |
| 1.4.2 Audio Control (Level A) |
Supports | Audio will not play automatically. Both visual and keyboard controls are available to control play/pause of audio. The audio button is clearly labeled with "Audio Captcha" ARIA attribute. Unlike most captcha systems that provide completely different challenges for visual and audio modes, CaptchaText's audio challenge directly corresponds to the visual challenge text, enabling users with partial vision to benefit from both modalities simultaneously without cognitive context switching. |
| 2.1.1 Keyboard (Level A) |
Supports | CaptchaText can be fully operated with keyboard only without requiring specific timings for individual keystrokes. Tab navigation, spacebar for button activation, and standard keyboard interactions are supported throughout the component. |
| 2.1.2 No Keyboard Trap (Level A) |
Supports | Focus on elements can be freely moved on or off using standard keyboards (tab, alt-tab). No keyboard traps are present within the CaptchaText component. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) |
Supports | Keyboard shortcuts are only available on focus of specific elements. No single-character shortcuts are implemented that would require modifier keys. |
| 2.2.1 Timing Adjustable (Level A) |
Supports | Session timers can be extended through the refresh option, providing users additional time to complete verification. The timer provides a 5-minute window with warning notifications at 60 seconds remaining. This is particularly beneficial for elderly users or those with motor difficulties who may require more time for typing and response. The multi-modal feedback system (visual and audio for correct answers) reduces cognitive load and helps users complete verification more efficiently, reducing the need for time extensions. |
| 2.2.2 Pause, Stop, Hide (Level A) |
Supports | Does not contain constantly moving/blinking/scrolling/updating information or visuals. Changes are primarily driven by user action, and any automated changes happen infrequently to reflect state changes. |
| 2.3.1 Three Flashes or Below Threshold (Level A) |
Supports | Does not contain anything that flashes more than 3 times a second. CaptchaText avoids animation patterns that could trigger seizures. |
| 2.4.1 Bypass Blocks (Level A) |
Supports | Not Applicable. CaptchaText is a single-component widget and does not have repeated blocks of content. |
| 2.4.2 Page Titled (Level A) |
Supports | Not Applicable (not a webpage). CaptchaText is a component within pages, not a standalone page. |
| 2.4.3 Focus Order (Level A) |
Supports | Focus order is meaningful and operable. The component uses a logical tab sequence that preserves relationships and meaning: from checkbox to input field to audio button to refresh button. |
| 2.4.4 Link Purpose (In Context) (Level A) |
Supports | Link text and alternative text provide full purpose of links. Any links within the CaptchaText component have clear purposes that can be determined from the link text alone or its context. |
| 2.5.1 Pointer Gestures (Level A 2.1 only) |
Supports | Not Applicable, does not use multipoint/path-based gestures. All operations can be performed with single pointer and without pathing requirements. |
| 2.5.2 Pointer Cancellation (Level A 2.1 only) |
Supports | For single pointers (mouse), action is on up-event only. Users can abort or undo pointer actions before completion, and no down-events trigger actions without an explicit up-event. |
| 2.5.3 Label in Name (Level A 2.1 only) |
Supports | Visual components all have accessible names and descriptions. The visible text labels match the programmatic names, ensuring consistency between visual and programmatic representations. Corresponding text is also presented in the status text portion of widget. |
| 2.5.4 Motion Actuation (Level A 2.1 only) |
Supports | Not applicable. CaptchaText has no device motion operations or actuation. All functionality can be operated through interface components. |
| 2.5.7 Dragging Movements (Level A 2.2 only) |
Supports | CaptchaText does not require dragging movements for operation. All functionality that can be operated by dragging can also be operated by single pointer inputs, ensuring users with limited mobility can interact successfully with the component. |
| 2.5.8 Target Size (Minimum) (Level A 2.2 only) |
Supports | All target sizes for pointer inputs are at least 24 by 24 CSS pixels. Interactive elements such as buttons, checkbox, and input fields meet or exceed the minimum target size requirements, ensuring that users with limited dexterity can interact successfully. |
| 3.1.1 Language of Page (Level A) |
Supports | The language of the page is determined programmatically via the HTML meta header, which captcha clients can use. CaptchaText supports 23 languages with automatic detection based on the user's browser settings. These languages were specifically chosen to align with primary keyboard input languages, ensuring users can complete the captcha challenge using their preferred keyboard input method. If a user's language is not among the supported languages, the system automatically defaults to English. Language can also be manually configured through the data-captchatext-lang attribute or script tag parameters. |
| 3.2.1 On Focus (Level A) |
Supports | No change in context occurs when any component receives focus. Focus changes only highlight the current element without initiating context changes. |
| 3.2.2 On Input (Level A) |
Supports | Any changes in context on input or interaction are appropriate and expected. Changes in settings are only made after explicit user confirmation, and users are informed about behavior that could cause context changes. |
| 3.3.1 Error Identification (Level A) |
Supports | Errors are clearly described in text. Visual icon feedback (X-mark for errors) and textual error messages are provided to help users identify and correct input errors. Error states are identified both visually and programmatically. For successful validation, a checkmark icon appears alongside a color change, and an audio success tone plays to provide feedback through multiple sensory channels, benefiting both visually impaired users and elderly individuals who may need additional confirmation. |
| 3.3.2 Labels or Instructions (Level A) |
Supports | Clear labels and instructions are provided when requiring user input. The captcha provides specific instructions on what text to enter, and all interactive elements have descriptive labels. |
| 4.1.1 Parsing (Level A) |
Supports | Well-formed HTML is used throughout the component. All elements have complete start and end tags, are nested according to specifications, and have unique IDs where required. |
| 4.1.2 Name, Role, Value (Level A) |
Supports | Standard HTML controls (buttons/forms) are used with appropriate ARIA attributes to support programmatically determining name, role, and value. All interactive elements have appropriate accessible names, roles, and states that can be programmatically determined. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) |
Supports | Not Applicable, no live audio content is used in CaptchaText. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) |
Supports | Not Applicable, no video content is used in CaptchaText. |
| 1.3.4 Orientation (Level AA 2.1 only) |
Supports | CaptchaText is fully responsive and can be used in both portrait and landscape orientations. Content presentation is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 only) |
Supports | Standard HTML form elements are used, with labels and/or aria/alt text to further describe and explain input control/purpose. The input field for captcha response has an appropriate accessible name that describes its purpose. |
| 1.4.3 Contrast (Minimum) (Level AA) |
Supports | All theme combinations meet the required contrast ratios. Text has a contrast ratio of at least 4.5:1 against its background, and large text has a contrast ratio of at least 3:1. The default themes support contrast ratios higher than standard requirements. |
| 1.4.4 Resize text (Level AA) |
Supports | Text can be resized up to 200% using native browser support without loss of functionality or content. The component layout adapts appropriately to larger text sizes. |
| 1.4.5 Images of Text (Level AA) |
Supports | There are no 'images of text', except the captcha image itself which is 'essential' to the functionality, and the captcha image text supports audio mode as an alternative. |
| 1.4.10 Reflow (Level AA 2.1 only) |
Supports | The widget does not require 2D scrolling at a width of 320 pixels or a height of 256 pixels. The component is fully responsive and adapts to different viewport sizes, offering micro (60px), mini (150px), and default (400px) size options that expand appropriately when activated. |
| 1.4.11 Non-text Contrast (Level AA 2.1 only) |
Supports | All user interface components and graphical objects maintain a contrast ratio of at least 3:1 against adjacent colors. Status indicators (checkmark for success, X-mark for errors) are designed with high contrast to ensure visibility for users with low vision. The default and pre-set themes support contrast ratios higher than standard requirements, making both the verification process and its results clearly perceivable. |
| 1.4.12 Text Spacing (Level AA 2.1 only) |
Supports | Text spacing properties can be adjusted without loss of content or functionality. The component allows for increased line height, spacing following paragraphs, letter spacing, and word spacing without breaking layout. By default, the widget employs single-line text with optimized spacing to ensure maximum readability and minimal visual clutter. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only) |
Supports | Any content that appears on hover or focus is persistent until dismissed, can be hovered over without disappearing, and remains visible until the hover/focus is removed or the content is explicitly dismissed. |
| 2.4.5 Multiple Ways (Level AA) |
Supports | Not Applicable for single-component widget. CaptchaText is a component within a page, not a complete web page requiring multiple navigation paths. |
| 2.4.6 Headings and Labels (Level AA) |
Supports | Headings and labels clearly describe topic or purpose. The component uses descriptive labels for all form elements and buttons that clearly indicate their purpose. |
| 2.4.7 Focus Visible (Level AA) |
Supports | All elements that gain keyboard focus have visible style changes on focus. Focus indicators are clearly visible and meet contrast requirements against adjacent colors. |
| 2.4.11 Focus Appearance (Minimum) (Level AA 2.2 only) |
Supports | The focus indicator for all user interface components has a contrast ratio of at least 3:1 against adjacent colors and is at least 2 CSS pixels thick. The indicator fully encloses the focused component or has a thickness of at least 8 CSS pixels. All focus indicators are clearly visible when the component has keyboard focus. |
| 2.4.12 Focus Not Obscured (Minimum) (Level AA 2.2 only) |
Supports | When a user interface component receives keyboard focus, no part of the focused component is obscured by author-created content. The widget design ensures that all elements remain fully visible when focused, and no overlapping content appears that would hide any portion of the focused element. |
| 2.5.5 Target Size (Enhanced) (Level AA 2.2 only) |
Supports | All target sizes for pointer inputs are at least 44 by 44 CSS pixels, exceeding the minimum requirements. All interactive elements including buttons, checkbox, and form controls maintain this enhanced target size to ensure users with limited dexterity can interact with ease. |
| 3.1.2 Language of Parts (Level AA) |
Supports | CaptchaText correctly labels language at the HTML element level. When the language changes within the component (such as for multilingual sites), the language is programmatically determined. |
| 3.2.3 Consistent Navigation (Level AA) |
Supports | Not Applicable for single-component widget. CaptchaText maintains consistent presentation and behavior across implementations. |
| 3.2.4 Consistent Identification (Level AA) |
Supports | Not Applicable for single-component widget. Components with the same functionality are identified consistently throughout the captcha interface. |
| 3.2.6 Consistent Help (Level AA 2.2 only) |
Supports | Help mechanisms such as instructions and error messages are presented consistently throughout the widget. The help text and error messages appear in the same location relative to the component across all instances, ensuring users can easily locate assistance when needed. Feedback mechanisms for both correct entries (visual checkmark and audio tone) and incorrect entries (visual X-mark) are consistently implemented, creating a predictable experience that benefits all users, particularly those with cognitive limitations and elderly users. |
| 3.3.3 Error Suggestion (Level AA) |
Supports | CaptchaText provides specific error suggestions for user input. When input errors are detected, suggestions for correction are provided, including clear messaging for invalid responses. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) |
Supports | Not Applicable, no legal commitments or financial transactions. CaptchaText verification doesn't involve data that would require this level of error prevention. |
| 3.3.7 Redundant Entry (Level AA 2.2 only) |
Supports | The widget does not require users to re-enter information they have already provided during a session. All previously provided information is maintained throughout the verification process, with options to automatically reuse this information when appropriate. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) |
Supports | CaptchaText provides an accessible authentication mechanism that doesn't rely solely on cognitive function tests. The audio alternative to the visual captcha ensures that users with cognitive limitations have multiple ways to complete verification, and neither method requires memorization or transcription of complex strings. |
| 4.1.3 Status Messages (Level AA 2.1 only) |
Supports | Status messages are programmatically determined and presented to assistive technologies without receiving focus. Status messages about verification results (success indicated by both visual checkmark and audio confirmation tone, errors indicated by visual X-mark), errors, and session timing are conveyed through multiple channels: visually, audibly for correct answers, and programmatically for screen reader users. This multi-modal approach ensures that verification status is accessible to all users regardless of their abilities or age-related limitations. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.6 Sign Language (Prerecorded) (Level AAA) |
Supports | Not Applicable. No pre-recorded media requiring sign language interpretation is used. |
| 1.2.7 Extended Audio Description (Prerecorded) (Level AAA) |
Supports | Not Applicable. No pre-recorded video content is used. |
| 1.2.8 Media Alternative (Prerecorded) (Level AAA) |
Supports | Not Applicable. No pre-recorded synchronized media is used. |
| 1.2.9 Audio-only (Live) (Level AAA) |
Supports | Not Applicable. No live audio-only content is used. |
| 1.3.6 Identify Purpose (Level AAA 2.1 only) |
Supports | Purpose of controls (User Interface Components) are defined both by standard HTML forms and ARIA descriptions. The component uses appropriate ARIA attributes to identify the purpose of user interface components. Single-line text presentation with appropriate spacing helps further clarify the purpose and function of each component. The widget also incorporates intuitive icons alongside text labels to provide visual cues that reinforce meaning and improve user understanding across different cognitive abilities. This dual approach of simplified text and supportive iconography enhances recognition and interaction for all users. |
| 1.4.6 Contrast (Enhanced) (Level AAA) |
Supports | All theme combinations meet the enhanced contrast requirements. Text contrast ratios exceed 7:1 for normal text and 4.5:1 for large text. |
| 1.4.7 Low or No Background Audio (Level AAA) |
Supports | Unlike traditional captchas that deliberately add background noise to audio challenges or use entirely different challenges between visual and audio modes, CaptchaText's audio is intentionally clear and free from distortion, and directly matches the content in the visual challenge. The security mechanism relies on users identifying specific words within clearly spoken phrases, with a scalable difficulty system: Level 1 requires identifying a single specific word from the phrase, Level 2 requires two specific words, and Level 3 requires three specific words. This innovative approach maintains security without sacrificing audio clarity, providing exceptional accessibility for users with hearing impairments or auditory processing difficulties. The speech is delivered with high clarity and optimal pacing, with no background noise that could interfere with comprehension. |
| 1.4.8 Visual Presentation (Level AAA) |
Supports | Text is purposely designed to be short and presented in single lines throughout the widget, avoiding dense text presentation. All text elements are strategically minimized with proper spacing to reduce cognitive load and enhance readability. Font color can be changed using browser/plugins. Text can be resized to 200% and still remain within full screen. The component allows for foreground/background color selection, text width constraints, and line/paragraph spacing adjustments through browser settings. |
| 1.4.9 Images of Text (No Exception) (Level AAA) |
Supports | No text via image format except for the captcha image itself, which is essential for security functionality and has an audio alternative. |
| 2.1.3 Keyboard (No Exception) (Level AAA) |
Supports | All actions in CaptchaText can be completed with keyboard only with no timing requirements for individual keystrokes. Every feature and function of the component is accessible via keyboard without exception. |
| 2.2.3 No Timing (Level AAA) |
Supports | Timing can be extended through the refresh option, which provides a new challenge with a fresh 5-minute window. While timing is an essential part of security verification, users receive warnings and options to refresh before expiration. |
| 2.2.4 Interruptions (Level AAA) |
Supports | No updates or interruptions that are not user-initiated. Users can postpone or suppress interruptions except for emergencies. |
| 2.2.5 Re-authenticating (Level AAA) |
Supports | Not Applicable. CaptchaText verification is a single event, not an authenticated session requiring re-authentication. |
| 2.2.6 Timeouts (Level AAA 2.1 only) |
Supports | Users are warned when session is about to expire. CaptchaText provides warnings at 60 seconds remaining, and at 10 second intervals thereafter. |
| 2.3.2 Three Flashes (Level AAA) |
Supports | No flashing content. CaptchaText does not contain any content that flashes. |
| 2.3.3 Animation from Interactions (Level AAA 2.1 only) |
Supports | No animations triggered by interaction, except for essential status indicators. Users can disable non-essential animations using the "ani" parameter. |
| 2.4.8 Location (Level AAA) |
Supports | Not Applicable, no multi-page flows. CaptchaText is a single component without navigation structures. |
| 2.4.9 Link Purpose (Link Only) (Level AAA) |
Supports | Link text provides clear meaning. Any links within the component have text that identifies their purpose without requiring additional context. |
| 2.4.10 Section Headings (Level AAA) |
Supports | Not Applicable, no multi-section content. CaptchaText is a compact component without section organization requiring headings. |
| 2.4.13 Focus Appearance (Enhanced) (Level AAA 2.2 only) |
Supports | The focus indicator has a contrast ratio of at least 4.5:1 against all adjacent colors, completely encloses the focused element with a border that is at least 2 CSS pixels thick, and has a surface area at least as large as the area of a 4 CSS pixel thick perimeter of the unfocused component. All focus indicators are prominent and easily distinguishable when the component has keyboard focus. |
| 2.4.14 Focus Not Obscured (Enhanced) (Level AAA 2.2 only) |
Supports | When a user interface component receives keyboard focus, the component is completely visible and no part of it is obscured by any author-created content. The widget layout ensures that focused components remain completely visible on screen without being covered by tooltips, popups, or other dynamic content. |
| 2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 only) |
Supports | No limit on input mechanisms. Users can switch between input methods (keyboard, mouse, touch) without losing functionality. |
| 3.1.3 Unusual Words (Level AAA) |
Supports | No unusual words. CaptchaText uses straightforward language that doesn't require specialized knowledge. |
| 3.1.4 Abbreviations (Level AAA) |
Supports | No abbreviations. CaptchaText does not use abbreviations that would require explanation. |
| 3.1.5 Reading Level (Level AAA) |
Supports | No advanced reading level needed. Instructions and messages use clear, simple language appropriate for lower secondary education level. |
| 3.1.6 Pronunciation (Level AAA) |
Supports | No ambiguous pronunciation. Words used in the component don't have multiple pronunciations that would affect meaning. |
| 3.2.5 Change on Request (Level AAA) |
Supports | Change of context is driven by user action only, except on timeout, which happens infrequently and is essential to captcha security. Users receive clear warnings before timeout-related context changes. |
| 3.3.5 Help (Level AAA) |
Supports | Clear labels and status messages are provided on controls. Contextual help is available through descriptive instructions and error messages. |
| 3.3.6 Error Prevention (All) (Level AAA) |
Supports | Errors can be corrected, and verification steps are included. Users can check, correct, and confirm information before finalizing their submission. |
| 3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only) |
Supports | CaptchaText provides authentication methods that do not rely on cognitive function tests. The widget offers multiple verification methods (visual and audio) and neither requires the user to memorize or transcribe information. Both methods are designed to be cognitively accessible, with simple, clear instructions and feedback. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Supports | CaptchaText widget uses standard HTML and WAI-ARIA attributes and keyboard shortcuts to describe the identity, operation, and state of user interface elements to Assistive Technologies. The audio alternative provides complete verification functionality for users without vision. |
| 302.2 With Limited Vision | Supports | CaptchaText widget supports standard browser magnification and contrast adjustments. The component is compatible with screen magnifiers and offers high contrast themes. Unlike typical captcha systems that force users to choose between visual or audio modes with completely different challenges, CaptchaText's synchronized approach allows users with partial vision to leverage both modalities simultaneously, as the audio challenge matches the visual content. This provides a more inclusive experience for users with a wide range of visual capabilities. |
| 302.3 Without Perception of Color | Supports | Color is only used as decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information. The captcha Image essential to functionality is designed to be color blind safe for most types of color blindness, and an audio mode is supported as well. |
| 302.4 Without Hearing | Supports | CaptchaText widget does not include audio-only features that require hearing to be used. Visual captcha is the primary mode, with audio being an alternative option. |
| 302.5 With Limited Hearing | Supports | CaptchaText widget provides both visual and audio verification options. While the audio CAPTCHA option naturally requires some hearing ability to use, it is designed with exceptional clarity unlike traditional captchas that rely on distortion and background noise. The audio challenge features crystal-clear voice recordings optimized for intelligibility that directly match the content shown in the visual challenge, making it significantly more accessible for users with partial hearing or auditory processing difficulties. For users who cannot use the audio option, the visual captcha serves as an alternative verification method, ensuring the widget remains accessible to users regardless of hearing ability. |
| 302.6 Without Speech | Supports | CaptchaText widget does not require speech input. All interactions can be completed using keyboard, mouse, or touch input. |
| 302.7 With Limited Manipulation | Supports | CaptchaText widget supports standard input mechanisms such as user-provided keyboards and pointing devices. Usage of the product does not require fine motor controls nor simultaneous actions. All controls have sufficient target sizes for users with limited precision. |
| 302.8 With Limited Reach and Strength | Supports | CaptchaText widget's compact design and keyboard accessibility ensures users with limited reach and strength can interact with the verification system. The component's controls are clustered to minimize movement required. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | CaptchaText widget uses simple, clear language and consistent interface patterns to minimize cognitive load. Instructions are concise and straightforward, and the interface uses familiar patterns. The multi-modal feedback system with visual indicators and audio confirmation for successful verification provides reinforcement through different sensory channels, reducing cognitive demand and particularly benefiting elderly users who may need additional validation cues. |
Notes: The CaptchaText Widget is a web software application and is not subject to the requirements of this section.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope – Incorporation of WCAG 2.0 AA | See WCAG 2.x section | See information in WCAG section |
| 502 Interoperability with Assistive Technology | Heading cell – no response required | Heading cell – no response required |
| 502.2.1 User Control of Accessibility Features | Not Applicable | CaptchaText Widget not considered platform software as defined by Section 508 |
| 502.2.2 No Disruption of Accessibility Features | Supports | CaptchaText Widget is compatible with operating system and browser accessibility features configured by the user. The component respects user preferences for high contrast, text size, cursor settings, and keyboard settings. |
| 502.3 Accessibility Services | Heading cell – no response required | Heading cell – no response required |
| 502.3.1 Object Information | Supports | CaptchaText Widget uses standard HTML input elements and WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. Every interactive element has an accessible name that describes its purpose. |
| 502.3.2 Modification of Object Information | Supports | CaptchaText Widget uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. Object attributes can be set or changed in a way that is programmatically available to assistive technologies. |
| 502.3.3 Row, Column, and Headers | Supports | CaptchaText Widget uses standard HTML attributes to define table structure and relationships, including column and row headers, to Assistive Technologies when presenting tabular information. |
| 502.3.4 Values | Supports | CaptchaText Widget uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. Current values of user interface elements are programmatically available to assistive technologies. |
| 502.3.5 Modification of Values | Supports | CaptchaText Widget uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. Values that can be set by the user can be set programmatically, including through assistive technology. |
| 502.3.6 Label Relationships | Supports | CaptchaText Widget uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of "aria-labelledby" and "aria-label" attributes for explicit relationships. |
| 502.3.7 Hierarchical Relationships | Supports | CaptchaText Widget uses standard HTML markup to express hierarchical relationships between elements. Parent-child relationships are programmatically determinable. |
| 502.3.8 Text | Supports | CaptchaText Widget renders strings as plain text values in HTML for maximum compatibility with assistive technologies. Text content, attributes, and text alternative content are programmatically determinable. |
| 502.3.9 Modification of Text | Supports | CaptchaText Widget renders strings as plain text values in HTML for maximum compatibility with assistive technologies. Text that can be set by the user can be set programmatically, including through assistive technology. |
| 502.3.10 List of Actions | Supports | CaptchaText Widget uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. Actions that can be executed on an object are programmatically determinable. |
| 502.3.11 Actions on Objects | Supports | CaptchaText Widget uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. Available actions can be programmatically executed. |
| 502.3.12 Focus Cursor | Supports | CaptchaText Widget provides visible focus indicators for all interactive elements. The location of the keyboard focus indicator is programmatically exposed to assistive technology. |
| 502.3.13 Modification of Focus Cursor | Supports | CaptchaText Widget product uses standard HTML elements with standard cursor controls for user input. Focus can be moved programmatically to keyboard-operable user interface elements. |
| 502.3.14 Event Notification | Supports | CaptchaText Widget provides status notifications for important events, such as validation results, errors, and session timeouts. Notifications about changes in content are available programmatically, including to assistive technologies. |
| 502.4 Platform Accessibility Features | Not Applicable | CaptchaText Widget is not considered platform software as defined by Section 508. |
| 503 Applications | Heading cell – no response required | Heading cell – no response required |
| 503.2 User Preferences | Supports | CaptchaText Widget respects user preferences from platform or OS settings. For example, if user enables high contrast mode, the interfaces will display with high contrast. The component respects system settings for text size, colors, and contrast. |
| 503.3 Alternative User Interfaces | Not Applicable | CaptchaText Widget does not provide any alternative user interfaces that function as assistive technology. |
| 503.4 User Controls for Captions and Audio Description | Heading cell – no response required | Heading cell – no response required |
| 503.4.1 Caption Controls | Not Applicable | CaptchaText Widget does not provide live or recorded audio as primary content. The captcha audio is a secondary mode for the image captcha. |
| 503.4.2 Audio Description Controls | Not Applicable | No video content requiring audio descriptions. |
| 504 Authoring Tools | Heading cell – no response required | Heading cell – no response required |
| 504.2 Content Creation or Editing (if not authoring tool, enter "not applicable") | Not Applicable | CaptchaText is not an authoring tool. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not Applicable | CaptchaText is not an authoring tool. |
| 504.2.2 PDF Export | Not Applicable | CaptchaText is not an authoring tool. |
| 504.3 Prompts | Not Applicable | CaptchaText is not an authoring tool. |
| 504.4 Templates | Not Applicable | CaptchaText is not an authoring tool. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 602.1 General | Heading cell – no response required | Heading cell – no response required |
| 602.2 Accessibility and Compatibility Features | Supports | Documentation includes information about the accessibility and compatibility features of the software, including how to use them. |
| 602.3 Electronic Support Documentation | See WCAG 2.x Section | See information in WCAG section |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | All documentation is provided electronically. |
| 603.1 General | Heading cell – no response required | Heading cell – no response required |
| 603.2 Information on Accessibility and Compatibility Features | Supports | CaptchaText provides a point of contact for information about accessibility features. |
| 603.3 Accommodation of Communication Needs | Supports | Support services accommodate the communication needs of individuals with disabilities through multiple channels. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 4.2.1 Usage without vision | Supports | CaptchaText Widget uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies. The audio alternative provides complete verification functionality for users without vision. |
| 4.2.2 Usage with limited vision | Supports | CaptchaText widget supports standard browser magnification and contrast adjustments. The component is compatible with screen magnifiers and offers high contrast themes. |
| 4.2.3 Usage without perception of colour | Supports | Color is only used as decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information. The captcha Image essential to functionality is designed to be color blind safe for most types of color blindness, and an audio mode is supported as well. |
| 4.2.4 Usage without hearing | Supports | CaptchaText widget does not include audio-only features that require hearing to be used. The primary verification mode is visual, with audio as an alternative. |
| 4.2.5 Usage with limited hearing | Supports | CaptchaText widget provides both visual and audio verification options. While the audio CAPTCHA option naturally requires some hearing ability to use, it is designed with exceptional clarity unlike traditional captchas that rely on distortion and background noise. The audio challenge features crystal-clear voice recordings optimized for intelligibility, making it significantly more accessible for users with partial hearing or auditory processing difficulties. For users who cannot use the audio option, the visual captcha serves as an alternative verification method, ensuring the widget remains accessible to users regardless of hearing ability. |
| 4.2.6 Usage without vocal capability | Supports | CaptchaText widget does not require speech input. All interactions can be completed using keyboard, mouse, or touch input. |
| 4.2.7 Usage with limited manipulation or strength | Supports | CaptchaText widget supports standard input mechanisms such as user-provided keyboards and pointing devices. Usage of the product does not require fine motor controls nor simultaneous actions. All controls have sufficient target sizes for users with limited precision. |
| 4.2.8 Usage with limited reach | Supports | CaptchaText widget's compact design and keyboard accessibility ensures users with limited reach can interact with the verification system. The component's controls are clustered to minimize movement required. |
| 4.2.9 Minimize photosensitive seizure triggers | Supports | CaptchaText widget does not include visual features with flashing that could trigger seizures. No content flashes more than three times per second. |
| 4.2.10 Usage with limited cognition | Supports | CaptchaText widget uses a logical focus order, and provides capabilities for specifying error text for user interface components. Instructions are concise and straightforward, and the interface uses familiar patterns. |
| 4.2.11 Privacy | Supports | CaptchaText widget does not impede usage of standard privacy controls alongside assistive technologies. For example, users can connect a headset for private listening to screen reader announcements. Audio feedback is only played when explicitly requested by the user. |
Notes: CaptchaText Widget supports standard assistive technologies and is therefore not subject to the Closed Functionality criteria described in this Chapter.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 5.1 Closed functionality | Not Applicable | CaptchaText is not closed functionality software. |
| 5.2 Activation of accessibility features | Supports | CaptchaText respects and works with platform accessibility features. |
| 5.3 Biometrics | Not Applicable | CaptchaText does not use biometric forms of user identification. |
| 5.4 Preservation of accessibility information during conversion | Not Applicable | CaptchaText does not convert content from one format to another. |
| 5.5 Operable parts | Not Applicable | CaptchaText is software, not hardware with operable parts. |
| 5.6 Locking or toggle controls | Not Applicable | CaptchaText does not have locking or toggle controls. |
| 5.7 Key repeat | Not Applicable | CaptchaText does not use key repeat functionality. |
| 5.8 Double-strike key acceptance | Not Applicable | CaptchaText does not use keyboard input with double-strike functionality. |
| 5.9 Simultaneous user actions | Supports | CaptchaText does not require simultaneous actions for operation. All functions can be performed with single actions. |
Notes: CaptchaText Widget does not offer two-way voice communication and is therefore not subject to the requirements of this section.
Notes: CaptchaText Widget does not offer video capabilities and is therefore not subject to the requirements of this section.
Notes: CaptchaText Widget is a web software application and is not subject to the requirements of this section.
Notes: Please refer to the WCAG 2.x section for detailed conformance information related to web content requirements.
Notes: CaptchaText Widget does not include non-web documents and is therefore not subject to the requirements of this section.
Notes: The accessibility requirements applicable to CaptchaText Widget as a web-based software component are primarily covered under Chapter 9 (Web) and the corresponding WCAG 2.x section. Additional software-specific aspects have been addressed in Chapter 5 (Software).
Notes: This report covers accessibility conformance for the CaptchaText's Captcha web Widget and does not discuss Documentation or Support Services in detail.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 12.1.1 Accessibility and compatibility features | Supports | Documentation lists and explains the accessibility and compatibility features of the product. |
| 12.1.2 Accessible documentation | See WCAG 2.x Section | Electronic documentation follows the same accessibility standards as the web interface. |
| 12.2.1 Support services for accessibility | Supports | CaptchaText offers support services that provide information and assistance on accessibility features through multiple channels. |
| 12.2.2 Information on accessibility and compatibility features | Supports | Support services provide information about accessibility features and compatibility with assistive technologies. |
| 12.2.3 Effective communication | Supports | Support services accommodate the communication needs of individuals with disabilities. |
| 12.2.4 Accessible documentation | See WCAG 2.x Section | Documentation provided by support services follows the same accessibility standards as the web interface. |
Notes: CaptchaText Widget does not provide relay or access to any emergency services.
This Voluntary Product Accessibility Template (VPAT) represents CaptchaText's good-faith effort to provide accurate information about the accessibility of its product. The information contained in this document is not a legal interpretation of the applicable laws and regulations. CaptchaText makes no warranties, expressed or implied, about the completeness, accuracy, or reliability of the information contained in this document. This report is provided in good faith, and in case of any errors or omissions, please contact us to request corrections or updates to this document as needed.