Accessibility
What we test, and what we have not
NextCall targets WCAG 2.1 Level AA. Everything claimed below is checked automatically on every change, and the limitations are named rather than left out.
The standardWCAG 2.1 Level AA, checked by automated tests on every change across twelve pages at two viewports. A failure blocks the change.
Web Content Accessibility Guidelines 2.1, Level AA. Conformance is checked by automated tests that run against a real browser on every change, across twelve pages at both a desktop and a mobile viewport. A failure blocks the change.
What is checkedRule scan, measured contrast, reflow at 320px, reduced motion, 44px targets, visible focus, current-page announcement and live regions.
- Rule scan
- An automated audit at Level AA across the landing page, Today, Results, Leaderboards, Archive, Rules, Profile, Settings and these four supporting documents, at 1280px and 393px
- Contrast
- Computed, not eyeballed. Body text is held at 4.5:1 and interface boundaries at 3:1, with translucent layers composited against the surface actually behind them
- Reflow
- No horizontal scrolling is required at 320 pixels wide, the width the reflow criterion names
- Reduced motion
- With the operating system setting on, no animation is left running — including the loading placeholder, which repeats forever if the rule misses it
- Targets and focus
- Every navigation target is at least 44 by 44 pixels, and keyboard focus is visible against the page surface
- Current page
- Exactly one navigation item is announced as the current page to assistive technology
- Live regions
- Recording an answer is confirmed both in visible text and through a polite live region
The contrast check is a measurement rather than a rule scan. Where an automated audit cannot resolve which surface sits behind a piece of text — over a gradient, or inside a semi-transparent panel — the real ratio is computed and checked instead of being skipped. It has already caught one genuine fault this way.
What is not coveredNo specialist audit and no assistive-technology user testing yet. No screen reader has been driven through the game by hand.
Automated checks catch a real but partial share of accessibility problems. These are the gaps we know about, stated plainly rather than omitted.
- No audit yet
- NextCall has not been audited by an accessibility specialist, and no assistive-technology user testing has been carried out
- Screen readers
- Structure, names and roles are checked automatically, but no screen reader has been driven through the game by hand
- Cognitive load
- Reading level, time pressure from deadlines, and the clarity of resolution rules have not been assessed
- The editorial console
- The staff-only console at /admin is outside the tested set and is not held to this standard
- Advertising
- Ad content is supplied by a third party and is not under our control. Ads never gate or obscure a question
Reporting a barrierSend a message and choose the accessibility topic. No account needed, and no address required unless you want a reply.
If something here is unusable for you, please tell us — a report about a real barrier is worth more than any of the checks above. Send a message and choose the accessibility topic. You do not need an account, and you do not need to leave an address unless you want a reply.
Please say what you were trying to do, what happened instead, and what you were using — browser, device, and any assistive technology. Any of those is useful on its own; none of them is required.
A reply is not automatic. NextCall is a small operation and there is no staffed support desk — but reports are read, and an accessibility report is the kind that gets acted on first.