Accessibility

On October 17, 2026 (2026-10-17) an automated static audit was run on 34 public pages of this site (45 renders: pages that change when you sign in were checked signed out and signed in). Each page was rendered on the server and its markup checked against 21 rules modelled on the axe-core 4.11 rule set (form labels, button and link names, image text alternatives, list and heading structure, hidden-but-focusable content, page language). The checker is the project's own re-implementation of those rules for markup; it is not axe-core itself and not a browser. It runs on every change in continuous integration.

Rendered with react 19.3.0, next 15.5.28.

On October 18, 2026 (2026-10-18) a second automated audit ran axe-core 4.13.0 in a real browser (Chromium 156.0.8078.4), at desktop and phone sizes, on 40 public pages and page states, including a single recording, battery report and site report in their demo or signed-out form. It checks the WCAG 2.0, 2.1 and 2.2 level A and AA rules axe can decide, colour contrast among them, on each page as it first appears and again after one interaction (opening the menu, switching a demo control, submitting an empty form). It also presses Tab from the top of each page and checks that focus moves forward and is visibly marked. It runs on every change in continuous integration.

In the markup audit, across all audited pages: 0 critical, 0 serious, 9 moderate and 0 minor findings. On the sign-in, sign-up, terms, Battery Watch, GIC, recordings and replay pages (/signin, /signup, /terms, /battery, /gic, /my, /replay, /accessibility) there are 0 critical or serious findings; a new one fails the continuous-integration check.

In the browser audit: 0 critical and 0 serious findings (0 elements), 0 moderate and 0 minor. Its first run found 1305 elements with critical or serious problems, mostly text too faint against the dark background; those were fixed before this audit was recorded. On the core pages there are 0; on any page, a new one fails the continuous-integration check. The keyboard check passed on every page.

• heading-order (moderate) on /battery, /gic
• page-has-heading-one (moderate) on /dashboard

The automated audits cannot see everything. Not yet checked:

• Colour contrast by eye. The browser audit measures text contrast automatically; text over images, maps and gradients, and the contrast of focus outlines and other non-text elements, have not been measured.
• Keyboard-only use (focus order through a whole page, operating every control, no traps inside maps or charts). Only the first stops of each page are checked automatically. Not yet tested by hand.
• Screen readers (VoiceOver, NVDA, TalkBack). Not yet tested by hand.
• Most states a page reaches after you interact with it or after data loads (dialogs, live readings, a real account's data). The browser audit checks one interaction per page.
• Pages for a single recording, report or site (/battery/recordings/[id], /battery/recordings/[id]/report, /power/[site]/report, /replay/[id], /survey/sessions/[id]/report) with real data: only their demo or signed-out form was checked.
• /survey/sessions/[id]/report: not audited in the browser either, because the showcase has no demo survey session: ?demo=1 renders only "not available on this server", not the report.
• Zoom to 400 %, and Safari on iPhone and iPad (the browser audit runs Chromium only).
• Maps and charts, which show information visually; their text alternatives have not been reviewed.

The markup checker's own list of what it cannot decide: color-contrast; keyboard / focus order / focus visible; screen-reader behaviour; post-interaction states; document-title.

If something on this site is hard or impossible to use with your setup, please tell us: which page, what you were trying to do, and the browser or assistive technology you use. Write to the address on the sign-in email you received, or use the contact details in the privacy policy.

This statement is about the NextMAG product. The company name in the footer below comes from the frame this site shares with the sign-in and terms pages; which legal entity operates the service has not been settled yet.