Accessibility statement
We want this site, and the dashboards we build, to work for everyone who needs to read them, including people who use a screen reader, a keyboard instead of a mouse, or high zoom. This page says what we aim for, what we have checked, what we know falls short, and how to tell us about a problem.
Last reviewed 5 October 2026
Our target
The Web Content Accessibility Guidelines (WCAG) 2.1, level AA, for this website and for the public pages of anything we build.
Where we stand
We work toward that target and check against it. We do not claim full conformance, because automated tools catch only part of what WCAG asks and parts of this site have not had a full manual review.
Found a problem?
Tell us what page and what got in the way. We reply within one business day. Details are below.
What we have checked
On 5 October 2026 our home page scored 100 out of 100 in the accessibility audit in Google Lighthouse, an automated tool. An automated score is a floor, not proof: it cannot tell whether link text makes sense out of context or whether a chart's meaning survives without colour.
- Menu links show a visible focus outline when you move through them with the keyboard.
- Pages are checked at phone width (390 pixels) for content that runs off the side of the screen.
- The charts on our police demo each carry a table view with the same numbers, so the figures can be read without the chart.
What we know falls short
- The same audit, run on other pages on 5 October 2026, flagged links set in running text that are told apart from the words around them by colour only, and a list of blue links on a light background that falls below the contrast ratio for normal-size text.
- Some older buttons on inner pages use a blue fill that is below the AA contrast ratio for their white label text. Newer pages use a darker fill that passes.
- Screenshots of dashboards on some service pages are captured at desktop size. On a phone they show the layout rather than readable numbers; the live demos themselves adapt to the screen.
- Some downloadable PDFs have not been checked with a screen reader.
How client dashboards are checked
Most of what we build is Power BI, and dashboards bound for a public website are judged on accessibility like any other public page.
Power BI can't fully meet WCAG 2.1 AA, so we don't promise conformance; we tell you where you stand. Before a dashboard is handed over, it gets an automated rule check over the report file (alt text on every visual, colours from the agreed palette, named pages) and a manual pass for the things a rule check misses: the order the keyboard moves through the page, colour contrast in the data colours as well as the text, and a table alternative for charts the public will read.
What still falls short goes into a written list with the handoff, so your team knows what it is publishing. Public agencies working toward the federal web accessibility rule can also buy that check on their existing dashboards and statistics PDFs as a separate piece of work; it is described on our crime statistics page.
Report an accessibility problem
Tell us the page address, what you were trying to do, and what got in the way. If it helps, say what browser or assistive technology you use. We reply within one business day, and if we can fix it, we say when.
If you need something on this site in another format, ask and we will try to provide it.