Accessibility statement

Conformance target

Our goal is WCAG 2.1 Level AA. We test key templates and user flows during development and remediation work. Because the site includes legacy static content alongside newer Next.js pages, conformance may vary by section until remediation is complete.

Feedback and contact

If you encounter a barrier on subrosacyber.com — for example, keyboard navigation, contrast, screen reader labels, or form errors — please tell us. Include the page URL and a short description of the issue so we can reproduce it.

Known limitations

• Legacy blog and service pages

  Thousands of older static pages are being updated incrementally. Shared navigation and footer components are prioritized; individual legacy posts may not yet reflect every accessibility improvement.

• Third-party embeds

  Some pages load third-party widgets such as analytics, scheduling, or consent tools. We choose vendors with accessible products where possible, but cannot fully control their interfaces.

• PDF and document downloads

  Downloadable files may not always include accessible structure or alternative formats. Contact us if you need a specific document in another format.

Remediation process

1. We log accessibility feedback with the page URL, assistive technology (if provided), and severity.
2. Critical barriers that block access to core content or forms are prioritized as P1 fixes.
3. Fixes ship through the shared component system or the Next.js app, then propagate to exported locale builds.
4. We re-test affected templates after deployment and update this statement when scope or conformance changes.