Polytxt
Translate a document
Legal

Accessibility statement

We aim to make Polytxt usable by everyone, including customers using assistive technologies. Last updated 13 October 2026.

Standards

We follow readability and legibility best practice on the Microsoft Fluent 2 accessible colour palette, and we are working toward a formal WCAG 2.2 AA audit.

What works today

  • Skip-to-content link on every page (Tab key from page load).
  • Keyboard-navigable: every interactive element is reachable without a mouse.
  • Visible focus rings (Fluent v9 focus indicator: 2px brand outline + offset).
  • Light, dark, and system-following colour themes — manual toggle persists across pages.
  • Reduced-motion respected: animations collapse to instant transitions when prefers-reduced-motion: reduce is set.
  • Semantic HTML throughout — headings in order, landmarks marked, form fields labelled.
  • Colour contrast: text uses Fluent v9 accessible neutrals.

Known limitations

  • Some pages are still being migrated from an older visual register (the upload preview / progress indicators).
  • The contact form is browser-side only at present; a fuller accessible message inbox is in development.
  • We have not yet completed an external WCAG audit. (Planned ahead of public launch.)

How to report a problem

If you encounter an accessibility issue, please use the contact form with subject "Accessibility feedback". We aim to acknowledge within one working day and investigate within five.