Accessibility Statement

1. Our commitment

We want Balauron to be usable by everyone, including people who navigate by keyboard, use a screen reader, magnify the page, or need reduced motion.

We treat accessibility as a defect class, not a feature request. A barrier that stops you using the site is a bug, and we would rather hear about it than have you work around it.

2. Conformance status

Balauron is partially conformant with WCAG 2.1 Level AA.

"Partially conformant" is the honest answer, and here is exactly why: automated testing across the pages listed in section 3 reports zero violations at Level A and AA. But automated tooling can only detect a fraction of the WCAG success criteria — it cannot judge whether alt text is meaningful, whether a reading order makes sense, or whether a chart is comprehensible without sight. We have not yet completed a full manual audit with assistive technology, so we will not claim full conformance.

3. What we have tested, and how

Last audited: 29 July 2026.

Method: automated scanning with axe-core against the WCAG 2.1 A and AA rulesets, run as part of our automated test suite so a regression fails the build rather than waiting for a person to notice. Plus manual keyboard-only navigation of the pages below.

Pages covered: the home page, and all nine legal pages — Privacy, Terms, Cookies, Risk Disclaimer, this statement, License, Imprint, Site Map and Your Data. The cookie preferences dialog was tested separately in its open state, since a modal is a distinct surface with its own focus behaviour.

Result: no violations of any severity on any page tested.

4. Known issues and limitations

Stated plainly, because a statement that lists no limitations is usually just a statement nobody checked:

• The trading surfaces have not been audited to this depth. The markets board, probability charts, wallet profiles, calendar and leaderboards are data-dense and use SVG visualisations. They carry text alternatives and ARIA descriptions, but they have not been through the same audit as the pages in section 3, and complex data visualisation is genuinely hard to make equivalent for non-visual use. Assume these are less accessible until we say otherwise.
• No screen-reader testing has been carried out yet. We have tested with keyboard and automated tooling. We have not yet sat down with NVDA, JAWS or VoiceOver, so any claim about how the site sounds would be invented.
• One item is flagged "needs review" by our tooling. The language switcher's small ▼ chevron cannot have its colour contrast measured automatically because it contains no text characters. On inspection it is decorative and marked aria-hidden, so assistive technology ignores it and the control itself is properly labelled. We record it here rather than quietly filtering it out.
• Third-party content. Market data comes from external venues; where a market's own question text is poorly written, we surface it as published rather than rewriting it.

5. Technical specifications

Accessibility relies on the following technologies working with your browser and any assistive technology you use:

• HTML
• WAI-ARIA
• CSS
• JavaScript

The legal pages render entirely server-side and remain readable with JavaScript disabled. Interactive features — the cookie preferences dialog, the language switcher, the live market board — require JavaScript.

6. Compatibility

Balauron is built for current versions of Chrome, Edge, Firefox and Safari, on desktop and mobile.

It respects your system preferences: if you have asked your operating system for reduced motion, animations are suppressed. Text scales with your browser's zoom and font-size settings. Colour is never the only way information is conveyed — status and direction always carry a text label as well.

7. Tell us about a barrier

If something here blocks you, email [email protected] and describe what you were trying to do. Telling us the page, your browser and any assistive technology you use helps, but do not let missing details stop you writing — a one-line report is worth more than a perfect one you never send.

We aim to acknowledge accessibility reports within five working days and to tell you what we intend to do about it, including if the answer is that it will take a while.

8. Legal status and enforcement

We should be straightforward about which rules actually bind us.

The EU Web Accessibility Directive (2016/2102), transposed in Romania by Law 232/2022, applies to public-sector bodies. Balauron is a private service, so it is not covered. The European Accessibility Act (Directive 2019/882) applies to certain private services from June 2025, but its service obligations exempt micro-enterprises, and Balauron — operated by one individual, charging nothing — falls well inside that exemption.

So we aim at WCAG 2.1 AA because it is the right target, not because someone is compelling us to. That also means there is no dedicated enforcement body to escalate to if we ignore you. What there is instead is this: if you report a barrier and we do not deal with it properly, say so publicly. That is a weaker remedy than a regulator, and we would rather you never need it.

If Balauron ever begins charging for the service, the Accessibility Act analysis changes and this section will be revisited before that happens.