Accessibility Statement

01 Standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Where a component does not yet meet that standard, it is listed below.

02 What we have done

• Semantic HTML with proper heading order, landmarks and lists.
• A skip link to the main content on every page.
• Visible keyboard focus indicators, and full keyboard operability without a mouse.
• Text contrast meeting or exceeding the AA ratio against its background.
• Form fields with associated labels, required fields marked in text as well as colour, and errors described in words.
• Status and error messages announced to assistive technology.
• Colour never used as the only way to convey meaning — verdicts carry a word as well as a colour.
• Reduced motion honoured: animation is suppressed when the operating system requests it.
• Responsive layouts that work at 320 pixels wide and at 200% zoom without loss of content.
• Legal pages formatted to print cleanly, for people who prefer to read on paper.

03 Known limitations

We are aware of the following and are working on them:

• Some dense data tables in the registry require horizontal scrolling on small screens.
• A small number of exported PDF reports are not fully tagged for screen readers.
• Third-party embedded content, where used, may not fully meet AA.
• Some older analytics charts lack a full text alternative; a data table equivalent is available on request.

If something is blocking you and it is not on this list, please tell us — we would rather know.

04 Feedback and alternative formats

Email support@supersaveprotocol.com with the page address, what you were trying to do, and the assistive technology or browser you were using. We acknowledge within 3 business days and aim to give a substantive answer within 10.

We can supply any document on this site in an alternative format — large print, plain text, or accessible PDF — on request and at no charge.

05 Enforcement

If you are not satisfied with how we respond, you may raise the matter with the equality or accessibility body in your jurisdiction. We would appreciate the chance to fix it first.

06 How we test

We test with automated tooling on every release, and carry out manual keyboard and screen reader testing on major changes. This statement is reviewed at least annually and whenever a significant change is made to the site or the registry.