accessibility statement
Preview build. These documents are drafts pending review by counsel and are not legal advice. Numbers and terms may change before launch.
getDARC's commitment to accessible design, our WCAG 2.2 Level AA target, known gaps, and how to reach us for help.
1. Our commitment
getDARC is built to be usable by everyone, including people who rely on assistive technology. Accessibility is a design requirement here, not an afterthought bolted on at the end.
Our conformance target is the Web Content Accessibility Guidelines (WCAG) version 2.2, Level AA. We treat the core commerce flows, browse, configure, and checkout, as the paths that must meet this bar first and stay there.
2. Measures we take
We build with semantic HTML and accessible component primitives from Radix UI, so structure, roles, and states are exposed to assistive technology by default rather than reconstructed after the fact.
Concretely, we verify color contrast of at least 4.5 to 1 for body text, ensure full keyboard operability of interactive elements, provide a visible focus indicator, support screen readers, and honor the prefers-reduced-motion setting so no animation blocks a task for people who reduce motion.
3. Assistive technologies we test with
We test against widely used assistive technology and configurations rather than assuming conformance from automated checks alone.
Our testing covers screen readers across desktop and mobile, keyboard-only navigation, browser zoom and reflow, and the operating-system reduced-motion and contrast settings.
4. Known limitations
We are honest about where we fall short. Some third-party embeds and dense data visualizations, such as detailed performance charts and comparison tables, may not yet fully meet our WCAG 2.2 AA target.
These gaps are tracked and being remediated. If you hit a barrier in one of these areas, please tell us so we can prioritize a fix and offer you the information another way in the meantime.
5. Request an accommodation or report a barrier
If you encounter an accessibility barrier, or need information or a transaction completed in a different way, contact [email protected] and describe the page and the problem.
We acknowledge accessibility reports promptly and work with you toward a resolution, including an accessible alternative while a permanent fix is in progress.
6. Standards and future scope
Our WCAG 2.2 Level AA target also pre-satisfies the accessibility standard of the European Accessibility Act, so an eventual expansion into the EU is a matter of confirmation rather than a rebuild.
Status note: this is a preview draft under legal review. It is not legal advice, and specific terms may change before publication.