Established on 17 February 2025 and updated on 4 September 2026 following the compliance audit. 

Saemes is committed to making its website accessible in accordance with Article 47 of Law No. 2005-102 of 11 February 2005.

To this end, Saemes is implementing the following strategy and measures:

  • A multi-year accessibility plan, including the action plan for the current year

This accessibility statement applies to www.saemes.fr

Compliance status

The website www.saemes.fr is partially compliant with the General Framework for Improving Accessibility (RGAA), version 4.1.2, due to the non-conformities listed below.

Test results

The compliance audit carried out by ThinkMyWeb in June 2026 reveals that 54 per cent of the criteria in RGAA version 4.1.2 are met in the audited sample.

Of the 1,166 criteria tested:

  • 21% are compliant
  • 18% are non-compliant
  • 61% are not applicable

Inaccessible content

Non-compliances

The main non-compliances identified following the audit in June 2026 are presented below by template and by page. Elements common to all pages (menu, footer, cross-site forms) account for two-thirds of the non-conformities identified. The page references (P01 to P11) refer to the list published below in the section ‘Pages of the website that were subject to the compliance check’.

Across all pages (common template)

In the main menu and the hamburger menu:

  • The button to open the menu is coded as a link, and the top-level menu items cannot be accessed via the keyboard: it is impossible to navigate the menu without a mouse.
  • The hamburger menu does not comply with the expected design pattern for a modal window: keyboard focus is not moved upon opening, it is not maintained within the menu, the Esc key does not close the menu, and focus is not restored upon closing.
  • The main menu, the burger menu and the quick access link to content (skipping link) are not enclosed within a `<nav>` tag.
  • The language selector is not identified as a navigation area.
  • Several decorative images in the menu are announced to screen readers when they should be ignored.
  • The sequences of links in the menu are not structured as lists.

In the footer:

  • The alternative text for social media icons is hidden from screen readers by a style property.
  • Several pieces of content are written in English without the language change being indicated in the code.
  • The useful links placed after the ‘Legal notices’ and ‘Cookie management’ sections disappear when the screen width is reduced to 320 px.
  • Sequences of links are not structured as lists.

In the newsletter subscription form:

  • The email field does not have a visible, persistent label: the label exists in the code but is hidden by a style property.
  • The email field does not have the attribute enabling the browser to auto-fill it.
  • The input help message is written in English.
  • The contrast between the white text and the block’s turquoise background is insufficient.
  • Input errors are not reported to assistive technologies; the focus is not returned to the field containing the error, and no correction suggestions are offered.

In the cookie management module:

  • The module is positioned at the end of the HTML code, whereas it should obtain consent as the first step: it appears last in the tab order and the reading order of the content is inconsistent.

Elements common to all pages:

  • Several links have a tooltip (title attribute) whose text does not match the visible link text.
  • Several links open in a new tab without this being indicated in their text.
  • The heading hierarchy is sometimes incomplete or inconsistent: missing section headings, empty headings, and headings used for presentational purposes.
  • Informative text is placed within generic tags rather than semantic tags, and empty paragraphs remain in the code.
  • Several pieces of text lack sufficient contrast with their background.
  • Links within the editorial content are distinguished from the surrounding text solely by colour, with a contrast ratio that is slightly insufficient (measured at 2.56, compared to an expected minimum of 3).
  • No visible focus indicator appears on drop-down lists: keyboard users cannot tell where they are on the page.
  • The site offers only one means of navigation: the main menu. There is neither a search engine nor a site map, whereas two distinct means of navigation are expected.

On specific templates and pages

On the home page (P01):

  • Several key sections of the page (‘News’, ‘Charge your vehicle’) are not preceded by a section heading.
  • The page title, ‘Find a car park | Saemes’, does not specify the geographical area covered by the site (Île-de-France).
  • The car park search field does not have a visible, persistent label.
  • Each news block generates two tab stops instead of just one.
  • In the code, the article’s topic is placed before its title.

On the news list (P02) and the news item page (P03):

  • On the news list, pagination generates incorrect page titles.
  • In the code, the article’s date is placed before its title.
  • The news blocks are not structured as lists.
  • Several decorative images have alt text that unnecessarily reads out content to screen reader users.

On the car park list (P04):

  • The page title is reduced to ‘Map’ and the main page title is empty.
  • Each of the 66 car park entries contains a ‘View car park’ link and a ‘Book my space’ link that are exactly the same: when accessed out of context via assistive technologies, these links are impossible to distinguish.
  • The car park listings are not structured as a list.
  • The tick boxes and radio buttons for the filters are hidden in favour of a custom component that cannot be operated using a keyboard.
  • The filters are triggered automatically upon selection, without prior warning and without the new number of results being announced to assistive technologies.
  • In the code, promotional information is placed before the car park name.
  • On mobile devices, the ‘List of car parks’ button overlaps the car park details and hides part of the content.

On the car park information sheet (P05):

  • The three tariff tables have a visual heading that is not linked to the table in the code, and contain empty columns used for layout purposes.
  • The headers of these tables consist of pictograms whose alternative text is ‘icon’: assistive technologies read out ‘icon’ instead of ‘Duration’, ‘Car rate’ or ‘Motorbike rate’.
  • The photo gallery scrolls automatically with no option to stop the scrolling, and neither the images nor the pagination buttons can be accessed using the keyboard.
  • The active pagination button is indicated solely by a change in colour, with very low contrast.
  • The PDF of the price lists is not accessible (insufficient contrast, pictograms without alternative text) and no accessible version is provided on the page.
  • The alternative text labels in the ‘accessible to’ section are made invisible to screen readers by a style property.
  • Several decorative images have alternative text provided.

On the subscription flow (P06):

  • The ‘Need help?’ help windows cannot be activated using the keyboard, do not provide their labels to assistive technologies, and do not support keyboard focus.
  • The drop-down lists do not reflect the visible label of the field: screen reader users hear “Select an option” instead of the actual label.
  • The field sections (car park selection, profile, subscription details, contact details) are not grouped together in the code.
  • Tick boxes and radio buttons are hidden in favour of a custom component that cannot be operated using the keyboard.
  • The general error message announced to assistive technologies is in English.
  • The breadcrumb trail does not have an accessible label.
  • The label of the ‘Subscribe’ submission button does not reflect the actual nature of the action, which is a subscription request processed within 7 working days.

On the point of interest page (P07):

  • The ‘Nearby car parks’ section is not structured as a list.
  • Several ‘Find out more’ links have a generic label that does not make it possible to understand their destination out of context.

On the ‘Book your place’ editorial page (P08):

  • The car park booking table (39 rows) is in fact a list presented in a grid format: its structure means that assistive technologies interpret it as a data table, which makes it difficult to read.
  • The 38 ‘Book now’ links in this table all have the same accessible label and cannot be distinguished out of context.
  • The heading hierarchy does not reflect the content provided, and empty paragraphs as well as a heading used for presentational purposes remain in the code.
  • Horizontal scrolling appears on the booking table when the screen width is reduced to 320 px.
  • The alternative text for the online booking banner does not include the phrase ‘Keep your mind free’, which does not appear anywhere else in the text.

On the contact page (P09):

  • The drop-down lists do not display the field’s visible label: users of screen readers hear ‘Select an option’ instead of ‘Type of enquiry’.
  • The tick boxes and radio buttons are hidden in favour of a custom component that cannot be operated using a keyboard.
  • Error handling relies on the browser’s native validation: the error messages do not offer any specific suggestions for correction, focus is not returned to the first field with an error, and there is no indication of which fields are mandatory before input.
  • The label on the ‘Send’ submission button is too generic.
  • Several fields contain presentation attributes that should be handled in a stylesheet.

On the Accessibility Statement (P10) and Legal Notice (P11) pages:

  • Several links have truncated or generic labels (‘www.saemes.fr&nbsp;’, ‘Find out more’) which do not make it possible to understand their destination out of context.
  • Empty paragraphs and headings used for presentation purposes remain in the code.
  • Content not subject to accessibility requirements
  • Cookie management module: this is provided by a third-party service provider (Axeptio). It is neither developed nor maintained by Saemes.
  • Maps: this is an external service, which is neither developed nor maintained by Saemes. Essential information (location, rates, services and access arrangements for car parks) is mainly provided in accessible text form in the relevant car park details pages. One exception remains on the map of car parks equipped with electric vehicle charging points: car parks reserved for season ticket holders are indicated there solely by the colour of the markers, with no equivalent text. The publication of this information in the form of an accessible list is included in the action plan.

Establishment of this accessibility statement

This statement was drawn up on 17 February 2025.

It was updated on 4 September 2026 following the compliance audit. It will be updated following each follow-up audit.

Technologies used to build the website

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

Testing environment

  • The web pages were tested using the following combinations of web browsers and screen readers:
  • Firefox and NVDA
  • Chrome and VoiceOver

Tools used during the assessment

  • HeadingsMaps extension
  • WCAG Contrast Checker extension
  • DevTools Inspector

Pages on the website that were checked for compliance

Feedback and contact

If you are unable to access any content or service, you can contact the website manager to be directed to an accessible alternative or to obtain the content in another format.

We undertake to reply within a reasonable timeframe.

Appeal procedures

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

You can:

 

 

Share on