Legal

Accessibility statement

How far the public site, the free checker, and the signed-in product have been checked, and how to tell us about a barrier.

Last updated 22 October 2026.

What this covers

GBK Solutions Ltd wants people to be able to use SortProof at sortproof.com. The aim is WCAG 2.2 Level AA for the marketing pages, the free checker, and the signed-in product. This statement describes the checks that have been done. It is not a conformance certificate.

What is in place

  • Pages use headings, labels, and buttons that name the action.
  • Status is shown with a text label as well as colour.
  • The sign-in form can be reached with the keyboard. That check runs with the public pages.
  • The Why panel on a requirement can be used with the keyboard. Escape closes it and focus returns to the control that opened it. Tab stays inside the panel while it is open.
  • Loading placeholders stop animating when the browser asks for reduced motion (prefers-reduced-motion).
  • Public pages are checked automatically with axe-core against WCAG 2.0 A and AA and WCAG 2.2 AA tags (wcag2a, wcag2aa, wcag22aa).

What is still open

  • A recorded VoiceOver pass and a recorded NVDA pass of the checker, the dashboard, and the assessment have not been completed.
  • The automatic check covers the public pages. Signed-in pages are not all included in that public run.
  • A full keyboard walk of every signed-in screen, including completing an assessment and opening the Why panel, is still a manual check.

We will update this statement after those checks, and when a public page changes in a way that affects access.

Reporting a barrier

If something blocks you, use the contact form and choose Other. Include the page address, what you were trying to do, and the browser and assistive technology you use. You can also write to GBK Solutions Ltd, 20 Bouverie Court, Leeds, LS9 8LB. We aim to reply within five working days.

How this statement was prepared

This statement was prepared on 22 October 2026 from the product’s automated public-page checks, the keyboard behaviour of the Why panel, and the accessibility notes kept with the code. The screen-reader rows in those notes are still unticked.

← Back to home