Legal
Accessibility Statement
Last updated: 2026
Our commitment
Ribix is committed to making the web dashboard usable by everyone, including customers who rely on assistive technology such as screen readers, voice-control software, and keyboard-only navigation.
Conformance target
The Ribix web dashboard targets WCAG 2.1 Level AA across all launch-critical pages:
- Login and registration
- Onboarding flow
- GitHub App connection
- Dashboard overview, findings, and approval queue
- Billing and plan management
- Workspace settings and member management
Automated testing
We run automated accessibility checks using axe-core in our end-to-end test suite. These checks cover the marketing site and authentication pages on every pull request. Violations of WCAG 2.1 AA rules block merges.
Keyboard navigation
All interactive elements are operable via keyboard. We provide:
- A skip-to-content link as the first focusable element on every page.
- Visible focus indicators on all interactive components.
- Logical tab order that follows the visual layout.
- Escape-key handling for modals, the command palette, and the mobile navigation drawer.
Screen reader support
We use semantic HTML elements and ARIA attributes where appropriate:
- Landmark roles (main, navigation, header, footer).
- Accessible names for icon-only buttons via aria-label.
- Form inputs with associated label elements.
- ARIA live regions for dynamic status updates.
Color and contrast
Text and interactive elements meet WCAG 2.1 AA contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components). We do not rely on color alone to convey information.
Known limitations
While we strive for full conformance, the following areas may have limitations:
- The data-rich findings table has complex interactive rows that may require additional screen-reader testing with real users.
- Third-party embedded content (e.g., GitHub OAuth screens) is governed by the respective provider's accessibility statement.
- The web IDE surface is optimized for developers and may not fully conform to WCAG 2.1 AA.
Reporting issues
If you encounter an accessibility barrier, please email support@ribix.dev with the page URL and a description of the issue. We aim to acknowledge reports within two business days and provide a remediation timeline.