Accessibility Statement

1. Scope and target

This statement covers the bilingual public ROCSI website at rocsi.eu, including core navigation, research and project pages, ROCSI Build, Digital Resilience registration, Contact scheduling and the native legal/data-rights pages.

WCAG 2.2 Level AA is the release target. This statement is not an external certification and does not claim that every third-party interface used by ROCSI is fully conformant.

2. How we test

Accessibility is treated as a release gate rather than a one-time review. Testing combines automated checks with manual browser checks in Romanian and English, light and dark themes, keyboard-only navigation, visible focus, form labels and error recovery, semantic structure, colour contrast, reduced motion, responsive reflow and zoom.

A focused staging review on 21 September 2026 covered representative public routes at 320 CSS pixels and approximately 200% browser zoom, together with the current Build, Data Rights, workshop registration and Contact scheduling interactions. Representative screen-reader checks remain part of final release acceptance.

3. Current accessibility support

• localized skip links, landmarks and a single primary page heading on audited public routes;
• keyboard-operable navigation, theme and language controls, forms and primary actions;
• visible keyboard focus for interactive controls and focusable diagrams;
• programmatic labels and accessible names for audited form controls;
• field-level validation that identifies invalid fields and moves focus to the first error where applicable;
• responsive layouts designed to reflow without horizontal content loss at narrow widths and browser zoom;
• a reduced-motion mode that suppresses non-essential animation when the operating system requests it.

4. Known third-party limitations

ROCSI uses Cal.com for optional scheduling. The ROCSI page requires an explicit action before the scheduling frame loads and also provides a direct booking link. In our September 2026 review, the embedded Cal.com document did not expose a non-empty document title and its mobile viewport configuration disabled pinch zoom. These behaviours are controlled by the provider rather than ROCSI.

Protected public forms can use Cloudflare Turnstile. ROCSI labels the security-verification region and avoids replacing native form semantics, but the internal accessibility behaviour of the challenge itself is provided by Cloudflare.

5. Reporting an accessibility barrier

If you encounter an accessibility barrier on a ROCSI page, use the Contact page linked below and identify the page, the action you were trying to complete and, if useful, the browser or assistive technology involved. Please do not include sensitive personal information unless it is necessary to explain the problem.

If the embedded scheduling interface is itself the barrier, use the direct booking link exposed on the Contact page or report the issue during another available ROCSI interaction.

6. Review and improvement

ROCSI reviews accessibility again when production-critical routes or interactions materially change. Known issues are tracked in the website repository and are re-tested before production acceptance.