Accessibility statement for ScoreView

ScoreView is built by ThinkTribal Ltd. We want as many people as possible to be able to use this service. This statement covers the ScoreView application at scoreview.thinktribal.com (authenticated app) and the marketing surfaces at scoreview.thinktribal.com/trust (public).

How accessible this service is

Conformance level: Partial conformance. We aim to meet WCAG 2.2 Level AA. Some parts of this service are not yet fully accessible. We list the known issues below.

Non-accessible content

The following content does not yet meet WCAG 2.2 Level AA. We are working to fix these issues; tracked remediation targets in parentheses.

• 2.4.11 Focus Not Obscured (Minimum): The sticky public-header on mobile (<640px) can obscure the focus ring on the first form field of a long page on Safari. (target: 2026-07-15, tracked at #910)
• 2.5.8 Target Size (Minimum): Some small icon-only buttons on the determination detail page measure 20×20 CSS px against the 24×24 minimum. Sweep in progress. (target: 2026-07-15, tracked at #910)
• 3.2.6 Consistent Help: Help mechanism (contact email + glossary) is in the public footer and the protected sidebar; not yet in the print-only NED one-pager. (target: 2026-08-01, tracked at #910)

Disproportionate burden

We currently claim no disproportionate-burden exemptions. If we introduce one we will publish the assessment here.

Content that is out of scope of the accessibility regulations

Third-party PDFs uploaded by customers (compliance registers, stock-condition surveys) sit outside the regulations because the user controls the content. We do, however, surface the metadata and computed signal in accessible form within the ScoreView UI.

How we tested this service

• Automated testing via axe-core against every authenticated and public route, reported in docs/20260527_ScoreView_UXReview_axe-report.json and docs/20260528_ScoreView_AdminAudit_axe-report.json.
• Manual review against the 9 new WCAG 2.2 success criteria, with particular attention to 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), and 3.3.7 Redundant Entry.
• Keyboard-only walk-through of all primary flows by the build team. Visible focus ring on every interactive element.

Reporting an accessibility issue

If you find an accessibility problem with this service, please email accessibility@thinktribal.com with the URL of the page and a short description. We aim to respond within 5 working days.

Enforcement procedure

If you contact us with a complaint and you are not happy with our response, you can contact the Equality Advisory and Support Service (EASS).

Preparation of this statement

This statement was prepared on 2026-06-02. It was last reviewed on 2026-06-02. The service was last tested on 2026-05-28.