Accessibility

Last updated: 4 August 2026

We want the Coderex website to work for everyone, including people who browse with a keyboard, a screen reader, magnification, or reduced motion. This page describes how we approach that, and how to reach us if something here gets in your way.

Our approach

We aim to meet WCAG 2.1 Level AA, the standard referenced by Section 508 in the United States and by EN 301 549 in Europe. That is the level we work toward rather than a certified conformance claim: we have not commissioned an independent audit, and we would rather describe what we do than publish a grade we cannot show our work for.

In practice we review pages against those criteria, move through them using only the keyboard, check colour contrast, and run automated accessibility tests. We build with standard HTML, using real headings, landmarks and controls, so that assistive technology has something meaningful to work with, and we honour the reduced-motion setting your system already provides.

We do not use an accessibility overlay or widget. Overlays do not change the underlying page and can interfere with the screen reader you already use. We would rather correct the code.

Tell us about a barrier

Automated tests and our own review catch some problems, not all of them. If any part of this site is hard or impossible to use, telling us is the most useful thing that can happen. Please write to accessibility@coderex.com. Say which page and what happened; you do not need to know the technical cause, and a rough description is genuinely enough. We aim to reply within five business days and we treat an access barrier as a bug, not a feature request.

Scope

This page concerns the coderex.com website. The Coderex web application at app.coderex.com and the desktop application are separate products; if you need accessibility information about either, or an Accessibility Conformance Report for a procurement process, write to the address above and we will tell you where things stand.