Trust
Accessibility
Our target is WCAG 2.1 level AA. Here is where we actually are against it.
Last updated 15 August 2026
Draft — not yet legally reviewed
This document describes how the service actually works, but it has not been checked by a lawyer and the operating entity is not yet named. Have it reviewed for your jurisdiction before you rely on it. This notice disappears once the registered company details are filled in.
People pursuing a refund are often stressed, often on a phone, and sometimes using assistive technology. A claim you cannot file is a claim you lose, so this is not decoration.
What is in place
- Keyboard access. Every interactive control can be reached and operated by keyboard, with a visible focus ring. The sign-in method switcher and the six-digit code boxes support arrow keys, and there is a skip link to the main content.
- Contrast. Body and heading colours were measured against their real backgrounds rather than assumed. Text on the dark green bands sits at roughly 9.8:1, and the hero headline at about 17.7:1 — both comfortably past the 4.5:1 requirement.
- Touch targets. Controls on the sign-in, sign-up, claim and support forms are at least 44×44px, which is beyond the 24×24px the standard asks for.
- Labels and errors. Every input has a real
<label>. Validation errors are tied to their field witharia-describedby, marked witharia-invalid, and never signalled by colour alone — each carries an icon and text. - Motion. The homepage carousel stops auto-advancing and drops its cross-fade when your system asks for reduced motion, and it can be paused outright.
- Structure. One
<h1>per page, headings in order, landmark regions, and images either described or marked decorative. - Zoom and reflow. Layouts work down to 320px and up to 200% zoom without horizontal scrolling.
What is not done yet
We would rather list these than claim conformance we have not earned:
- No audit has been carried out with actual screen readers — NVDA, JAWS and VoiceOver — only with automated checks and manual keyboard testing.
- No testing has been done with users who rely on assistive technology.
- The status tracker on a claim conveys progress partly through position and colour; it needs a clearer text equivalent.
- The interface is English only, which is a barrier in itself for some users.
So: we are aiming at WCAG 2.1 AA and believe we meet much of it, but we are not claiming full conformance until it has been independently checked.
Tell us about a barrier
If something here stopped you doing what you came to do, email support@securerefund.online and say what you were trying to do, what happened, and what you were using. We will reply within 5 business days and tell you honestly whether and when we can fix it.
If the site is blocking you from filing a claim before a deadline, say so in the subject line — we will take the details another way and file it for you rather than let the deadline pass.
Questions about this page? Email support@securerefund.online.
