airaceGP Docs

Accessibility statement

This statement covers the airaceGP documentation at docs.airacegp.com. The website airacegp.com has its own accessibility statement.

airaceGP is a free, non-commercial private project. The Czech accessibility laws do not oblige it: Act No. 99/2019 Coll. covers public-sector bodies, and Act No. 424/2023 Coll. (the European Accessibility Act) covers products and services sold to consumers, and airaceGP is not sold. The Luxembourg rules on digital accessibility likewise apply to public-sector websites. We follow them voluntarily anyway, with the standard they use: EN 301 549 V3.2.1, which for websites means WCAG 2.1 Level AA.

Compliance status #

Partially compliant

docs.airacegp.com is partially compliant with EN 301 549 V3.2.1 and WCAG 2.1 Level AA, based on our own assessment of 27 September 2026, reviewed on 3 October 2026. We know of no remaining failure, but the docs have not yet been tested with a screen reader, so we do not claim full compliance until they have.

That assessment found problems, and we fixed them before publishing this statement: section links that only appeared on hover and all had the same name, wide tables and code blocks that could not be scrolled with the keyboard, the Escape key not returning focus to the menu button, focus landing behind the open mobile menu, focus outlines hidden under neighbouring cards, and a missing skip link on the page-not-found page.

No assistive-technology user has tested the docs yet. If a test with a real screen reader finds a problem, we will fix it or list it below and change this status.

What is not accessible #

Non-compliant content

None known.

Exempt content

None on these pages. The screenshots of the app show its interface as it is and each has a text alternative that gives the values shown. Links to YouTube and GitHub lead to third-party sites that we do not run or control; their accessibility is up to them.

Disproportionate burden

None claimed: nothing in the docs is left inaccessible on grounds of cost or effort.

How we assessed it #

A self-assessment by the project on 27 September 2026. Every page was checked at 390 and 1440 pixels wide, with animations allowed and with reduced motion:

  • automated testing with axe-core 4.10 against the WCAG 2.0 and 2.1 A and AA rules, with every result axe could not decide reviewed by hand;
  • keyboard only: every link, button and scrolling region reached in order with a visible focus indicator (measured at 3:1 contrast or more), the skip link, and the mobile menu;
  • zoom to 200%, reflow at 320 pixels wide, and the WCAG text-spacing test;
  • contrast of text and controls, and a check that nothing moves or flashes;
  • the structure a screen reader relies on: page language, titles, landmarks, headings, link names and text alternatives.

The automated part is the _verify_a11y.py script in the docs repository. We could not yet test with a real screen reader such as NVDA, JAWS or VoiceOver; that test is still to be done.

Statement prepared on 27 September 2026. Last reviewed on 3 October 2026.

Report a problem #

If something in the docs does not work for you, or you need a page in another form, tell us by email at contact@airacegp.com, or open an issue on the docs repository (a free GitHub account is needed, and issues are public). Say which page, what you were trying to do, and, if you like, the browser and assistive technology you use.

We will answer within one month.