TrustComponent

Accessible CAPTCHA without puzzles

Invisible CAPTCHA designed to reduce friction and avoid puzzle-based barriers.

Accessibility as a core design principle

TrustCaptcha helps protect forms and flows from bots without forcing users to solve puzzles, identify images, or complete audio/visual challenges.

Traditional CAPTCHAs often create accessibility barriers, especially when they rely on image recognition, distorted text, audio prompts, timed challenges, or interaction-heavy widgets. An accessible CAPTCHA should not depend on any of these. TrustCaptcha takes a different path: it is an invisible CAPTCHA built to work in the background so users can complete forms with no extra steps.

That helps everyone, including people who use screen readers, keyboard-only navigation, switch devices, voice input or other assistive setups. The sections below show how the widget behaves, which standards apply and where to find documentation for audits.

What “no interaction” means in practice

TrustCaptcha verification is designed to be passive, so users aren’t interrupted during critical journeys like sign-up, login, or checkout.

  • ✓ No puzzles, image selection, or distorted text
  • ✓ No audio challenge requirements
  • ✓ No extra clicks or “prove you’re human” steps
  • ✓ Designed to preserve keyboard flow and form semantics

How TrustCaptcha supports accessible user journeys

Key design goals that help reduce common CAPTCHA accessibility issues.

No interaction required

TrustCaptcha is an invisible CAPTCHA. Users don’t solve puzzles, click images, or decode text. Verification is passive.

No time-pressure challenges

There are no countdown tasks, which can put people with motor, cognitive or processing disabilities at a disadvantage.

Assistive-tech friendly UX

No modal puzzle overlays, no audio CAPTCHA, and no visual-only tasks, so screen reader and keyboard users can complete forms smoothly.

Predictable form behavior

Integrated with the recommended patterns, the widget leaves focus order, tab navigation and form semantics intact.

Standards & expectations

Accessibility standards and regulations

The laws and standards a CAPTCHA is most often checked against, and how a CAPTCHA without puzzles fits each one.

WCAG (Web Content Accessibility Guidelines)

Web Guideline

Many teams assess accessibility against WCAG (WCAG 2.2, backward compatible with WCAG 2.1 and WCAG 2.0). TrustCaptcha is designed to be WCAG 2.2 compliant and reduce CAPTCHA-related barriers by avoiding puzzles, timers, audio tasks, and complex interactions. Verification requires no user interaction by default.

European Accessibility Act (EU)

Directive

TrustCaptcha keeps the check passive. There is no puzzle, no audio or image task and no extra step that could interrupt a sign-up or checkout for someone using assistive technology.

BITV 2.0 (Germany)

DE Regulation

For most visitors the check runs in the background, so keyboard navigation, focus order and form behavior stay the way you built them. There is no challenge widget to trip up assistive technology.

BFSG (Germany)

DE Law

Sign-up, login, checkout and contact forms are where puzzle CAPTCHAs cause the most trouble. TrustCaptcha leaves the puzzle out, so these forms stay simple and predictable.

EN 301 549 (EU)

EU Standard

TrustCaptcha asks for little or no interaction and opens no challenge overlay, so you can add bot protection without breaking the semantics of your forms.

ADA (United States)

US Guidance

Traditional CAPTCHA challenges often ask people to recognize images or sounds. With TrustCaptcha your site does not depend on them, and users complete forms without extra steps.

Section 508 (US Federal)

US Federal

Timed challenges and modal puzzles often get in the way of keyboard navigation and screen readers. TrustCaptcha uses neither, which helps keep public sector forms usable.

AODA (Ontario, Canada)

CA (ON) Law

TrustCaptcha removes the puzzle step and keeps verification passive. Our integration guidance shows how to keep focus and tab order intact for people who rely on assistive technology.

Resources

Accessibility documentation & support

Resources for product teams, auditors, procurement, and customer support.

Accessibility statement & support

Need help integrating TrustCaptcha in an accessible way, or want to report an accessibility issue?

Contact accessibility support

Accessibility Conformance Report (ACR) / VPAT request

You can request documentation for procurement and compliance reviews.

Request ACR / VPAT

Implementation guidance for accessible forms

Technical recommendations for adding the widget to accessible forms.

Integration guidance

Frequently Asked Questions

Questions about TrustCaptcha accessibility

If you don’t find what you need here, contact us and we’ll help.

How is TrustCaptcha different from traditional CAPTCHAs for accessibility?
Traditional CAPTCHAs often require visual recognition, audio tasks, timed puzzles, or multi-step widgets. TrustCaptcha is an invisible CAPTCHA designed to run in the background, so most users complete forms with no extra interaction, which reduces common accessibility barriers.
Do users need to click a checkbox or solve puzzles?
No. TrustCaptcha is a no-interaction CAPTCHA: there are no image puzzles, distorted text, or audio challenges. Verification is designed to be passive during normal use.
Does TrustCaptcha work with screen readers and keyboard-only navigation?
TrustCaptcha is designed to avoid UI challenges that commonly interfere with assistive technology. When integrated using recommended patterns, it should not disrupt focus order, tab navigation, or semantic form behavior.
What happens if verification can’t be completed?
TrustCaptcha never hard-blocks access. When verification can’t be completed (e.g., because of network restrictions, privacy tools, or uncommon devices), TrustCaptcha reports this outcome to your integration. The site owner/operator determines the next step, such as allowing or preventing access, requesting a second verification method, or routing the user to manual review.
Can TrustCaptcha help with WCAG-related risk from CAPTCHAs?
Because TrustCaptcha removes puzzle-based interaction and avoids visual-only or audio-only challenges, it can reduce the accessibility risks commonly associated with CAPTCHAs. Accessibility outcomes still depend on the surrounding form UX and your overall implementation.
Do you provide accessibility documentation for audits or procurement?
Yes. Where applicable, we can provide documentation to support reviews (such as an ACR/VPAT request) and integration guidance. Contact us through the resources section for details.