Accessibility statement for the tgv-lyria.com website

This page outlines our commitments to digital accessibility and sets out the level of compliance of this website with the applicable regulations and standards.

What is digital accesibility?

Digital accessibility refers to a set of rules and best practices covering, in particular, functional, graphical, technical and editorial aspects.

Following these rules and best practices helps ensure that digital services (websites, mobile applications, PDF documents, etc.) are accessible to people with disabilities.

An accessible website allows users, for example, to:

  • Customise the display using their operating system and/or browser (enlarge or reduce text, change the font, modify colours, disable animations, etc.).
  • Browse using assistive technologies such as screen readers or refreshable Braille displays.
  • Navigate without a mouse, using only a keyboard, switches or a touchscreen.
  • Watch videos and listen to audio content with subtitles and/or transcripts.
  • Etc.

Digital accesibility commitments

TGV Lyria is committed to making its websites (public-facing, intranet and extranet), mobile applications, software packages and digital street furniture accessible, in accordance with Article 47 of French Law No. 2005-102 of 11 February 2005 (in French).

Compliance status

This website is partially compliant with RGAA (General Accessibility Improvement Framework - in French) – version 4.1.2, due to the non-compliances listed below. This website is also partially compliant with standard EN 301 549, with the assessment carried out using RAWeb (Web Accessibility Assessment Framework - in French) – version 1.

Test results

The compliance audit against RGAA version 4.1.2 and RAWeb version 1, conducted in December 2025 by Ideance, found the following results for the sample tested:

  • The overall compliance rate is 72.1%.
    This rate is calculated by dividing the number of compliant criteria by the number of applicable criteria.
  • The average compliance rate is 78.2%.
    This rate is calculated by averaging the compliance rates of each page.

Inaccessible content

Non-conmpliances

List of criteria that are not met:

  • 1.2 – Decorative images are not ignored by assistive technologies.
  • 3.2 – Text and background colour contrasts are insufficient.
  • 6.1 – Links are not sufficiently descriptive.
  • 7.1 – Scripts are not compatible with assistive technologies.
  • 7.3 – Scripts cannot be operated using a keyboard or any pointing device.
  • 7.5 – Status messages are not correctly conveyed by assistive technologies.
  • 8.7 – Language changes are not indicated.
  • 8.9 – Markup is used solely for presentation purposes.
  • 9.1 – Information is not structured using appropriate headings.
  • 9.3 – Lists are not correctly structured.
  • 10.13 – Additional content displayed when an interface component receives focus or is hovered over cannot be controlled.
  • 11.1 – Form fields do not have labels.
  • 11.8 – Items of the same type in selection lists are not appropriately grouped.
  • 11.10 – Input validation controls are not used appropriately.
  • 11.11 – Input validation controls are not accompanied by suggestions to help users correct errors.
  • 12.8 – The tab order is inconsistent.
  • 13.11 – Actions triggered by a pointing device at specific points on the screen cannot be cancelled

Additional information

Validity of the generated source code

The source code generated for the website pages is not fully valid according to the specified document type.

However, for the reasons explained below, RGAA criterion 8.2 relating to this issue has been marked as compliant.

Officially, WCAG criterion 4.1.1, which corresponds to RGAA criterion 8.2, has been removed from WCAG 2.2 and must still be considered satisfied under WCAG 2.1 and European standard EN 301 549.

In practice, this criterion no longer provides any benefit in terms of accessibility for people with disabilities. Any potential accessibility issues resulting from invalid generated source code are covered by other RGAA criteria.

Third party components not audited

Cookie management tool

The third-party cookie management tool « Cookie First » has not undergone a full and detailed audit.

However, it has been verified that its presence does not prevent users from accessing or using the rest of the website.

Date pickers on internal pages

The date pickers on the « Train Timetables » and « Traffic Information » pages were not audited, as dates can also be entered manually in the relevant fields.

Chatbot

The chatbot available on the website has undergone a separate audit. The criteria relating to it are therefore not applicable to the present audit. The results of the chatbot accessibility audit are available in the chatbot's accessibility statement.

Acessibility features

A contrast enhancement feature is available in the website footer via the « Accessibility » button.

Preparation of this statement

This statement was prepared on 4 February 2026.

Technologies used to build the website

  • HTML5.
  • ARIA.
  • CSS.
  • JavaScript.

Test environment

The tests were carried out using the following combinations of web browsers and screen readers:

  • Firefox 145 et NVDA 2025.3.2 on Windows 11.
  • Firefox 145 et JAWS 2024 on Windows 11.
  • Safari et VoiceOver on macOS 26.1.
  • Safari et VoiceOver on iOS 26.1.

Acessibility evaluation tools

  • Pika (contrast analyses tool)
  • Firefox Developer Tools.
  • Web Developer (Firefox extension).

Pages of the website included in the compliance audit

Improvement plan

As part of its commitment to digital accessibility, TGV Lyria is committed to progressively improving the compliance of the tgv-lyria.com website with the requirements of RGAA 4.1.2 and standard EN 301 549 (via RAWeb v1).

Following the audit conducted in December 2025 by Ideance, which established an overall compliance rate of 72.1% (with an average rate of 78.2%), we identified the following priority areas for improvement and planned their implementation according to the timetable below.

Short term — within 1 month

These fixes involve targeted HTML/CSS adjustments that can be implemented quickly without major technical redevelopment:

  • Criterion 1.2 – Decorative images: adding the alt="" and role="presentation" attributes to all purely decorative images, so that they are correctly ignored by screen readers.
  • Criterion 8.7 – Language changes: marking up passages written in a foreign language (particularly German and Italian in the Swiss legal notices) using the appropriate lang attribute.
  • Criterion 8.9 – Presentational markup: removing or correcting HTML tags used solely for formatting purposes, in order to preserve the semantic integrity of the code.
  • Criterion 9.1 – Heading structure: reviewing the heading hierarchy (h1 to h6) across all audited pages to ensure a logical and consistent structure.
  • Criterion 9.3 – Lists: restructuring list content using the ul, ol and li tags wherever list-type content is displayed without appropriate markup.

Medium term — within 3 month

These fixes require more extensive work on forms and dynamic interactions:

  • Criterion 11.1 – Form labels: associating each form field with an explicit label using the for/id or aria-label attributes, particularly in search and booking forms.
  • Criterion 11.11 – Error correction suggestions: implementing descriptive, contextual error messages linked to the relevant fields using aria-describedby and aria-invalid.
  • Criterion 7.5 – Status messages: using the ARIA attributes role="status" and aria-live="polite" to ensure that confirmations and dynamic notifications are correctly conveyed to screen reader users.
  • Criterion 6.1 – Descriptive links: revising generic link labels (e.g. « click here », « find out more ») so that they can be understood independently of their visual context.
  • Criterion 11.8 – Grouping of fields: structuring groups of related fields (radio buttons, checkboxes) using the fieldset and legend tags.

Monitoring and validation

Each fix will undergo functional verification using automated accessibility testing tools (WAVE, axe DevTools) and manual testing with screen readers (NVDA, VoiceOver). The results will be documented and this statement updated accordingly.

Feedback and contact

If you are unable to access any content or service on this website, you can contact us using one of the methods below, providing details of the issue you have encountered:

Write to us at the following postal address:

Lyria SAS – 25 rue Titon – 75011 Paris – France

We undertake to respond within 72 hours at the latest.

Complaints procedure

  1. You have identified one or more breaches of digital accessibility regulations on this website (such as accessibility issues or failure to meet publication requirements).
  2. You have contacted us to report the issue.
  3. You have not received a satisfactory response.

In this case, you may:

Contact Arcom

To report one or more breaches of digital accessibility regulations, visit the « Report an accessibility issue with a digital service » (in French) page on the Arcom website.

Contact the Défenseur des droits

Pour faire valoir vos droits relatifs à des défauts d'accessibilité que vous avez rencontrés :


Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07
France