Skip to content
Sandbox open: magic test cards, hosted checkout and signed webhooks · 55 payment methods in the catalogue, cards to crypto · Built and hosted in the EEA · Read the API reference at /developers

Sandbox open: magic test cards, hosted checkout and signed webhooks

Accessibility statement

Our conformance with WCAG 2.2 AA and the European Accessibility Act, and how to report a barrier.

Last updated

On this page

Version 1.0, effective 7 October 2026.

Commitment

Kesheron Digital Ltd., trading as Cleared-pay, intends its services to be usable by everyone, including people who rely on assistive technology. The target Cleared-pay builds against is WCAG 2.2 level AA across the marketing site, the hosted payment page, the merchant portal and the emails we send. This statement is made under the European Accessibility Act (Directive (EU) 2019/882), which applies to payment services offered to consumers in the European Union, and describes where we stand today.

Scope of this statement

This statement covers:

  • the public website at cleared-pay.com, including the documentation and blog;
  • the hosted payment page under /pay;
  • the merchant portal under /portal and the backoffice under /admin;
  • transactional emails sent from cleared-pay.com.

It does not cover pages operated by other parties that a payment may pass through, such as a card issuer's authentication page, or documents uploaded by merchants.

Conformance status

Cleared-pay is partially conformant with WCAG 2.2 level AA: some content does not yet fully conform, as listed under known limitations, and our evidence is automated testing plus our own keyboard, motion, reflow and contrast checks, not yet an independent audit or a recorded screen-reader test. This status was last assessed on 7 October 2026.

How we assess

  • Automated checks in the build pipeline. Every website template, every portal and backoffice screen and the hosted payment page are tested with axe-core under the WCAG 2.0 A, 2.0 AA and 2.2 AA rule sets in our end-to-end suite; a serious or critical violation fails the build. A Lighthouse accessibility score of 100 is required against the production deployment.
  • Keyboard operability. The end-to-end suite checks focus order through the component library, arrow-key navigation of data tables, and keyboard control of dialogs and the command palette.
  • Reduced motion. When your system asks for reduced motion, animations resolve to their end state, scrolling marquees are replaced by a static list, and the home-page scene renders as a still image.
  • Reflow. Every website template and every backoffice screen is checked at a viewport 320 pixels wide; horizontal scrolling must not occur (WCAG 1.4.10).
  • Contrast. A token check on every build requires 4.5:1 for every text and background pair (WCAG 1.4.3) and 3:1 for every control border and non-text pair (1.4.11), forbids raw colours outside the token file, and forbids a status colour without an icon or label (1.4.1).
  • Independent review. Not yet commissioned; the reviewer and date will be named here when it is.

Compatibility with assistive technology

The site uses standard HTML, visible focus states, and ARIA only where a native element cannot express a state. Automated testing runs in Chromium. We have not yet completed and recorded a manual screen-reader pass, so we do not claim a tested browser and screen-reader combination; that pass is part of the independent review above. Until then, a report that a screen reader or magnifier does not work with a page is treated as a defect.

Known limitations

  • Charts in the portal and backoffice. Charts are drawn as SVG and may not be fully described to a screen reader. The figures they plot are available in the surrounding lists and in the exports. Text summaries are planned; no date is fixed.
  • Home-page scene. The animated scene on the home page is decorative, is replaced by a still image under reduced motion and by a lighter version on low-capability devices, and carries no information that is not in the text beside it.
  • Automated coverage. Automated checks find only part of what WCAG requires; until the independent review and screen-reader pass are complete, barriers these checks cannot detect may exist.

Report a barrier

If you find a barrier on any page in scope, write to legal@cleared-pay.com. Include the page address, what you were trying to do, what happened instead, and your browser and assistive technology. We acknowledge every report within three business days and tell you within ten business days what we found, when a fix is scheduled, and any alternative way to complete the task. If you cannot complete a payment, tell us and we will contact the merchant.

Enforcement

If our response does not resolve the problem, you may contact the authority that enforces accessibility requirements in your country. Each European Union member state designates a market surveillance authority for the European Accessibility Act; your national consumer protection body can direct you to it.

Preparation of this statement

This statement was prepared on 7 October 2026 by Kesheron Digital Ltd. from the checks in its build pipeline and its own review. It will be updated when the independent review is complete, when a known limitation is fixed, and in any case within twelve months.