Déclaration d'accessibilité

SNCF VOYAGEURS SA is committed to making its websites accessible in accordance with Article 47 of French Law No. 2005-102 of 11 February 2005.

To this end, SNCF VOYAGEURS SA is implementing the following strategy and actions:

• comprehensive support from Access42, a company specialising in digital accessibility: functional design, technical development and content accessibility;
• pooling of development work, including the mobile application and complex JavaScript components;
• planning of accessibility fixes;
• implementation of a three-year multiannual plan.

This accessibility statement applies to the editorial website (https://ouigo.com (ouigo.com)).

The Ouigo – Editorial website (https://www.ouigo.com/ (ouigo.com)) is not compliant with the French General Accessibility Improvement Framework (RGAA), version 4.1, due to the non-compliances listed in the “Test Results” section.

The compliance audit conducted by Access42 found that the website complies with 40.30% of the criteria in RGAA version 4.1.

The content listed below is not accessible for the following reasons.

The main non-compliances affecting the editorial content are listed below:

• Some pages contain informative images with no alternative text or no relevant alternative text.
• Across all pages, decorative images are not ignored by assistive technologies.
• On one page, a complex informative image requires a detailed description.
• On one page, a frame (iframe) has no title.
• Across all pages, some information is conveyed solely through colour or shape.
• Across all pages, some text and user-interface components have insufficient contrast.
• On one page, multimedia content has neither a text transcript nor subtitles.
• On one page, a table contains header cells that are not correctly defined.
• Across all pages, many links have no label or no explicit label.
• Across all pages, some JavaScript functions are incompatible with assistive technologies or are not keyboard-accessible—including modal windows, content that is displayed and hidden, and carousels—or make inappropriate use of ARIA properties.
• On one page, changes of context occur without the User being informed.
• On one page, status messages are not conveyed by assistive technologies.
• One page does not have a relevant page title.
• Across all pages, changes of language within the text are not correctly indicated.
• All pages use tags for presentational purposes, such as empty paragraphs and unstructured text within paragraph tags.
• All pages have an inappropriate heading hierarchy, with missing or incorrectly defined headings.
• The structure and main areas of the pages are incorrectly defined.
• On several pages, sequences of items are not structured as lists.
• Across all pages, presentational HTML tags or attributes are used.
• On several pages, content is not arranged in a logical order within the source code. In particular, the cookie banner is not the first element on the page.
• Some pages suffer from loss of information and readability when text-spacing properties are applied.
• Across all pages, visual focus indicators have insufficient contrast or are disabled.
• Across all pages, informative content is ignored by assistive technologies.
• Across all pages, some form fields do not have correctly associated labels.
• On some pages, fields of the same type are not grouped together.
• Across all pages, input assistance is missing or irrelevant for fields requiring a specific format.
• Across all pages, some form buttons do not have relevant labels.
• Across all pages, forms do not allow certain fields to be completed automatically using the User’s data.
• Across all pages, the quick-access link to the main page content does not work.
• One page has issues with the tab order.
• Across all pages, some additional content appearing on hover or focus cannot be reached using the keyboard or controlled by the User.
• On one page, a PDF document is inaccessible or does not have an accessible alternative.

No exempted content.

• The “reCAPTCHA” component—reason: external service.
• The “OneTrust” cookie-management component—reason: external service.

This statement was prepared on 19 January 2024.

• HTML5
• CSS
• JavaScript
• Content management system: Drupal

The editorial website pages were tested using the following combinations of web browsers and screen readers:

• Firefox 121.0 and NVDA 2023.3
• Firefox 121.0 and JAWS 2023.2302.15
• Safari 17.2 and VoiceOver on macOS 14.2

As the assistive technologies did not support the components being tested, rendering tests were not performed in a mobile environment.

Accessibility was verified through manual tests assisted by tools, including dedicated CSS style sheets, the HeadingsMap and Web Developer Toolbar extensions, and Colour Contrast Analyser.

1. Home
2. Contact
3. Legal Notice
4. Accessibility
5. Sitemap
6. Offers
7. General Terms and Conditions of Sale
8. Our Most Popular Routes (Lyon–Paris)
9. News and Special Offers
10. Seat Selection
11. Destinations
12. FAQ – Works in Progress

This statement was prepared on 8 December 2025 for the website https://ventes.ouigo.com (ouigo.com). It is valid from the date of publication and must be updated after three years, following major changes to the website, or 18 months after the publication of a new version of the applicable accessibility standard.

OUIGO is committed to making its websites, mobile applications, intranet, extranet and software packages accessible in accordance with Article 47 of French Law No. 2005-102 of 11 February 2005.

We value inclusion and diversity and ensure that our website, https://ventes.ouigo.com (ouigo.com), is accessible to everyone, particularly people with disabilities.

As part of this digital accessibility initiative, we work with Accessiway.

We are firmly committed to making the web accessible to everyone. As part of a responsible, long-term approach, we aim to meet all regulatory requirements, particularly RGAA 4.1.2 and European standard EN 301 549.

The website https://ventes.ouigo.com (ouigo.com) has an accessibility compliance rate of 50.91% and is therefore partially compliant with the French General Accessibility Improvement Framework (RGAA 4.1.2).

The compliance audit conducted by AccessiWay on 8 December 2025 found that 50.91% of the criteria in RGAA version 4.1.2 were met.

Details of the results:

• Number of compliant criteria: 28
• Number of non-compliant criteria: 27
• Number of non-applicable criteria: 51

The content listed below is not accessible for the following reasons.

• 1.1 – Does every informative image have a text alternative? Some non-text content presented to the User does not have an equivalent text alternative serving the same purpose.
• 1.2 – Is every decorative image correctly ignored by assistive technologies? Some decorative images are not ignored by assistive technologies.
• 3.1 – On each web page, information must not be conveyed by colour alone. Is this requirement met? On some web pages, information is conveyed by colour alone.
• 3.2 – On each web page, is there sufficient contrast between the colour of the text and the colour of its background, except in specific cases? The contrast between the text and its background is insufficient on some web pages.
• 3.3 – On each web page, do the colours used in user-interface components or informative graphical elements have sufficient contrast, except in specific cases? The colours used in some user-interface components or informative graphical elements do not have sufficient contrast.
• 7.1 – Is every script compatible with assistive technologies where necessary? Some scripts are not compatible with assistive technologies where required.
• 7.3 – Can every script be controlled using the keyboard and any pointing device, except in specific cases? Some scripts cannot be controlled using the keyboard or a pointing device.
• 7.5 – On each web page, are status messages correctly conveyed by assistive technologies? Some status messages are not correctly conveyed by assistive technologies.
• 8.6 – For every web page with a page title, is that title relevant? Some page titles are not relevant to the content.
• 9.1 – On each web page, is information structured through the appropriate use of headings? On some pages, information is not correctly structured through the appropriate use of headings.
• 9.2 – On each web page, is the document structure consistent, except in specific cases? The structure of some web pages is not consistent.
• 9.3 – On each web page, is every list correctly structured? Some lists on the web pages are not correctly structured.
• 10.1 – Are style sheets used on the website to control the presentation of information? Some web pages do not use style sheets to control the presentation of information.
• 10.3 – On each web page, does the information remain understandable when style sheets are disabled? On some pages, the information is not understandable when style sheets are disabled.
• 10.4 – On each web page, does the text remain readable when the font size is increased to at least 200%, except in specific cases? On some pages, the text is not readable when the font size is increased to 200% or more.
• 10.7 – On each web page, is the focus indicator visible for every element receiving focus? The focus indicator is not visible on some elements receiving focus.
• 10.8 – On each web page, is hidden content intended to be ignored by assistive technologies? Some hidden content is not correctly ignored by assistive technologies.
• 10.11 – On each web page, can content be presented without requiring both vertical scrolling in a window with a height of 256 px and horizontal scrolling in a window with a width of 320 px, except in specific cases? Some content requires excessive vertical or horizontal scrolling to be viewed.
• 10.12 – On each web page, can text-spacing properties be redefined by the User without any loss of content or functionality, except in specific cases? Text-spacing properties cannot be redefined by the User without loss of content or functionality.
• 10.13 – On each web page, can additional content appearing when a user-interface component receives focus or is hovered over be controlled by the User, except in specific cases? Some additional content appearing on focus or hover cannot be controlled by the User.
• 11.1 – Does every form field have a label? Some form fields do not have a label.
• 11.5 – In each form, are fields of the same type grouped together where necessary? Fields of the same type are not grouped together where necessary.
• 11.6 – In each form, does every group of fields of the same type have a legend? Some groups of fields of the same type do not have a legend.
• 11.10 – In each form, is input validation used appropriately, except in specific cases? Some input validation controls are not used appropriately.
• 12.2 – Within each group of pages, are the menu and navigation bars always located in the same place, except in specific cases? The menu and navigation bars are not always located in the same place within some groups of pages.
• 12.8 – On each web page, is the tab order consistent? The tab order is not consistent on some pages.
• 13.1 – On each web page, does the User have control over every time limit that changes the content, except in specific cases? The User does not have control over some time limits that change the content.

No content to report.

No content to report.

This statement was prepared on 8 December 2025.

• HTML5
• CSS
• JavaScript

The latest available versions of:

• Apple macOS
• Microsoft Windows
• Apple iOS
• Google Android

The latest available versions on the various operating systems:

• Google Chrome
• Windows
• Edge
• Safari
• Brave
• Adobe Acrobat Reader / Preview on Mac, for PDFs only

• Mouse emulators, magnifiers and on-screen keyboards available on the various operating systems
• VoiceOver, on Apple systems only
• TalkBack, on Android only
• NVDA 2025 and Freedom Scientific JAWS 2022, on PC systems only
• Tanaguru Webext RGAA4
• RGAA Assistant
• Graphical assessment tools available on the various operating systems, including tools for colours, contrast and subtitles

• Home page
• OUIGOLAND Fare Map
• Real-Time Train Tracking
• Real-Time Train Tracking – Trains
• Choose from the Suggested Dates
• Add Options – Customer Information
• Seat Selection
• My Tickets – Basket
• My Trips
• My Information
• Payment
• Payment Confirmation

If you are unable to access any content or service, you may contact OUIGO’s accessibility officer to be directed to an accessible alternative or to obtain the content in another format.

If you identify an accessibility issue that prevents you from accessing any content or functionality on the website and, after reporting it to us, you do not receive a response, you are entitled to submit a complaint or a referral request to the French Defender of Rights. Several options are available:

• Send a message to the Defender of Rights (opens in a new window)
• Contact the Defender of Rights’ representative in your region (opens in a new window)
• Send a letter free of charge, without a stamp, to: Défenseur des droits, Libre réponse 71120, 75342 Paris CEDEX 07, France