Your health dashboards have two deadlines.
ADA Title II (opens in a new window) requires WCAG 2.1 AA for local government web content by April 26, 2027. The HHS Section 504 rule (opens in a new window) requires the same of HHS funding recipients by May 11, 2027. Embedded BI dashboards make both hard. We built the alternative.
Whoever you are in this decision, the current setup is working against you.
For the health director
You own the compliance risk and the public's trust.
Two federal deadlines now apply to your public dashboards, and the community judges your department by whether it can find last week's flu numbers on a phone. Both land on your desk.
For the epidemiologist
You became a dashboard administrator against your will.
Licenses, extracts, workbook permissions, refresh failures at 7 a.m. The tooling was built for corporate BI, not disease surveillance, and every accessibility complaint routes back to you.
For the public information officer
In an emergency, the public has to understand the data in seconds.
A pinch-zoomed dashboard with hover-only numbers does not work in a press conference or on a worried parent's phone. Plain language and visible values are not polish; they are the job.
Don't take our word for it. Click a district.
This is not a screenshot. It is the product's own epi curve and district chart running on this page against the demo county's data, cross-filtering, prior-season overlay, and keyboard access included.
This isn't optional. Here's the legal landscape.
- ADA Title II web rule. WCAG 2.1 AA for state and local government web content, large entities by April 26, 2027. Health departments are squarely covered. DOJ, April 2024 (opens in a new window)
- HHS Section 504 rule. The same WCAG 2.1 AA standard for recipients of HHS funding, by May 11, 2027. Most health departments receive HHS funds, so both rules apply. HHS, 2024 (opens in a new window)
- Section 508. The federal accessibility baseline for technology bought or built with federal money. Rehabilitation Act (opens in a new window)
- Small-cell privacy. Surveillance data carries stricter small-number privacy expectations than almost any other public data. Suppression and reliability flags must be built in, not remembered. NCHS standards (opens in a new window)
Your department already produces 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 health 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, where the public actually reads it
- Small-cell suppression left to analysts
- Counts under 11 suppressed and unstable rates flagged, automatically
- Hover to see any value
- Values visible by default, in plain language
- Screenshots emailed around
- 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
- Walk an epi curve by keyboard alone
- Cross-filter a page from the district map
- Open it on your phone, no pinch-zoom required
- See small counts suppressed automatically
- Check any chart's update cadence and as-of date
- Toggle any chart into a data table
- Look up a single restaurant's inspection
- Share a filtered view as a plain URL
See it as your community would.
The demo county is fictional. The architecture is not.
Look for the demo bar at the top of the portal to find your way back.