Accessibility

Two automated suites run against real, populated pages, not blank ones: one walks every marketing and documentation page from the same registry that drives the sitemap, so a page cannot be added without being audited; the other walks every page inside a workspace seeded with real products, alerts, cases and evidence, because an empty-state screen has never shown the layout a working account actually renders. Both check axe-core’s WCAG 2.x A/AA rule sets, that no page scrolls sideways at 320 pixels wide, that every page has exactly one heading level one with no level skipped, and that every control reachable by keyboard shows a visible focus ring.

As of the date above, both suites report zero serious or critical violations across every audited page. Moderate and minor findings are logged, not treated as blocking, and are worth fixing without holding up a release over them.

axe-core catches a large, well-studied slice of WCAG failures reliably and finds close to none of the rest: things like whether an instruction actually makes sense to someone using a screen reader, or whether a keyboard-only path through a multi-step flow is genuinely usable rather than merely reachable. A full manual audit, including real assistive-technology testing, has not been done. Automated passing is a floor, stated as one.

There is no address to write to yet, because the company is not registered. One will appear here the moment it is.