We design and operate chronogate.io so that anyone — including people using assistive technology such as screen readers, keyboard-only navigation, or screen magnification — can browse the catalogue, place an order, activate a platform, and manage their account. Accessibility is part of the work, not an afterthought.

This website partially conforms with WCAG 2.1 Level AA. “Partially” means that most requirements are met but some issues remain open; they are listed below along with planned remediation.

We aim for Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Where WCAG 2.2 introduces a stricter criterion (for example focus-appearance), we adopt it.

• Colour contrast on all text and UI controls is verified against WCAG 2.1 AA (4.5:1 for body text, 3:1 for large text and UI elements).
• Every form field has a visible label tied to an HTML ; error messages are linked to their fields with aria-describedby.
• All interactive elements are reachable and operable with keyboard alone; visible focus rings match the gold accent colour.
• Non-text content (icons, illustrations) carries alt text, aria-label, or role="presentation" depending on purpose.
• The HTML lang attribute is set on every URL-prefix route (/en/, /ru/, /fr/, /nl/) so assistive technology announces content in the right language.

We are working on the following issues. If you hit one, please tell us — a quick report helps us prioritise.

• 3D model viewer on the catalogue page relies on WebGL and has no full-keyboard alternative yet. Product photos and written specifications remain available as a fallback.
• Map pages use Leaflet; zoom controls are keyboard-operable but individual platform markers cannot yet be focused one-by-one. A tabular list view is available on the platforms page as a workaround.
• Chart components (battery, CPU, WiFi history) render as <canvas>. Numeric summaries appear above each chart, but point-by-point time-series data is not yet exposed to screen readers.

This statement is based on our own self-evaluation using the WCAG 2.1 AA success criteria, automated checks with axe-core on representative pages, and manual testing with NVDA and VoiceOver. No third-party audit has been commissioned yet.

If you are not satisfied with our response, you can contact Unia (Belgian Inter-Federal Centre for Equal Opportunities) at unia.be, or raise a complaint with the European Commission under the EU Accessibility Act.

This statement was prepared on 2026-04-20 and will be reviewed at least once a year, or whenever a material change is deployed.