Accessibility
Last updated 2026-07-07
This is an honest self-assessment by the team that builds the product. It has not been validated by an external accessibility audit, and it names known gaps rather than claiming conformance.
Our commitment
Orgsembletargets WCAG 2.1 Level AA. That target is written into the product's governing design rules, not bolted on afterward: every color token must clear AA contrast for text (4.5:1) and 3:1 for non-text marks, in both the light and the dark theme; every interactive element must be reachable and operable by keyboard; and no status may be encoded by color alone.
What is in place today
- A skip-to-content link is the first focusable element on every page, including in Safari, where plain links are otherwise not in the tab order.
- A single, consistent, visible focus ring on every interactive element; focus is never removed without a visible replacement.
- Light and dark themes whose text and border tokens are each contrast-checked against the AA text and 3:1 non-text bars.
- Status and meaning are never carried by color alone: colored marks sit beside their labels or a legend that decodes them, and updating numbers use tabular digits so values do not jitter.
- The chart editor honors the reduced-motion preference by making its camera moves instant.
- Forms use real labels, error text is announced with alert semantics, and pages carry landmark structure for screen readers.
Known gaps
Stated per the same honesty rule that governs the rest of the product:
- The chart canvas is pointer-first. Building and rearranging a chart (drag to reparent, marquee selection) is not yet fully operable by keyboard alone, and screen-reader coverage of the canvas itself is limited. The directory, list, and report views of the same data are keyboard-accessible alternatives.
- PNG and PDF exports are images of the chart and do not carry a text alternative; the CSV export of the same data is the accessible format.
- No formal third-party audit or VPAT exists yet, so conformance is a target we test against ourselves, not a certified claim.
Feedback
If you hit a barrier, tell us at hello@orgsemble.com and include the page and the assistive technology involved. Accessibility defects are treated as defects, not feature requests.