Accessibility: partially compliant

The Sainte-Maxime Tourist Office is partially compliant with the General Framework for Improving Accessibility (RGAA).

You can view the audit via the following link:https://ara.numerique.gouv.fr/rapport/2Ize2i-9FCNlrSH2_tZ3I/resultats

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

Non-compliance

Images:

Several images containing information do not have alternative text or a relevant alternative (criteria 1.1 and 1.3). This is particularly the case for illustrative images on many pages, where the alt attribute contains a technical file name (e.g. a photo ID) rather than describing the visual content. Furthermore, decorative images, such as certain icons in the menu or calendar, are not correctly ignored by assistive technologies (criterion 1.2), and the captions associated with the images are not technically linked to them (criterion 1.9). For a blind or visually impaired person using a screen reader, these shortcomings result either in a complete lack of information about the visual content or in the reading out of useless or meaningless text, which hinders comprehension and unnecessarily complicates navigation.

Colours:

The website has recurring issues with contrast between text and its background, as well as between the colours of interface components such as buttons or field borders (criteria 3.2 and 3.3). These shortcomings affect both site-wide elements and most of the pages in the panel. Furthermore, information is conveyed solely through a change in colour, without any additional indication, on the interactive map on the home page (criterion 3.1). These issues primarily affect people with visual impairments or colour blindness, who may be unable to perceive certain text, buttons or status information.

Scripts:

Many interactive components are not correctly rendered by assistive technologies: menus and sub-menus, the search engine, the language selector, the image gallery, the interactive map and accordion menus (criterion 7.1). Several of these same components are also not keyboard-accessible, notably because focus is not maintained in modal windows or because certain clickable elements cannot be reached (criterion 7.3). Finally, a search engine status message is rendered incorrectly, resulting in confusing output for screen readers (criterion 7.5). These issues are among the most serious identified in the audit: they can make it completely impossible for a person using only a keyboard or a screen reader to use the menu or the search function.

Mandatory elements:

The titles of some pages in the calendar do not reflect the pagination displayed, which makes it difficult to navigate using tabs or a screen reader (criterion 8.6). Furthermore, certain tags are used solely for visual formatting rather than to structure the content, in particular text inserted into generic tags instead of paragraphs (criterion 8.9). Such misuse hinders assistive technologies’ understanding of the content’s structure.

Presentation of information:

Several issues affect the presentation of content, regardless of its visual formatting. Gallery images are inserted solely as CSS backgrounds and disappear when styles are disabled (criterion 10.2), and the reading order of certain content is inconsistent in this same situation (criterion 10.3). Increasing the font size to 200 per cent results in display and readability issues (criterion 10.4), as does viewing the site in a small, mobile-style window (criterion 10.11). A link in the footer is not sufficiently visible against the surrounding text (criterion 10.6), information is indicated solely by its shape in the search engine (criterion 10.9), and keyboard focus is not always visible, particularly on featured thumbnails (criterion 10.7). Finally, tooltips that only appear on mouse hover remain invisible to keyboard users (criterion 10.14). These issues particularly affect people with visual impairments who zoom in or adjust the display, as well as keyboard users.

Forms:

The contact form does not sufficiently group fields of the same type (criterion 11.5), and some button labels are not relevant, such as a search button lacking an accessible name or a close button labelled in English (criterion 11.9). Furthermore, input error messages are not very clear, as they do not always specify the field in question or the expected format (criterion 11.10), and do not offer suggestions for correction in the event of an error, particularly in the email field (criterion 11.11). These shortcomings make it difficult for all users to complete the forms, and particularly for those using a screen reader or with cognitive impairments.

Viewing:

The PDF documents available for download are not natively accessible and have no alternative versions (criterion 13.3), which completely blocks access to their content for anyone using a screen reader. The scrolling video on the homepage cannot be paused (criterion 13.8), which may cause discomfort for people with attention disorders or who are sensitive to movement. An emoji used in a heading has no alternative text, making its interpretation by assistive technologies uncertain (Criterion 13.5). Finally, several featured carousels are only accessible on mobile devices via a swipe gesture, with no alternative navigation arrows (criterion 13.10), which excludes people with fine motor difficulties.

None.

• The reCAPTCHA
• The Touristic Maps base map

This statement was drawn up on 17 August 2026.

• HTML
• CSS
• JavaScript
• WordPress CMS

Content rendering checks were carried out using the combination provided by the RGAA reference database, with the following versions:

• On iOS mobile devices using Safari and VoiceOver
• On a MacOS desktop computer with Chrome and VoiceOver
• On a macOS desktop computer with Firefox and VoiceOver
• On a Windows desktop computer with Microsoft Edge and NVDA

• Web Developer Toolbar
• Colour Contrast Analyser
• WCAG Contrast Checker
• HeadingsMap
• Component Inspector
• RGAA Assistant
• W3C HTML Validator
• VoiceOver
• NVDA
• Stylus
• RGAA 4 Documentation
• Axe Devtools extension
• 11y tools
• Bookmarklet – Text spacing
• Bookmarklet – Force Show Keyboard Focus
• Bookmarklet – HTML Validation
• Bookmarklet – ARIA properties

• Home – https://www.sainte-maxime.com/
• Contact – https://www.sainte-maxime.com/contactez-nous/
• Legal notices – https://www.sainte-maxime.com/mentions-legales/
• Accessibility – https://www.sainte-maxime.com/accessibilite-non-conforme/
• FAQ – https://www.sainte-maxime.com/faq/
• The Mimosa Trail – https://www.sainte-maxime.com/explorer/balades-decouvertes/la-route-du-mimosa/
• Nartelle Beach – https://www.sainte-maxime.com/explorer/la-mer-a-linfini/toutes-les-plages-de-sainte-maxime/plage-de-la-nartelle/
• The port of Sainte-Maxime – https://www.sainte-maxime.com/explorer/la-mer-a-linfini/le-port-de-sainte-maxime/
• Full events calendar (list view) – https://www.sainte-maxime.com/agenda/tout-lagenda/
• End-of-summer events (card view) – https://www.sainte-maxime.com/agenda/closing-dete-sainte-maxime-fr-6343602/

If you are unable to access any content or service, you can contact the manager of the Sainte-Maxime Tourist Office to be directed to an accessible alternative or to obtain the content in another format.

• Send a message to:https://www.sainte-maxime.com/en/contact-us/

If you notice an accessibility issue preventing you from accessing content or a feature on the website, and you report this to us but do not receive a response from us, you are entitled to submit your complaint or a request for the matter to be referred to the Défenseur des droits.

There are several ways to do this:

Send a message to the Défenseur des droits athttps://formulaire.defenseurdesdroits.fr/formulaire_saisine/
Contact the Défenseur des droits’ regional representativehttps://www.defenseurdesdroits.fr/carte-des-delegues
Send a letter by post (free of charge – no stamp required) to:
Ombudsman
Post free 71120
75342 Paris CEDEX 07