Accessibility
Accessibility statement.
We want 0arch.io to work for everyone, including people using a screen reader, keyboard-only navigation, or browser zoom. Here's where things actually stand.
Last updated · September 6, 2026
Our goal
0ARCH aims for 0arch.io to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the common standard for a website being usable by people with a range of disabilities. We have not had a formal, third-party audit performed, and we don't claim the site is fully compliant today. This page describes what we've actually done and what we know still falls short, and we'll keep updating it as that changes.
What we've done
- Built the site with semantic HTML (real headings, lists, links, and buttons) so screen readers can move through it in a sensible order.
- Made every interactive element reachable and usable from a keyboard alone, with a visible focus outline so you can see where you are.
- Checked our text and background colors against the WCAG AA contrast ratios.
- Added text alternatives to meaningful images; purely decorative images and animations are hidden from screen readers.
- Respect your operating system's reduced-motion setting: if you have "reduce motion" turned on, the site's sketch animations and transitions turn off or simplify.
- Respect your browser's or device's text-size setting instead of locking in a font size that can't be resized.
Known limitations
Some parts of the site are harder for us to fully control:
- The chat assistant in the corner of the screen is a dynamically updating widget. We've made it operable by keyboard, but it may not behave perfectly with every screen reader.
- The payment form on the order page is built and rendered by Stripe inside an embedded frame. Its accessibility is Stripe's responsibility rather than ours, though Stripe also targets WCAG AA.
- A few decorative sketch animations are visual flourishes. We hide them from assistive technology and suppress them under reduced motion, but if you find one that isn't fully suppressed, tell us and we'll fix it.
We're working through issues like these as we find them, not treating this list as final.
Feedback
If you run into an accessibility barrier anywhere on 0arch.io, email support@0arch.io with the page and what happened, and we'll get back to you within 5 business days.
Formal complaints
If you feel a problem hasn't been resolved, contact us the same way first, at support@0arch.io, so we have a real chance to fix it before you take it further.