Accessibility statement

The City of Lyon is committed to making its websites, intranet, extranet and software packages accessible (as well as its mobile applications and digital street furniture) in accordance with Article 47 of Law No. 2005-102 of February 11th 2005.

To this end, the City of Lyon is implementing the following strategy and actions:

  • The website is currently being updated to respect current accessibility standards. These updates are scheduled to go live in the second half of 2025.

This accessibility statement applies to the Lyon "Festival des Lumières" website, www.fetedeslumieres.lyon.fr.

Auditor

The RGAA 4.1.2 compliance audit was carried out by Temesis company .

Stratis, a committed actor of Responsible Digital Technology, carried out the control audit and corrective measures, and drafted this accessibility statement with the help of its Certified Accessibility Experts.

State of compliance

The Lyon "Festival des Lumières" website is partially compliant with the General Accessibility Improvement Framework (Référentiel Général d'Amélioration de l'Accessibilité - RGAA), version 4.1.

Test results

The compliance audit carried out by Stratis company reveals that 56.25% of the RGAA criteria are met.

Inaccessible content

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

Non-compliances

List of non-compliant criteria:

  • 1.2: Is each decorative image correctly ignored by assistive technologies?
  • 1.3: For each image containing information that has a text alternative, is this alternative relevant (except in special cases)?
  • 1.8: Each image containing information must, where possible, be replaced by styled text if there is no alternative mechanism. Is this rule being followed (except in special cases)?
  • 1.9: Is each image caption correctly linked to the corresponding image, where necessary?
  • 2.2: For each manager with a managerial title, is this managerial title relevant?
  • 3.2: On each web page, is the contrast between the text colour and the background colour sufficiently high (except in special cases)?
  • 3.3: On each web page, do the colours used in interface components or graphic elements that convey information provide sufficient contrast (except in special cases)?
  • 4.1: Does each pre-recorded time-based media have, where necessary, a text transcript or audio description (except in special cases)?
  • 6.1: Is each link explicit (except in special cases)?
  • 6.2: Does every link on every web page have a title?
  • 7.1: Is each script, where necessary, compatible with assistive technologies?
  • 7.4: For each script that initiates a context change, is the user notified or in control?
  • 7.5: On each web page, are status messages correctly rendered by assistive technologies?
  • 8.6: For each web page with a page title, is that title relevant?
  • 8.7: On each web page, is each language change indicated in the source code (except in special cases)?
  • 8.9: On each web page, tags should not be used solely for presentation purposes. Is this rule being followed? ;
  • 9.1: Is information on each web page structured through the appropriate use of headings?
  • 9.2: Is the document structure consistent on each web page (except in special cases)?
  • 10.1: Are style sheets used on the website to control the presentation of information?
  • 10.2: On each web page, does the visible content that carries information remain present when style sheets are disabled?
  • 10.3: On each web page, does the information remain understandable when style sheets are disabled?
  • 10.7: On each web page, for each element receiving focus, is the focus visible?
  • 10.11: For each web page, can the content be presented without loss of information or functionality and without requiring either vertical scrolling for a window with a height of 256 pixels or horizontal scrolling for a window with a width of 320 pixels (excluding special cases)?
  • 11.2: Is each label associated with a form field relevant (except in special cases)?
  • 11.10: Is data entry validation used appropriately in each form (except in special cases)?
  • 12.3: Is the "site map" page relevant? ;
  • 12.6: Can content grouping areas present on multiple web pages (header, main navigation, main content, footer, and search engine areas) be reached or avoided?
  • 12.8: Is the tab order consistent on each web page?

Derogations for disproportionate load

No exemptions have been established.

Content not subject to accessibility requirements

  • Files available in office formats published before September 23th 2018;
  • Third-party content that is neither funded nor developed by the organisation concerned and is not under its control:
    • The cookie management banner and modal (Tarteaucitron);
    • The YouTube video player on the home page.

Establishment of this accessibility statement

This statement was drawn up on 18 November 2024 following the compliance audit, and was updated on 28 November 2025 following numerous corrections and the control audit.

Technologies used for implementation

  • HTML 5
  • CSS
  • JavaScript
  • PDF
  • Drupal CMS

Test environment

Assistive technology Browser
NVDA 2024.2 Firefox 132
Jaws 2023 Firefox 132
VoiceOver Safari 17.4.1

Tools used during the audit

  • Colour Contrast Analyser
  • HeadingsMap
  • Web developer
  • ARC Toolkit

Pages of the website that have been checked for compliance

  1. Homepage
  2. Contacts
  3. Legal notices
  4. Accessibility statement
  5. Sitemap
  6. Search
  7. News
  8. Tourist information
  9. Lyon : Light specialist
  10. Partners
  11. Frequently asked questions
  12. Services for festival-goers with a disability

Feedback and contact

If you are unable to access content or a service, you can contact the City of Lyon's digital accessibility advisor to be directed to an accessible alternative or obtain the content in another format.

Remedies

This procedure should be used in the following case: you have reported an accessibility issue to the website manager that prevents you from accessing content or one of the portal's services, and you have not received a satisfactory response.