Accessibility
Last measured: 25 August 2026, and again on 27 August 2026 when Iso split into a football site and a basketball site with their own colours.
The standard Iso holds itself to
Iso targets WCAG 2.2 Level AA on every page, on both the football site and the basketball site, in both themes, at every width down to 320px. In practice that means:
- Text contrast of at least 4.5:1, and 3:1 for text at 24px or larger (19px when bold).
- Contrast of at least 3:1 for anything that is not text but carries meaning — control borders, focus rings, icons, chart lines and chart marks.
- Touch targets of at least 44px. WCAG 2.2 asks for 24px; Iso uses the larger Apple Human Interface Guidelines figure, and 48px for the phone tab bar.
- A focus ring you can see on every control, and one that is never hidden underneath the tab bar, a toast or the cookie banner.
- Full keyboard operation — every control reachable, every dialog and drawer entered and exited, focus returned where you left it.
- Reduced motion honoured. If your device asks for less motion, every animation collapses to 1ms and charts do not animate at all.
- Nothing conveyed by colour alone, no horizontal scrolling at 320px outside a few named tables and maps that scroll on purpose, and results and toasts announced to a screen reader.
What was measured, and when
On 25 August 2026 every route was audited with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rule sets, for every kind of account, in both themes — 427 route, width and theme combinations — alongside a separate pass that computed the real contrast of every rendered text node.
The result, after the fixes that pass produced:
- Zero serious or critical violations on any rendered page. The one remaining automated hit is the refresh tag Next.js writes itself on a page that is redirecting you, which Iso does not control and which nobody sees.
- Zero text-contrast failures in either theme.
- 52 icon-only buttons, none of them unlabelled.
Automated tools only see what is on the screen when they run, so the audit was paired with a keyboard walk of every page and a read of every capture by a person. Three scrolling regions a keyboard could not reach were found that way, not by the tool — one of them because it sits inside a collapsed section the tool never opened.
On 27 August 2026 the two sites were given their own colours — a purple ground and a blue accent for football, a deep red ground and an orange accent for basketball, and no colour at all on the pages that belong to neither. Because that changes what every measurement above was taken against, the colours were re-measured rather than assumed: 44 route, width and theme combinations across both sites and every public page, with zero violations and zero text-contrast failures. Eight of those cells contain text sitting on a gradient, which an automated tool reports as “needs review” rather than as a pass; each was computed by hand and the lowest measured 5.07:1, against the 4.5:1 floor.
Where Iso falls short
One known problem, on phones, open by decision. It is listed here because you are more likely to meet it than to read about it anywhere else.
- Expanding a school match on a phone pushes the cards below it down the page. The explanation is four to six lines on a narrow screen, and it appears where you tapped. If you were reading the card underneath, it moves. Measured at 0.102 on the Cumulative Layout Shift scale at 375px, against 0.017 on a laptop — and the shift follows your own tap, which is why it stays: an expansion that pushed nothing below it would stop you comparing two cards.
A problem this page used to list is fixed: the play diagrams in both sites’ IQ modules no longer shrink their labels on a phone — the diagram keeps its full-size drawing and scrolls sideways instead, and the scrolling region works from the keyboard.
Tell us what you find
If any part of Iso is hard or impossible for you to use, email support@isoathletes.com and a person answers within 1 business day (Monday–Friday, 9am–5pm PT) — the same promise the support page makes.
Tell us the page, what you were trying to do, and what you use to browse — a screen reader and its version, keyboard only, a magnifier, a particular text size. That is usually enough for us to reproduce it. A report about something this page already admits is still worth sending: it tells us how much the problem is costing.