Legal
Accessibility statement
We dey aim make Polytxt fit use am by everybody, including customers wey dey use 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.
Wetin dey work for today
- Skip-to-content link for every page (Tab key from page load).
- Keyboard-navigable: every interactive element fit reach without mouse.
- Visible focus rings (Fluent v9 focus indicator: 2px brand outline + offset).
- Light, dark, and system-following colour themes — manual toggle go stay across pages.
- We respect reduced-motion: animations go collapse to instant transitions when
prefers-reduced-motion: reducedon set. - Semantic HTML for inside e plenty — headings dey follow order, landmarks don mark, form fields don label.
- Colour contrast: text dey use Fluent v9 wey get accessible neutrals.
Known limitations
- Some pages still dey migrate from old visual register (the upload preview / progress indicators).
- Contact form na browser-side only for now; we dey develop better inbox wey go fit accessible.
- We no don finish external WCAG audit yet. (Planned ahead of public launch.)
How you fit report problem
If you meet accessibility issue, please use the contact form with subject "Accessibility feedback". We aim make we acknowledge am within one working day and investigate am within five.