Accessible & User-friendly CAPTCHA

This page outlines key accessibility aspects to consider when integrating the CAPTCHA widget into your website. It refers to the WCAG accessibility guidelines and the European Accessibility Act (EAA) to help ensure that the CAPTCHA remains accessible in your implementation.

By default, text and background colours are designed to meet WCAG AAA contrast requirements:

• AA: Minimum contrast ratio of 4.5 : 1
• AAA: Minimum contrast ratio of 7 : 1

If you apply custom colours, make sure these contrast ratios are still met. You can find more information about customizing the design in the CAPTCHA widget overview.

Note: Text and background colour customization is available in the Enterprise plan only.

• No colour-only indicators: Important states (default, error, success) must not rely on colour alone. Always include visible text, icons, or ARIA status messages to clarify the meaning.
• Theme compatibility: If your site supports light and dark mode, verify that the CAPTCHA remains clearly visible and fully functional in both.
• Backgrounds: Avoid strong or highly variable background colours that reduce consistency and readability.

Include an associated label indicating what the element is, for example:

“CAPTCHA Verification” or “I’m not a robot check”

This helps screen readers and keyboard users understand that the element is a human verification step.

• When customizing text, use short, clear, and descriptive language.
• The widget automatically inherits the page language (lang attribute).
• If your site uses a different language or locale, explicitly set it via configuration.

For more information on changing the language and customizing texts and translations, see the CAPTCHA widget overview.

If you configure the CAPTCHA to block an action at a high bot score (e.g., form submission), you should display a clear, human-readable message. Optionally, you could provide an alternative contact method or way of verification (e.g., email).

You can configure the following properties during integration:

• Text content
• ARIA attributes
• Language
• Light/Dark mode
• Colour parameters (Enterprise plan)

When customizing, always use clear and descriptive labels (e.g. “Security check – I am not a robot” instead of “captcha1”).

You can find more information in the CAPTCHA widget overview.

• Ensure that popups, cookie banners, or chat widgets do not cover or block the CAPTCHA.
• Keep the focus indicator visible and within the user’s viewport.

The CAPTCHA should appear logically in the form flow (typically before the submit button).

These advanced settings are available in higher-tier plans to tailor usability and security behaviour:

• Custom Difficulty / Duration (Business & Enterprise)
  Adjust how long the CAPTCHA takes. Ideal for audiences using older devices or with low threat levels, as you can keep it shorter for smoother UX.

• Custom Validity Period of Results (Business & Enterprise)
  Defines how long a passed verification remains valid before it must be rechecked. Helpful for multi-step or delayed submission flows.

• Results Retrievable Multiple Times (Enterprise only)
  Enables multiple uses of a previously completed CAPTCHA result in multi-step or asynchronous workflows.

You can find more information in the security rules guide.

Some accessibility options are only available in certain plans, such as Business or Enterprise.
If you have questions about activation or usage, please contact our support team.

The accessibility features and recommendations described in this documentation are based on the principles of the Web Content Accessibility Guidelines (WCAG) and the European Accessibility Act (EAA).
Final accessibility compliance will always depend on the final implementation and integration on the customer’s website or application.