Skip to main content

Accessibility Statement

Last reviewed: May 16, 2026 · Daruma Tech LLC

1. Our commitment

OctoComply is built to help organizations meet WCAG 2.1 Level AA conformance. We hold ourselves to the same standard we ask our customers to meet. Accessibility is not a feature we ship — it's a property of every page we publish.

If any part of this site is not accessible to you, we want to know. See section 7 for how to report issues.

2. Conformance status

We aim for full conformance with WCAG 2.1 Level AA — the same technical standard adopted by the DOJ Title II ADA Web Accessibility Rule (28 CFR Part 35) and the HHS Section 504 Web Accessibility Rule (45 CFR Part 84).

Status as of May 16, 2026: Partial conformance. The marketing site (octocomply.com) and authenticated app (app.octocomply.com) are designed and built against WCAG 2.1 AA criteria. The site has not yet completed third-party accessibility audit. Self-audit findings are tracked in section 4.

3. Technical specifications

The site is built with:

  • Next.js 14 (React) with server-rendered HTML
  • Tailwind CSS for layout and styling
  • Inter font family from Google Fonts
  • No JavaScript framework overlays or accessibility shims
  • Semantic HTML5 elements throughout (header, nav, main, section, article, footer)

4. Known limitations

We track known accessibility issues and remediation timelines openly. Current known limitations:

  • Third-party content (Google Analytics): We use Google Analytics for aggregate marketing-site analytics. The GA script is loaded with the standard async strategy and does not inject visible UI, but its presence is a third-party dependency we don't fully control.
  • Third-party content (Google Fonts): The Inter font family is loaded from Google Fonts. If Google Fonts is unavailable, the site falls back to system sans-serif fonts — readable, but visually different.
  • Knowledge base content rendering: Knowledge base articles are loaded from a backend API. If the API is unreachable, the KB index shows a "coming soon" empty state rather than article content. This is graceful degradation, not a conformance issue, but worth noting.
  • Decorative emoji rendering: Several pages use emoji characters (📄 📊 🏥) as visual decoration. These are marked with aria-hidden="true" so screen readers skip them. Visual rendering depends on the user's OS and browser emoji font.

5. Assessment methodology

We use the same methodology we describe in our Certification Methodology for our customer-facing remediated documents:

  • axe-core 4.10 (Deque) — WCAG 2.0/2.1/2.2 AA automated rules
  • Google Lighthouse 12 — Accessibility category audit
  • pa11y / HTML_CodeSniffer — WCAG 2.1 AA via independent ruleset
  • Playwright (Chromium) — Reflow, focus, color-only conveyance, touch targets
  • Manual keyboard navigation testing on primary user flows

We are pursuing third-party accessibility audit. Audit date and findings will be published here when complete.

6. Compatibility

The site is designed to work with:

  • Recent versions of Chrome, Firefox, Safari, and Edge
  • Screen readers: NVDA, JAWS, VoiceOver, TalkBack
  • Keyboard-only navigation
  • 200% browser zoom
  • Reduced-motion preferences (we respect prefers-reduced-motion)
  • Mobile devices (iOS Safari, Android Chrome)

The site has not been tested on every combination of browser and assistive technology. If you encounter issues with a specific combination, please report them — we will fix them.

7. Reporting issues

If you encounter accessibility issues, content that is hard to access, or anything that doesn't work the way you expect, please report it. We respond to every report.

Email

accessibility@octocomply.com

Include: the URL of the page, what you were trying to do, what happened, and (if applicable) the browser and assistive technology you were using.

We commit to acknowledging your report within 2 business days and providing a remediation timeline within 5 business days.

8. Formal complaints

If you are not satisfied with our response and we are a covered entity under applicable law, you may file a complaint with the appropriate authority:

Note: OctoComply itself is a private SaaS provider; whether ADA Title II / Section 504 apply to interactions with our site depends on your role. This section is provided for transparency.

9. Updates to this statement

We update this statement whenever there is a material change to the site's accessibility characteristics — including after third-party audits, after remediation of known limitations, or when new known limitations are identified. The "Last reviewed" date at the top reflects the most recent review.