Accessibility Statement

1. Commitment to Digital Accessibility

At Openrize, we believe business software and digital systems should be accessible to all operators, regardless of ability or technology stack. We are actively committed to ensuring that our public website and proprietary platforms conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA standards.

2. Concrete Accessibility Measures Implemented

To ensure an inclusive digital experience, the following engineering controls are implemented site-wide:

A. Keyboard Navigation & Focus Management

• Skip-to-Content Link: A high-visibility skip link is mounted as the first focusable element, allowing keyboard operators to bypass repetitive navigation and jump directly to #main-content.
• Prominent Focus Rings: High-contrast focus indicators (:focus-visible) are applied universally across buttons, links, inputs, and controls with a 2px offset.
• Dialog Focus Trapping: Interactive modals (Cookie Preferences, Tell Us Your Challenge) feature strict focus trapping, initial auto-focus, focus restoration upon closing, and dismissibility via the Escape key.
• Scroll Margin Protection: All in-page section anchors define a scroll-margin-top: 100px rule to prevent our fixed header from occluding headings or focused elements.

B. Visual Design & Contrast

• Contrast Compliance: Text-to-background contrast ratios equal or exceed 4.5:1 for body copy and 3.0:1 for large display headings.
• Touch Target Size: Interactive touch targets meet or exceed the minimum 44 × 44 CSS pixel recommendation.
• Reduced Motion Respect: All CSS keyframe animations and decorative grid movements respect the operator’s prefers-reduced-motion: reduce system preference.

C. Screen Reader Semantics & Forms

• Single Authoritative Landmark: Every page renders exactly one top-level <main id="main-content"> landmark.
• Logical Heading Hierarchy: Heading levels (H1 through H4) follow a structured tree without skipping levels.
• Programmatic Error Association: Form validation failures automatically shift focus to the first invalid field and announce errors via aria-describedby.
• Label in Name: All icon buttons and call-to-action controls include accessible names that match or contain visible text (WCAG 2.5.3).

3. Continual Verification & Testing

We verify our accessibility implementations using both automated tooling (axe-core, Lighthouse accessibility audits) and hands-on manual keyboard navigation across Edge, Chrome, Firefox, and screen readers (NVDA, VoiceOver).

4. Feedback & Accommodation Requests

We welcome feedback on the accessibility of Openrize. If you encounter accessibility barriers, require alternative formats, or need assistance accessing any part of our platforms, please reach out to us: