Accessibility
Accessibility
We check this site against WCAG 2.2 Level AA on every deploy. Here's what that covers, how we test it, and where we're not there yet.
Last updated
What we target
costmon.com targets WCAG 2.2 Level AA. That covers color contrast, heading order, keyboard access, and the usual list of things that make a page work with a screen reader or without a mouse.
We don't have a third-party VPAT yet. If a security or procurement review needs one, ask on the contact page and we'll get it sorted.
How we check it
Every build runs axe-core against every page on the site, with reduced motion turned on so a scroll animation mid-fade doesn't get flagged as a false contrast failure. The build fails on any serious or critical violation, and on any skipped heading level. That's a gate in CI, not a one-time audit, so a regression breaks the build the same day it ships rather than sitting there until the next review.
What we haven't done
Automated tools catch a lot of syntactic issues, not the experience itself. We haven't run a manual pass with a screen reader or voice control software. This page also only covers the marketing site: the CostMon dashboard your team logs into hasn't been through the same review yet. A few charts, like the Kubernetes cost breakdown, separate their segments with both color and a text legend, but we haven't checked them against every form of color blindness.
Found a barrier?
If something on this site doesn't work with your assistive technology, tell us. The contact page reaches a real person. Tell us the page you were on, what you were using, and what happened, and we'll look into it.