Policy

Accessibility Statement

What we have built for accessibility so far, what we know is still imperfect, and how to report a problem.

Version
0.9-draft
Last updated
2026-11-16
Effective
not yet set

Draft policy

This is a working draft. It is published so members can see how OddsButter operates today. Business details and legal review are still required before it is final: Pending Accessibility Audit.

Contents
  1. 1. Our commitment
  2. 2. What we have done
  3. 3. Known limitations
  4. 4. Reporting a problem
  5. 5. Ongoing work

1. Our commitment

OddsButter should be usable on a phone, with a keyboard, with a screen reader, and at larger text sizes. Accessibility is treated as part of building the product, not a separate project.

We have not completed an independent accessibility audit, so we do not claim WCAG conformance or certification at any level. This statement describes current practices and known gaps honestly.

2. What we have done

Layout is single-column and mobile-first, with no horizontal scrolling at typical phone widths, and the same structure is used on larger screens rather than a separate desktop shell.

Interactive controls are native buttons and links with visible text labels, the main navigation uses a labelled navigation landmark, and the current tab is marked for assistive technology.

Form fields have associated labels, the checkout and cancellation actions state the amount and date they will cause, and errors are shown as text next to the action rather than by colour alone.

Colour choices aim for readable contrast between text and background on the dark charcoal surfaces, and butter-yellow is used for emphasis rather than for long body text.

Images that carry information include alt text; decorative marks are hidden from assistive technology.

3. Known limitations

Some data tables and chart-like previews are visually dense and are easier with sight. Where a number matters, the same value is also written as text, but not every visualisation has an equivalent long description yet.

The product was built primarily for phones; a few admin and research screens are functional on a phone but not as comfortable as the five main tabs.

Motion is limited to short fades and rises, but we have not yet added a full reduce-motion path for every animation.

This draft is flagged for a real accessibility audit, including keyboard-only and screen-reader passes, before it makes any stronger claim.

4. Reporting a problem

Use the Contact and Support page and choose Accessibility. Tell us the page, what you were trying to do, and the device, browser or assistive technology you were using. Screenshots are optional and should not include personal or payment information.

Accessibility reports are recorded with other support requests so they can be tracked to resolution. A dedicated accessibility contact is a required item in the administrator checklist.

5. Ongoing work

Planned checks include keyboard navigation through sign-in and checkout, focus visibility on every interactive control, contrast measurement on the dark surfaces, labels for icon-only controls, and a reduced-motion preference.

Where a significant issue is found, it is fixed in the product rather than only described in this statement.

Questions, choices and requests

Back to OddsButter