Accessibility

Accessibility Statement

Last updated: May 18, 2026

Obsidian Ridge is committed to making this website usable by everyone, including people who rely on assistive technology. This statement explains the standard we work toward, the current state of conformance, known limitations, and how to ask for an accessible alternative or report a barrier.

1. Conformance target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. The Site is also designed to comply with applicable provisions of the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, and the European Accessibility Act 2025 to the extent they apply to a small US-based business.

2. What we do

• Use semantic HTML so screen readers can navigate page structure by landmark and heading.
• Provide a skip-to-content link at the start of every page for keyboard users.
• Maintain color contrast that meets or exceeds WCAG 2.2 AA on body text and interactive controls in our obsidian-and-amber palette.
• Label every form field with a visible, programmatically associated label.
• Use focus-visible outlines so keyboard users always know which element will receive input.
• Use descriptive alt text on meaningful images and decorative-only attributes on icons.
• Avoid content that flashes, auto-plays audio, or moves automatically in ways that could trigger seizures or vestibular reactions.

3. Known limitations

We test in current versions of Chrome, Edge, Firefox, and Safari with VoiceOver, NVDA, and keyboard-only navigation. Limitations we are aware of:

• Interactive reels (the embedded explainer animations under /reels/*) use real-time JSX compilation. The non-animated text-based alternative for each reel is on the parent service page. If you reach a reel that does not have a clear text alternative on the surrounding page, contact us and we will publish one.
• The Phish or Real game (/phish-or-real) relies on point-and-click interactions. A keyboard-equivalent path exists, but voice-only navigation is not fully supported. Improvements are planned.
• Downloadable PDF reports from the assessment tool are generated dynamically and have not yet been audited for full PDF/UA conformance. If you need an accessible alternative format, email us and we will deliver a tagged PDF or HTML version.

4. Assistive technology compatibility

The Site is designed to work with:

• Recent versions of major screen readers: VoiceOver (macOS / iOS), NVDA (Windows), JAWS (Windows), TalkBack (Android).
• Keyboard-only navigation across all primary pages and forms.
• Browser zoom up to 200% without loss of content or functionality.
• Operating-system level dark-mode and reduced-motion preferences (our base palette is already dark; we honor prefers-reduced-motion on animations).

5. Ongoing testing

Each major release is checked against an automated accessibility tool (Lighthouse / axe-core) before deployment, and significant changes get a manual keyboard-and-screen-reader pass before going live. We treat accessibility regressions like any other bug.

6. Report a barrier or request an accessible alternative

If something on this Site is hard or impossible for you to use, please email security@obsidianridge.io with:

• The URL of the page where you encountered the problem.
• A short description of what happened and what you were trying to do.
• The assistive technology, browser, and operating system you were using, if known.

We aim to respond within two business days. If the issue is straightforward, we will fix it and confirm. If it requires more work, we will give you a timeline and offer an accessible alternative (text version, audio walkthrough, or direct conversation) in the meantime. There is no separate fee for an accessible alternative.

7. Feedback on this statement

We update this statement as the Site evolves. If anything here is unclear, missing, or inaccurate, send us a note at security@obsidianridge.io. See also our Privacy Policy, Terms of Use, and Refund & Cancellation Policy.