Accessibility Statement

Our commitment

Rayz Security is used to make governance decisions that carry real consequence, often under time pressure. That only works if the product is usable by everyone who needs to use it. We hold every screen we ship to WCAG 2.1 Level AA as the floor, not a pass done at the end of a project — contrast, keyboard access, and readable type are treated as load-bearing requirements during design and review, not a checklist run once before launch.

What this looks like in practice

• Color is never the only signal. Status and risk indicators (Critical, High, Medium, Low, and change-request states) always pair color with a text label or icon, so the information doesn't depend on color perception alone.
• Contrast is verified, not assumed. Body and placeholder text is held to at least a 4.5:1 contrast ratio, and large text to at least 3:1, against every background it can appear on.
• Every interactive element has a visible focus state. We use a consistent focus-visible outline across buttons, links, inputs, and custom controls, and we don't remove a focus outline without replacing it with an equally visible alternative.
• Keyboard access is a first-class path. Menus, modals, forms, and multi-step flows (like onboarding and change-request review) are built to be operable without a mouse.
• Motion respects your preferences. Animated transitions and reveal effects honor the prefers-reduced-motion setting; nothing essential to understanding a screen depends on an animation completing.

Known limitations

Accessibility is ongoing work, not a finished state. We test with automated tooling and manual keyboard and screen-reader passes on core flows, but as a fast-moving product we expect to find gaps — particularly in newer or less-trafficked areas of the app. If you encounter one, we want to know about it.

Third-party content

Some integrations (for example, Jira) redirect to or embed interfaces we don't control, and our accessibility commitment doesn't extend to those third-party surfaces. We choose integration partners with reasonable accessibility practices where we have a choice.

Report an accessibility issue

If you run into a barrier using Rayz Security, tell us what page you were on, what you were trying to do, and what assistive technology (if any) you were using — that context is the fastest way for us to reproduce and fix it. Reach us at accessibility@rayz-security.com.