Accessibility Statement

WCAG 2.2 Level AA is our target; conformance is not yet established. How to report barriers, known gaps, and Belgian EAA context for autovig.eu.

Last reviewed
12 October 2026

In brief

  • Status: partially conformant — WCAG 2.2 Level AA (EN 301 549 v3.2.1) is our stated target; a full audit of every template, locale and interactive journey is not yet complete.
  • Report a barrier at privacy@autovig.eu with the page URL, what you tried to do, your browser and assistive technology; we aim to acknowledge within 14 days.
  • Directive (EU) 2019/882 (European Accessibility Act) and the Belgian Act of 5 November 2023 partially transpose accessibility duties for certain services from 28 June 2025; this pre-launch editorial site has no checkout. Enforcement for covered services may involve the Federal Public Service Economy.

This statement describes the accessibility of the website autovig.eu (the "Site") published by Autovig. It is prepared under Directive (EU) 2019/882 (European Accessibility Act), the Belgian transposition for the services it covers, and the model accessibility-statement structure in Commission Implementing Decision (EU) 2018/1523, adapted for a private-sector editorial website.

1. Publisher

The Site is published by:

  • RAENBI GROUP BV
  • Registered office: Lindestraat 42, 1640 Sint-Genesius-Rode, Belgium
  • Enterprise number (KBO/BCE): 0738.879.880
  • VAT: BE 0738.879.880
  • Accessibility feedback: privacy@autovig.eu

2. Scope

This statement applies to the public pages served at https://autovig.eu/ and its language-prefixed paths (English, French, German, Dutch, Romanian and Polish), as built and deployed from the Autovig static site. It does not cover third-party websites linked from the Site (national vignette operators, resellers or social networks).

3. Conformance target and status

Target: Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, interpreted through EN 301 549 v3.2.1 (2021-03) for ICT products and services.

Status: Partially conformant. Our evidence is automated: axe-core checks for serious and critical issues in the Playwright end-to-end suite on six representative English templates (homepage, a country page, an operational guide, a route guide, a trust page and a legal page) and on the open mobile menu; keyboard tests showing a visible focus indicator on the homepage, the route planner and a country page, and that focus stays inside the open mobile menu; a pixel-sampling test that text over the hero photographs of the tested country and guide pages reaches at least 4.5:1 contrast; and measurements showing that the cookie banner and preferences dialog reflow without horizontal scrolling from 240 CSS pixels wide and at 200 % text size. We have not recorded manual screen-reader testing, completed an independent third-party audit or verified every success criterion on every published URL in every locale. This statement therefore does not certify full WCAG 2.2 AA conformance.

4. Preparation and review dates

MilestoneDate
Statement first prepared2026-05-24
Last reviewed2026-10-11
MethodAutomated axe-core, keyboard-focus and contrast tests in the end-to-end suite and reflow measurements of the cookie dialogs (section 3); no recorded screen-reader test and no third-party audit

The Updated at and Reviewed at dates in the page header match the last substantive review of this statement.

5. Known non-accessible content

The gaps below are known as of the last review. Each names the WCAG 2.2 success criterion involved. We treat them as not conformant until fixed; we do not rely on a disproportionate-burden exemption for these items.

Whole Site — testing scope

WCAG 2.2 criterion All
Issue Automated tools find only part of WCAG failures, and our checks cover representative English templates rather than every URL and language.
Planned action Extend the checks to all six languages and add recorded manual keyboard passes.

Screen-reader use

WCAG 2.2 criterion 1.3.1, 4.1.2 and related
Issue No screen reader has been formally tested with the Site yet, so issues only a screen-reader user would notice may remain.
Planned action Run and record tests with at least NVDA and VoiceOver.

If you encounter a barrier not listed here, please report it (section 6).

6. Feedback and contact

If you cannot access content or use a function on the Site, write to privacy@autovig.eu. Include:

  • the page URL;
  • a description of the problem and what you were trying to do;
  • your browser, operating system and assistive technology (if any).

We aim to acknowledge accessibility reports within 14 days and to propose a correction, a workaround or an accessible alternative where feasible. Processing of your message is described in our Privacy Policy (correspondence data; legitimate interest in operating an accessible public website).

If you cannot use the cookie-preferences dialog, write to the same address and we will help. Your choice is stored only in your browser, so we cannot record it for you remotely; until then, blocking cookies in your browser settings keeps all analytics off.

7. Enforcement procedure (Belgium)

Directive (EU) 2019/882 applies to specified products and services. In Belgium, the Act of 5 November 2023 (partial transposition for consumer banking and e-commerce services, in force from 28 June 2025) implements accessibility duties for the services it covers. Autovig is an editorial information website at pre-launch stage: it does not offer checkout or payment on the Site. Whether a given page or feature falls within a covered service category depends on the actual service offered; this statement does not assert a legal exemption or a binding market-surveillance decision.

If you believe an accessibility obligation applicable to us has not been met, you may contact the Federal Public Service Economy (Service public fédéral Économie / Federale Overheidsdienst Economie), which provides guidance on the legal framework and routes complaints concerning economic legislation, including accessibility rules for covered services:

8. Compatibility and technical specifications

Technical basis: HTML5, CSS, semantic landmarks, WAI-ARIA where needed, JavaScript for progressive enhancement (route planner, cookie consent). Public pages are statically prerendered; core content remains usable when JavaScript is disabled except for features that inherently require it (planner interaction, consent storage).

Tested environment: the automated checks run in Chromium through Playwright, at a desktop viewport (1280 × 800) and a mobile viewport (390 × 844). No combination with a screen reader (such as NVDA, JAWS, VoiceOver or TalkBack) has been formally tested yet; if you use one, your feedback is especially welcome (section 6).

9. Alternatives

  • Vignette prices and rules: country guide pages provide structured headings, lists and tables; if a table is difficult to use with your technology, the same facts are usually repeated in prose in the body or FAQ.
  • Route planning: when the map is not usable, the planner still exposes corridor and country lists in the form controls; you may also use official operator websites linked from our guides.
  • Cookie choices: if the dialog is inaccessible, blocking cookies (or site data) for autovig.eu in your browser settings keeps all analytics off; write to privacy@autovig.eu if you need help.

Sources

Related legal pages