Accessibility statement
Sekktor is committed to making this platform usable for everyone — including readers and editors who rely on screen readers, keyboard navigation, voice control, magnification, or simply prefer reduced motion. This page describes where we are today and how to tell us when we're falling short.
Conformance target
We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across the public site. We treat AAA criteria as best-effort enhancements rather than blockers.
What's in place
- Three locales (Belarusian, English, Polish) with correct language declarations so screen readers pronounce content in the right voice.
- Required alt text for every image uploaded to the platform.
- Accessible component primitives (Radix UI) for dialogs, dropdowns, tooltips, and form controls — keyboard-navigable and screen-reader-friendly out of the box.
- Semantic page structure with skip-to-main link, landmarks, and meaningful page titles.
- Reduced-motion support: animations and cursor-tracking effects disable when the user has set the system "reduce motion" preference.
- Authentication forms wired with autocomplete attributes so password managers work reliably.
Known issues
- Two color tokens for secondary text are being measured for contrast and may be adjusted; see our internal audit register.
- The Payload CMS admin (used by editors, not readers) is being audited separately. Reader-facing accessibility is the current priority.
- Some icon-only buttons in legacy areas may still lack visible focus indicators; these are being standardised.
Feedback
If you encounter a barrier on Sekktor, please tell us. The fastest way is email — we read every message, prioritise based on user impact, and respond within five working days.
Email: accessibility@sekktor.com
Last reviewed: