Your public dashboards have a deadline.
Federal law now requires public institutions' web content, including every public-facing dashboard, to meet WCAG 2.1 AA by April 26, 2027. 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
Per-viewer licensing for a public website.
You are paying seat costs so the public can see data the law requires you to publish. Every viewer of a public dashboard is a person the license meter counts.
For the accessibility officer
Retrofitting WCAG 2.1 AA onto an embedded BI tool is a losing fight.
You own the compliance risk for an interface you cannot change. The vendor's VPAT has caveats; the OCR complaint will not.
For communications and IR
Most families will open this on a phone.
Pinch-zooming a desktop dashboard is the first impression they get of your institution. It reads as neglect, whatever the data says.
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 institution's data, 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 public institutions' web content and apps, large entities by April 26, 2027. DOJ, April 2024 (opens in a new window)
- Section 508. The same standard across the federal government and federally funded technology. Rehabilitation Act (opens in a new window)
- Student Right-to-Know. Every institution must disclose completion and graduation rates. 34 CFR 668.45 (opens in a new window)
- HEA consumer information. Required disclosure of costs, aid, enrollment, retention, and outcomes. 34 CFR Part 668, Subpart D (opens in a new window)
- IPEDS reporting. Annual federal reporting of enrollment, completions, finances, staffing, and aid. Statutory requirement (opens in a new window)
- Net price calculator. Families must be able to estimate their real cost, not the sticker price. HEOA (opens in a new window)
Your institution 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
- Hover to see any value
- Values visible by default
- 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
- Cross-filter a whole page with one click
- Open it on your phone, no pinch-zoom required
- Navigate a chart by keyboard alone
- Toggle any chart into a data table
- Download exactly the filtered view you built
- Share a filtered view as a plain URL
- Turn on reduced motion and watch it respected
- Meet the small-population privacy suppression
See it as your students would.
The demo institution is fictional. The architecture is not.
Look for the demo bar at the top of the portal to find your way back.