Skip to main content
RAENBI

Accessibility Statement

Accessibility Statement

Executive summary

  • This statement applies to the public pages published on raenbi.com.
  • RAENBI.com uses WCAG 2.2 Level AA as its primary accessibility benchmark and monitors EN 301 549 v3.2.1 for procurement and engineering reviews.
  • The site is currently partially conformant. Several accessibility controls are implemented and verified, but no independent full-site audit has yet been completed across every template, device class, and assistive-technology combination.
  • If you encounter an accessibility barrier, use the contact page or write to contact@raenbi.com.

Scope

This statement applies to the public corporate site published on raenbi.com. The site is used to present RAENBI's technical services, delivery model, and remote collaboration approach.

It does not automatically cover client environments, third-party platforms, externally hosted tools, or downloadable documents that may be published separately from the core site.

Accessibility benchmark

RAENBI uses WCAG 2.2 Level AA as the primary benchmark for new interface work and accessibility remediation on this domain.

For procurement-sensitive reviews and technical delivery contexts, RAENBI also monitors EN 301 549 v3.2.1 as the main European ICT accessibility reference.

The success criteria that the shared front-end system systematically targets include:

  • 1.3.1 Info and Relationships, 1.3.2 Meaningful Sequence — through semantic landmarks and heading structure
  • 1.4.3 Contrast (Minimum), 1.4.11 Non-text Contrast — through the project's design tokens
  • 1.4.12 Text Spacing, 1.4.13 Content on Hover or Focus
  • 2.1.1 Keyboard, 2.1.2 No Keyboard Trap — verified on the cookie-preferences dialog and shared navigation
  • 2.4.1 Bypass Blocks — through the skip link on legal and core routes
  • 2.4.7 Focus Visible, 2.4.11 Focus Not Obscured (Minimum) — through the visible focus-visible outline pattern
  • 2.5.5 Target Size (Enhanced) / 2.5.8 Target Size (Minimum) — through the shared h-11 (≥44 CSS px) interactive control pattern
  • 3.1.1 Language of Page — through the document lang attribute driven by the active locale
  • 3.2.3 Consistent Navigation, 3.2.4 Consistent Identification — through the shared header and footer components

This enumeration describes design and implementation targets, not a per-page conformance audit.

Regulatory position

RAENBI.com is a private corporate website. This statement therefore distinguishes between:

This statement does not represent raenbi.com as a public-sector website and does not claim that every page of this corporate site falls within the statutory scope of the European Accessibility Act.

Current conformance status

RAENBI.com is currently partially conformant with the benchmark above. The current repository review confirms several accessibility controls in the shared front-end system, but the domain has not yet completed an independent end-to-end audit across all templates, locales, browser and device combinations, and assistive technologies.

No formal certification is claimed in this statement.

Verified implementation points

The current internal review confirmed the following implementation patterns in the shared site code:

  • a skip link is present on legal and core public routes so keyboard users can move directly to main content
  • the document lang attribute is set from the active locale
  • visible focus-visible outlines are used as the default pattern for interactive controls
  • shared navigation, footer links, dialogs, and action buttons use the h-11 interactive size (≥44 CSS pixels), aligned with WCAG 2.5.5 / 2.5.8 target-size guidance
  • the cookie-preferences dialog uses a keyboard-accessible dialog primitive rather than a custom overlay
  • reduced-motion handling is defined for users who enable prefers-reduced-motion: reduce
  • semantic landmarks such as nav, main, and footer are used on the reviewed public routes

These points describe controls that were verified in the current codebase review. They do not by themselves amount to a full accessibility audit of every published page.

Known limitations under active review

The following areas still require ongoing review, with the WCAG 2.2 success criteria most likely at risk indicated in parentheses to make the "partially conformant" status concrete:

  • complex comparison tables, dense technical layouts, or diagram-heavy content may require additional manual checking for reading order and text alternatives (1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.3.2 Meaningful Sequence)
  • future third-party embeds or externally hosted tools may not inherit the same accessibility behaviour as the core site templates (any criterion applicable to the embedded surface; 4.1.2 Name, Role, Value is the most common gap)
  • downloadable documents, if published later, may need separate remediation and separate testing (1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.4.5 Images of Text)
  • a full screen-reader review across every template and locale has not yet been completed; until it is, full conformance with 1.3.1 Info and Relationships, 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value cannot be asserted for every page
  • the success-criteria targets listed in the benchmark section describe shared design and implementation patterns, not a per-page test; isolated regressions on specific pages may exist between full audit cycles

Feedback and accessible alternatives

If you encounter an accessibility barrier on RAENBI.com, use the contact page and mention that the message concerns accessibility. If the contact page itself is not usable, write to contact@raenbi.com and include the affected URL.

To help RAENBI investigate efficiently, include:

  • the page URL
  • the task you were trying to complete
  • the browser, device, and assistive technology used
  • the exact blocker and, if available, a screenshot or recording
  • whether the issue affects a procurement review, support access, or another time-sensitive technical context

Accessibility reports may be sent in English, French, Dutch, or Romanian, whichever is easier for you.

RAENBI aims to acknowledge accessibility reports within ten working days of receipt. If an immediate fix is not possible, RAENBI will propose a practical alternative route for the affected exchange, such as a transcript, a direct email reply, or a substitute document, so the original task can still be completed.

Any personal data included in an accessibility request is handled under the Privacy Policy.

Escalation route

Because RAENBI.com is a private corporate website that is not held out as a public-sector site, no statutory designated enforcement body applies to this corporate site by default. The primary route for accessibility concerns therefore remains the contact channel described above, and RAENBI treats accessibility reports as substantive operational requests rather than purely formal complaints.

If you believe the issue concerns an in-scope product or service under Directive (EU) 2019/882 and the Belgian implementing framework cited in the Regulatory position section above, you may also consult the Federal Public Service Economy for the Belgian enforcement context applicable to that specific product or service.

Related references

For adjacent legal and operational context, see:

Preparation and review method

  • Preparation date: 26 May 2026 (first issue of this statement in its current structured form).
  • Last review date: 27 May 2026.
  • Method: internal content and implementation review covering the statement text itself, the shared front-end accessibility patterns verified in the repository, and the official source links cited above.

This review did not constitute an external certification, a page-by-page assistive-technology audit of the whole live domain, or a privileged legal opinion.

Review cycle

RAENBI reviews this statement after material changes to shared navigation, interaction patterns, or accessibility requirements, and at least once per year.