Inclusion

Accessibility statement

People come to Bitaps under stress, often after losing significant savings. The website and client portal must work for everyone in that moment — including people who use screen readers, keyboard-only navigation, magnification or reduced motion.

Last updated 24 August 2026

01Our commitment

We aim to make this website and the client portal perceivable, operable, understandable and robust for the widest possible audience, and we treat accessibility defects as ordinary bugs rather than optional enhancements.

02Standard we design against

We design and build against the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA as our reference standard. This statement describes our own testing and self-assessment; it is not a third-party certification or audit result.

03Measures in place

  • Semantic HTML structure with a single main landmark and a logical heading order on each page.
  • Full keyboard operability, with visible focus indicators on links, buttons, tabs and form fields.
  • Accessible names on icon-only controls, and form fields associated with labels rather than relying on placeholder text.
  • Dialogs, menus and tabs built on accessible primitives that manage focus and ARIA state.
  • Dark-first colour system chosen for contrast, with information never conveyed by colour alone.
  • Responsive layouts that reflow to small screens and support zoom to 200% without loss of content.
  • Entrance animations that respect the operating system’s reduced-motion preference.
  • Tap targets on primary actions sized for touch use.

04Known limitations

We are candid about the areas we are still improving:

  • Complex transaction-graph exhibits inside forensic reports are visual by nature; we provide the same findings in narrative and tabular form on request.
  • Documents you or third parties upload to a case file — police reports, exchange correspondence — may not themselves be accessible, as we do not control their source.
  • Long monospace identifiers such as wallet addresses and transaction hashes can be verbose for screen reader users; we are continuing to improve how these are announced and truncated.

05Alternative ways to get help

If any part of this site or the portal prevents you from reporting an incident or following your case, we will work with you directly. Email support@bitaps.co or message us on WhatsApp at +44 7441 929224 and we will take your case details, send documents in an accessible format, and read reports back to you where that helps.

06Reporting a barrier

Tell us what you were trying to do, the page or screen involved, and the assistive technology, browser and device you were using. Send it to support@bitaps.co with “Accessibility” in the subject line.

We acknowledge accessibility reports within five working days and give you a remediation plan or a workaround. If you are not satisfied with our response, you may escalate to the accessibility or equality body in your jurisdiction.

07How we test

Accessibility checks are part of our review process: keyboard-only walkthroughs of the intake form and client portal, screen reader spot-checks of case stages and file uploads, automated checks for contrast, labelling and landmark structure, and manual review of any new component before it ships.

Questions about this document?

Write to support@bitaps.co or contact us at Marken 6, Himmelev, 4000 Roskilde, Denmark.

See also our legal & policy centre.