Loading this page
Every figure on this site is deterministic demonstration data. It is not a live source, not a forecast, and not a recommendation. No wagering market is connected, and nothing here should be acted on.
The conformance target, what has actually been verified and by what means, and the limitations that remain.
Structural decisions taken deliberately, each of which is asserted by a test rather than left as an intention.
<details>; the navigation drawer is a native <dialog>; filters, search, sorting and date selection are ordinary forms and links. Each brings its own keyboard operation and screen-reader semantics.h1 per page and no skipped levels. Enforced by the page header carrying the only h1, and asserted across every built route.#main — a skip link that moves only the viewport leaves the next Tab back at the top of the page, which is the common broken version.The means of verification matters as much as the result. An automated pass is weaker evidence than a manual one, and both are weaker than testing with the people affected.
| Area | Status | Verified by | What this does not establish |
|---|---|---|---|
| Contrast (1.4.3, 1.4.11) | Tested. Not verified against a high-contrast operating-system theme, and not reviewed by anyone with low vision. | Automated Axe checks against the rendered components at every viewport, on every built route. | Not verified against a high-contrast operating-system theme, and not reviewed by anyone with low vision. |
| Heading structure (1.3.1, 2.4.6) | Tested. Correct structure does not mean the headings are useful descriptions of what follows. | Asserted per route: exactly one h1, and no level skipped anywhere on the page. | Correct structure does not mean the headings are useful descriptions of what follows. |
| Landmarks and skip link (2.4.1) | Tested. Does not establish that the landmark structure is comprehensible in practice. | Asserted that landmarks are uniquely named, the skip link is the first tab stop, and activating it moves focus rather than only the viewport. | Does not establish that the landmark structure is comprehensible in practice. |
| Keyboard operation (2.1.1, 2.1.2) | Partially tested. Not yet asserted across every built route; only the command centre is covered by the keyboard suite. | Focus order, visible focus indicators and drawer focus containment are asserted on the command centre. | Not yet asserted across every built route; only the command centre is covered by the keyboard suite. |
| Reflow and zoom (1.4.10) | Tested. Reflow at 400% zoom, which 1.4.10 also implies, has not been checked. | Page-level horizontal overflow asserted at seven viewports from 320px, and at 200% zoom. | Reflow at 400% zoom, which 1.4.10 also implies, has not been checked. |
| Target size (2.5.8) | Partially tested. Not asserted for every interactive element on every page. | Navigation controls asserted at or above 24×24 CSS pixels. | Not asserted for every interactive element on every page. |
| Colour independence (1.4.1) | Tested. Automated shape presence is not the same as the shapes being distinguishable at a glance. | Every status badge asserted to carry a shape and a text label alongside its colour. | Automated shape presence is not the same as the shapes being distinguishable at a glance. |
| Charts and non-text content (1.1.1) | Tested. Does not establish that the summaries are actually useful. | Every chart asserted to ship a text summary and a data table carrying the same figures. | Does not establish that the summaries are actually useful. |
| Reduced motion (2.3.3) | Tested. Covered on the command centre only. | Asserted that animation stills completely under a reduced-motion preference. | Covered on the command centre only. |
| Screen-reader comprehension | Not tested. This is the largest gap in the evidence, and no automated result substitutes for it. | Nothing. No testing with a screen reader or with assistive-technology users has been carried out. | This is the largest gap in the evidence, and no automated result substitutes for it. |
| Cognitive load and density | Not tested. A dense research interface has real cognitive-accessibility costs that no automated check measures. | Nothing. No evaluation has been carried out. | A dense research interface has real cognitive-accessibility costs that no automated check measures. |
| Cross-browser behaviour | Not tested. No claim is made about behaviour in any browser other than Chromium. | Chromium only. Firefox and WebKit are unavailable in the development environment. | No claim is made about behaviour in any browser other than Chromium. |
Stated rather than discovered.
Worth stating, because pretending it does not exist would be its own accessibility failure.
A research product for professional use is dense. Dense interfaces are harder to read, harder to navigate and harder to operate with assistive technology than sparse ones, and the honest position is that density and accessibility pull against each other here.
The approach taken is to make density a presentation choice rather than a structural one: the underlying markup is semantic and linear, tables have real headers, charts have tabular alternatives, and every abbreviation is spelled out somewhere a screen reader reaches. Whether that is sufficient is a question for evaluation with actual users, which has not happened.
How to report a barrier.
If you encounter a barrier using this site, it is a defect and worth reporting. This is a foundation build with no production deployment and no support channel yet; when one exists it will be published here.
See also model limitations, which records what this product has and has not demonstrated more broadly.