Legal Accessibility Statement

01The standard we conform to

We design and build cruxdata.io to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium (W3C) and adopted as ISO/IEC 40500:2025. WCAG 2.2 AA is the operative technical standard for U.S. Title III web accessibility and is broadly recognized by courts and enforcement agencies as the baseline for private-sector website accessibility.

Where we are not yet in full conformance, we identify the gap honestly under "Known limitations" below and work actively to close it.

02What we’ve done

Concrete measures implemented on cruxdata.io:

• Semantic HTML and landmark regions. Every page uses proper <header>, <nav>, <main>, and <footer> landmarks with descriptive labels so assistive technology can navigate reliably (WCAG 1.3.1, 2.4.1).
• Skip-to-main-content link. The first focusable element on every page bypasses navigation for keyboard users (WCAG 2.4.1).
• Visible focus indicators on every interactive element using :focus-visible, meeting the WCAG 2.2 requirements for Focus Not Obscured (SC 2.4.11) and Focus Appearance (SC 2.4.13).
• Keyboard operability. Every interactive element is reachable and operable with a keyboard alone (Tab, Shift+Tab, Enter, Space, Escape, arrow keys where appropriate).
• Modal dialogs use role="dialog", aria-modal="true", focus is moved into the dialog on open and returned to the trigger on close, and Escape dismisses the dialog (WCAG 2.1.2, 4.1.2).
• Interactive tiles used as buttons carry role="button", tabindex="0", keyboard handlers for Enter and Space, and aria-pressed / aria-checked state that updates as the user interacts (WCAG 4.1.2).
• Mobile menu uses aria-expanded, aria-controls, and closes on Escape (WCAG 4.1.2).
• Theme toggle is a real <button> with an updating aria-pressed and aria-label.
• Form fields have explicit <label> associations, use autocomplete tokens where relevant, and errors are announced (WCAG 1.3.1, 3.3.1, 3.3.2).
• Color contrast meets or exceeds 4.5:1 for body text and 3:1 for large text and UI components, verified in both light and dark themes (WCAG 1.4.3, 1.4.11).
• Target size. Interactive targets are at least 24×24 CSS pixels, meeting WCAG 2.2 SC 2.5.8.
• Decorative icons and SVGs carry aria-hidden="true" and focusable="false" so they aren’t announced or focused (WCAG 1.1.1).
• Reduced motion respected. Animated backgrounds, gradients, and transitions are minimized or eliminated for visitors whose system requests reduced motion via prefers-reduced-motion (WCAG 2.3.3).
• Consistent help. Contact information and the accessibility link appear in the same footer location on every page (WCAG 2.2 SC 3.2.6).
• Language attribute. Every page declares <html lang="en"> (WCAG 3.1.1).

03Testing methods

We test using automated and manual methods on every significant site update:

• Automated: Chrome DevTools Lighthouse (accessibility score), axe DevTools browser extension, WAVE (wave.webaim.org).
• Manual: Full keyboard-only walkthrough of every page. Screen-reader spot checks with NVDA (Windows) and VoiceOver (macOS/iOS). Manual contrast checks in both themes.
• Prefers-reduced-motion: Verified via OS motion settings on Windows and macOS.

04Overlays and one-click solutions

We deliberately do not use accessibility overlays such as accessiBe, UserWay, EqualWeb, or similar. In 2024–2025 the U.S. Federal Trade Commission finalized an enforcement action against a leading overlay vendor for deceptive claims about WCAG compliance, and hundreds of sites running overlays have themselves been sued for the accessibility barriers the overlays failed to fix. Instead, we build accessibility into the site itself.

05Known limitations

We’re honest about where we’re still working:

• Some third-party embeds (such as our form processor, Formspree) are outside our direct control. If you cannot complete a form for any reason, please email us and we will accept your inquiry that way with no loss of information.
• Some decorative animated graphics on marketing pages (such as the orbital “tool hub” illustration on the home page and the chiropractic vertical page) are purely visual; the key information they convey is duplicated in adjacent text.
• Very old browser versions may not render every feature accessibly. We aim to support the two latest versions of Chrome, Edge, Firefox, and Safari.

06Compatibility

cruxdata.io is designed to be compatible with:

• Chrome, Edge, Firefox, and Safari (latest two versions)
• Screen readers: NVDA, JAWS, VoiceOver, TalkBack
• Voice control and switch-control input methods
• Keyboard-only navigation
• OS-level accessibility features including high-contrast mode, zoom to 200%+, and reduced-motion preferences

07Third-party content

Some content on the site is provided by third parties (our form processor, embedded analytics scripts, embedded media if any). We do not directly control the accessibility of third-party content, but we advocate with vendors for improvements and we will accept your inquiry through any accessible alternative when a third-party barrier is present.

08Reporting a problem or requesting an accommodation

09Formal complaints

If you are not satisfied with our response to an accessibility concern, you may file a complaint with the U.S. Department of Justice Civil Rights Division under Title III of the Americans with Disabilities Act at ada.gov. California residents may additionally file a complaint under the Unruh Civil Rights Act. We would much rather hear from you directly first so we can fix the issue.

10Ongoing review

We review this statement and our accessibility practices on every significant site update and at minimum quarterly. The “Last reviewed” date at the top of this page reflects our most recent review.

11Contact for this statement

Questions about this statement or Crux Data’s accessibility program:
accessibility@cruxdata.io