Accessibility Statement

Autovig accessibility commitment under the European Accessibility Act: WCAG 2.2 AA target, known limitations, feedback route, and the Belgian enforcement authority.

Autovig is committed to making the website autovig.eu (the "Site") accessible in accordance with Directive (EU) 2019/882 of 17 April 2019 on the accessibility requirements for products and services (the "European Accessibility Act") and its Belgian transposition, the Loi du 28 novembre 2022 relative aux exigences en matière d'accessibilité applicables à certains produits et services / Wet van 28 november 2022, applicable to covered private-sector services from 28 June 2025.

This statement follows the structure of the model accessibility statement set out in Commission Implementing Decision (EU) 2018/1523 (web-accessibility model), adapted to the private-sector scope of the European Accessibility Act.

1. Conformance target

The Site targets the requirements of:

WCAG 2.2 level AA — W3C Recommendation of 5 October 2023.
EN 301 549 v3.2.1 (2021-03)Accessibility requirements for ICT products and services, clauses 9 (web), 11 (non-web documents) and 12 (documentation and support services) where applicable.

2. Conformance status

The Site is partially conformant with WCAG 2.2 level AA: the editorial templates and the country-, route- and trust-page templates pass the criteria listed under section 3 below, while a small number of items listed under section 4 are not yet fully conformant.

A claim of "fully conformant" is not made because a full independent audit against every WCAG 2.2 AA success criterion across every template has not yet been completed.

3. Scope of the statement

This statement covers all pages of https://autovig.eu/ produced by the static build of the Autovig editorial codebase, in all published languages (en, fr, de, nl, ro, pl).

Third-party content reached through outbound links (for example operator websites such as ASFINAG, DARS, NÚSZ, BGTOLL or CNAIR) is outside the scope of this statement.

4. Non-accessible content and known limitations

The following items are known not to be fully conformant or are otherwise limited. Each item lists the relevant WCAG 2.2 success criterion (SC) and the planned remediation horizon.

Cookie consent banner — focus order on small viewports (SC 2.4.3 Focus Order, SC 1.4.10 Reflow). On viewports narrower than 360 CSS pixels the banner can temporarily overlap the last line of editorial content after page load. Planned fix: 2026-Q3. Alternative: the banner can be dismissed with the keyboard Esc key and all editorial content remains reachable.
Some legacy SVG icons missing <title> (SC 1.1.1 Non-text Content). A small number of decorative-or-near-decorative icons in older country page variants lack a programmatic name. They are being inventoried and either marked aria-hidden="true" (decorative) or given an accessible name. Planned fix: 2026-Q3.
Automated keyboard-traversal coverage of every template (SC 2.1.1 Keyboard). Automated end-to-end tests cover Core Web Vitals and high-level navigation, but do not yet exhaustively replay every interactive template with keyboard-only input. Planned addition to the E2E suite: 2026-Q4.

No item is claimed under the disproportionate burden exemption of article 14 of Directive (EU) 2019/882 at the present date. If such an exemption is ever claimed, the assessment criteria listed in that article will be documented in this statement before the exemption is invoked.

5. Alternative routes

Because the Site is an editorial information service and not a transactional service at the current stage, every primary function — reading country information, comparing operators, reading route guides, reading trust and legal pages, contacting us — is available through a fully keyboard-accessible HTML route. If you encounter a barrier on a specific page, you may also write to us (section 7) and we will provide the information directly.

6. Preparation of this statement

Date of preparation: 25 May 2026.
Last review: 25 May 2026.
Method: self-assessment by the responsible publisher, combining manual keyboard and screen-reader checks on the main templates with automated tooling (Lighthouse Accessibility audits and axe-core). Automated tools cover only a subset of WCAG criteria — typically around 30–40 % — and findings are confirmed manually before publication.

The statement will be reviewed at least annually and whenever a material change is made to the templates or the build.

7. Feedback mechanism

If you encounter an accessibility barrier on the Site, please write to:

Please include in your report:

the URL of the affected page;
a short description of the barrier (for example: "I cannot reach the consent button with the keyboard");
the assistive technology, browser and operating-system version you are using, if applicable.

We acknowledge accessibility reports within 5 business days and aim to provide a substantive response — fix shipped or workaround communicated — within 14 calendar days of acknowledgement, taking into account the complexity of the issue.

Personal data submitted in an accessibility report is processed under our Privacy Policy on the legal basis of legitimate interest (responding to feedback and improving accessibility) and is retained in accordance with the correspondence-data retention period stated there.

8. Enforcement procedure

If you are not satisfied with our response to an accessibility report, you can refer the matter to the Belgian market-surveillance authority designated under the Loi du 28 novembre 2022 (Belgian transposition of the European Accessibility Act):

Direction générale de l'Inspection économique / Algemene Directie Economische Inspectie
Service public fédéral Économie, P.M.E., Classes moyennes et Énergie / Federale Overheidsdienst Economie, K.M.O., Middenstand en Energie
North Gate III, Boulevard du Roi Albert II 16 / Koning Albert II-laan 16, 1000 Bruxelles / 1000 Brussel, Belgium

You may also refer cross-border accessibility matters to the European Commission's Accessibility Resource Centre via the European Disability Forum: https://www.edf-feph.org.

9. Compatibility

The Site is designed to work with the following browser and assistive technology combinations. Older configurations may work but are not actively tested.

Desktop: latest two stable versions of Mozilla Firefox, Google Chrome, Microsoft Edge and Apple Safari, with the operating-system native screen readers (NVDA on Windows, VoiceOver on macOS) and Windows Narrator.
Mobile: latest two iOS and Android versions, with VoiceOver and TalkBack.
The Site does not rely on JavaScript for primary content; with JavaScript disabled, the editorial body, navigation, language switcher and footer remain reachable.

10. Technical specifications

Accessibility of the Site relies on the following technical specifications:

HTML5 (living standard) — semantic structural elements (header, nav, main, article, aside, footer).
CSS — for visual presentation; the Site degrades gracefully without CSS.
WAI-ARIA 1.2 — only where native HTML semantics are insufficient; ARIA does not override native role.
JavaScript — progressive enhancement; the Site is statically pre-rendered and is fully readable without JavaScript.

Sources