Your city's dashboards have a deadline.
The DOJ's ADA Title II rule requires WCAG 2.1 AA for city and county web content by April 26, 2027, and your public dashboards are web content. Embedded BI tools make that hard. We built the alternative.
Whoever you are in this decision, the current setup is working against you.
For the CIO or CDO
You own the deadline for every department's dashboards.
Finance embeds one BI tool, police another, public works a third. Every one of them is web content under the new rule, and every one of them is your problem by April 2027.
For the city manager
Council was promised transparency. Residents got pinch-zoom Tableau.
The transparency page exists, technically. It is also unusable on the phones most residents actually open it with, and everyone in the council chamber knows it.
For the communications director
Residents ask on Facebook. The answer should be a link that works.
Where did my taxes go, when is my street getting fixed, is crime actually up? Each deserves a link that loads fast, reads plainly, and works on a phone in a parking lot.
Don't take our word for it. Click a bar.
This is not a screenshot. It is the product's own chart components running on this page against the demo city's budget, cross-filtering, labeling, and keyboard access included.
This isn't optional. Here's the legal landscape.
- ADA Title II web rule. WCAG 2.1 AA for city and county web content and apps, large entities by April 26, 2027. Your public dashboards are web content. DOJ, April 2024 (opens in a new window)
- Section 504. The same accessibility bar wherever federal dollars fund programs, which in a city is nearly everywhere. Rehabilitation Act (opens in a new window)
- State transparency laws. Virginia and most states already require open checkbook and public records access; publishing well is the part that is optional. Va. FOIA (opens in a new window)
- Open data commitments. Council resolutions and open data policies promise the public usable data, not a PDF in a portal. Policy practice (opens in a new window)
Your city already assembles every one of these datasets. The only question is how well you publish them.
How this is different
The old way
This way
- Viewer licenses for public data
- Open web, no seats, no logins
- Accessibility retrofitted, VPAT caveats
- WCAG 2.1 AA in the architecture, every chart with a table alternative
- Desktop dashboards shrunk onto phones
- Designed for the phone first
- A budget PDF nobody opens
- A budget anyone can drill from total to line item
- Screenshots emailed to council
- Every filtered view has a shareable URL
- Black-box embed
- Your brand, your domain, your design system
Take the tour
Eight things to try in the demo
0 of 8 tried
- Cross-filter the whole budget with one click
- Drill from the $214M total down to a line item
- Flip the budget to dollars per resident
- Find the project that is honestly over budget
- Browse 311 requests like a service log
- Open it on your phone, no pinch-zoom required
- Navigate a chart by keyboard alone
- Meet the small-count privacy suppression
See it as your residents would.
The demo city is fictional. The architecture is not.
Look for the demo bar at the top of the portal to find your way back.