
TrustCaptcha and WCAG compliance
TrustCaptcha is compatible with WCAG 2.2 at Level AA: it protects forms without introducing barriers for users with disabilities, because there is no puzzle, image or audio task to solve. This page explains how TrustCaptcha aligns with WCAG principles, why invisible CAPTCHAs matter for accessibility, and what you should document when deploying TrustCaptcha on an accessible website.
Traditional CAPTCHAs often create accessibility problems by requiring users to see images, hear audio, solve puzzles or perform fine motor tasks. TrustCaptcha leaves all of that out.
What TrustCaptcha does
TrustCaptcha protects websites and digital services from automated abuse. The visitor’s browser solves a proof-of-work task that gets harder with the risk of the request, and from the Solo plan each request also gets a bot score from 0 (very likely human) to 1 (very likely bot). All of this happens automatically, without presenting any task or challenge to the user.
TrustCaptcha evaluates technical and behavioral signals in the background to identify patterns associated with bots, spam, credential stuffing and automated attacks, while legitimate users carry on without interruption.
Why CAPTCHAs affect accessibility
Many traditional CAPTCHA mechanisms raise accessibility concerns because they:
- Require visual perception (image selection, distorted text)
- Require audio perception (spoken challenges)
- Demand cognitive interpretation under time pressure
- Introduce keyboard or focus traps
- Interrupt assistive technology workflows
These patterns can disadvantage users with visual, auditory, cognitive or motor impairments and can conflict with WCAG success criteria unless they are carefully worked around.
TrustCaptcha’s approach to accessibility
As an accessible CAPTCHA, TrustCaptcha is designed to avoid these issues entirely.
No user-facing challenge
TrustCaptcha does not present a puzzle, image grid or audio challenge, and users do not have to do anything extra to prove they are human. The widget is visible by default, but it starts on its own and asks for no input. With the paid Captcha Branding add-on it can also run fully invisible.
Because there is no challenge:
- There is nothing to perceive
- Nothing to operate
- Nothing to understand or respond to
No interference with assistive technologies
TrustCaptcha does not add interactive steps that could interfere with:
- Screen readers
- Keyboard-only navigation
- Voice control systems
- Switch devices or alternative input methods
That means no keyboard traps, no extra ARIA work on your side and no added navigation complexity.
Alignment with WCAG principles
WCAG is structured around four principles: Perceivable, Operable, Understandable, and Robust (POUR). TrustCaptcha’s design supports them by leaving very little room for accessibility risk.
Perceivable
TrustCaptcha does not rely on visual or audio cues. Users do not need to see, hear or interpret anything to get through the verification.
Operable
There are no controls to operate, no time limits to manage, and no interaction required. Keyboard-only users are not blocked or diverted.
Understandable
Users are not asked to solve problems, interpret instructions, or understand why they failed a challenge. Legitimate users simply proceed.
Robust
TrustCaptcha does not interfere with semantic HTML, ARIA landmarks, or assistive technology parsing. It operates independently of the accessibility layer of your UI.
WCAG versions and standards context
TrustCaptcha is compatible with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the current W3C recommendation. EU web accessibility law, including the European Accessibility Act, relies on the standard EN 301 549, whose current version references WCAG 2.1 Level AA. Its non-interactive design avoids the perception, operation and comprehension barriers commonly associated with traditional CAPTCHA mechanisms.
Because there are no visual, audio, cognitive or motor challenges, TrustCaptcha also aligns with certain WCAG Level AAA success criteria related to user interaction and perception. However, WCAG conformance at Level AAA is assessed at the level of the overall digital experience, and TrustCaptcha does not claim full AAA conformance independently of the surrounding application.
Side note: WCAG 3.0 is still under development and moves toward an outcome-based model that looks at user needs and functional outcomes rather than prescriptive success criteria. A CAPTCHA without a challenge should fit that model well, since it gives users nothing to fail.
Accessibility statements and documentation
In an accessibility statement, you can describe TrustCaptcha factually: it is a security control that protects forms and critical user journeys from automated abuse without user interaction. It performs its assessment in the background and does not ask users to complete perception-based or interaction-heavy challenges such as image selection, audio prompts, distorted text or time-limited tasks. The exact wording depends on your statement; this is not legal advice, so check it with your legal adviser.
Accessibility checklist for CAPTCHA usage
- CAPTCHA does not require visual, audio, or cognitive challenges
- No keyboard traps or focus interruptions
- No time-limited tasks
- No reliance on perception-based tests
- Accessible support path if a user is incorrectly blocked
Summary
TrustCaptcha protects forms against bots without giving users a challenge, which removes the accessibility issues that come with traditional CAPTCHA systems. For the legal side in Europe, see the guides on the European Accessibility Act and BFSG.


