Accessibility Statement

TimingAX is built and maintained by a single independent developer. We want the site and app to be usable by as many people as possible, including people using screen readers, keyboard navigation, browser zoom, or other assistive technology. This page describes where things currently stand, honestly — including what isn’t fully there yet.

Our standard

We aim to meet WCAG 2.1 Level AA across the site. This is an ongoing goal we’re actively working toward, not a claim that every page fully conforms today.

What works well today

GOOD SUPPORT

All marketing pages (Home, About, Blog, Academy, Methodology, Changelog, Contact) use semantic HTML headings, are navigable by keyboard, and maintain a consistent dark colour scheme designed for strong text contrast.
The site respects your operating system’s reduced motion preference — scroll animations and transitions are minimised if you have this enabled.
Text throughout the site is resizable via your browser’s zoom controls without breaking layout.
Forms (contact, newsletter, sign-up) use labelled fields and show clear error and success states.

Where we know we have work to do

PARTIAL SUPPORT

Area	Current state
Interactive charts (seasonal calendar wheel, bar charts)	These are visual SVG/HTML elements. Screen readers can access the underlying numbers via the data tables and cards displayed alongside each chart, but the charts themselves don’t yet have full ARIA descriptions.
Colour as the only signal	Green/red is used to indicate positive/negative seasonal returns. This is paired with +/− signs and text labels (e.g. "Best Month", "Worst Month") so the information isn’t conveyed by colour alone, but we haven’t formally audited colour contrast ratios against WCAG AA across every chart state.
Complex tool interfaces (Backtest, Screener, Portfolio builder)	These multi-step tools are keyboard-operable but haven’t had a full assistive-technology walkthrough yet.
AI chat widget	Operable by keyboard and screen reader, but live-region announcements for new messages are still being refined.

How to report an accessibility issue

If you encounter a barrier using TimingAX — whether you use a screen reader, keyboard navigation, voice control, or any other assistive technology — please get in touch via our contact form. We read every message personally, and accessibility issues are treated as a priority. Please let us know:

The page or tool where you encountered the issue
What assistive technology and browser you were using
What you expected to happen, and what happened instead

Technical approach

The site is built with semantic HTML, standard form controls, and CSS that respects browser and OS-level preferences (reduced motion, font scaling). As new features are added, accessibility is considered as part of the build — not retrofitted afterward — though as a small independently-run project, some areas (noted above) are still catching up.

This statement reflects our current understanding and will be updated as improvements are made. It is not a legal certification of conformance.