bigSIMPLE Development

Accessibility Statement

Last reviewed: July 31, 2026

Short version: We build with accessibility in mind across every Apex product, aim for WCAG 2.1 AA, and take reports of barriers seriously. This is an ongoing effort, not a finished audit.

Our Commitment

bigSIMPLE Development is committed to ensuring digital accessibility for people with disabilities across bigsimple.dev and the Apex product family (ApexAcumen, ApexWander, ApexDepths, ApexLeads, ApexStream). We continually work to improve the user experience for everyone and apply relevant accessibility standards as our products evolve.

Conformance Target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. This is our target standard, not a claim of full, verified conformance — see Testing Methodology below for what has actually been checked.

Measures Taken

  • Semantic HTML and ARIA landmarks used throughout page structure
  • Interfaces built to be keyboard navigable, with visible focus indicators on interactive elements
  • Color contrast checked against WCAG AA thresholds during design
  • Alt text provided on informational images
  • Responsive layouts that support browser zoom and text resizing

Known Limitations

Accessibility is an ongoing effort. Known gaps we're tracking include: some third-party embedded components (e.g., payment checkout flows, embedded maps) may not fully conform to WCAG 2.1 AA, since we don't control their markup directly. We haven't yet completed a comprehensive audit of every page across every Apex product. If you find a barrier not listed here, please tell us — see Feedback below.

Feedback

If you encounter accessibility barriers on bigsimple.dev or any Apex product, please contact bigsimpledevelopment@protonmail.com. We aim to respond within 5 business days.

Testing Methodology

This statement reflects a self-assessment by the developer, not a third-party audit. Testing performed to date has been manual: keyboard-only navigation checks and visual color-contrast review during design. Automated tooling checks (e.g., axe, Lighthouse) and dedicated assistive-technology testing (screen readers such as VoiceOver, NVDA, or TalkBack) have not yet been performed across all pages. We do not claim full WCAG 2.1 AA conformance until that verification work is complete.

Statement Date

Last reviewed: July 31, 2026