Accessibility Statement

Viaris accessibility commitment: WCAG 2.1 AA target, what is verified today, known limitations, and how to report a barrier.

Last reviewed
24 May 2026

In brief

  • Viaris is a content-first static site targeting WCAG 2.1 AA as a working reference; semantic HTML, keyboard focus, contrast, table headers and locale-correct numbers are already verified.
  • Known limitations include the consent banner overlapping content on very small viewports, some legacy SVG icons missing titles, and automated tests not yet covering full keyboard traversal.
  • Report barriers via the Contact page; reports are acknowledged within 5 business days, and outside Belgium this statement is a voluntary commitment rather than a regulated declaration.

Viaris is built as a content-first, static website. Most of what you see is rendered HTML with semantic structure, and the editorial pages should be usable without a mouse, with assistive technologies, and at a wide range of viewport sizes.

1. Conformance target

We target WCAG 2.1, Level AA as a reference standard. We treat this as a working target, not a finished claim: parts of the site already meet it, and other parts are being brought up to it.

2. What is verified today

  • Pages use semantic HTML with one h1 and a coherent heading outline.
  • Color contrast for body text on the main page templates is at or above the WCAG AA threshold.
  • Interactive elements are keyboard-reachable and visibly focused.
  • Country and route tables have proper header cells and stay readable when zoomed.
  • Outbound links are marked when they leave Viaris, and language alternates use correct hreflang and lang attributes.
  • Vignette prices and dates follow the locale style guide so screen readers spell out numbers and currencies the way native speakers expect.

3. Known limitations

We are aware of the following items and they are tracked for improvement:

  • The cookie consent banner uses a fixed bottom layout; on very small viewports it may overlap the last line of editorial content for a moment after the page loads.
  • Some legacy SVG icons miss explicit titles; we are auditing and adding them.
  • Automated end-to-end tests cover Core Web Vitals but do not yet cover full keyboard traversal of every template.

If you find an accessibility barrier not listed above, please tell us — see Feedback below.

4. Tools we use to verify

  • Manual keyboard and screen-reader checks on the main page templates.
  • Lighthouse and axe-core in development for automated heuristics.
  • Real-device checks on mobile Safari and Chrome at common viewport sizes.

5. Feedback

If you cannot access content on Viaris because of an accessibility barrier, please reach out via the channels listed on the Contact page. Include the page URL and a short description of what failed (keyboard trap, unreadable contrast, missing alt text, etc.). We aim to acknowledge accessibility reports within 5 business days and to ship a fix or a public workaround within a reasonable time frame depending on complexity.

Outside Belgium, this statement is published as a voluntary commitment and not as a regulated declaration under any national accessibility law. The Belgian variant of the brand (Viaris.be) carries an additional national-law section in its own Accessibility Statement.

Related legal pages