What is digital accessibility?
An accessible website is one that allows people with disabilities to access its content and features without difficulty.
An accessible website allows users, for example, to:
- Navigate using screen readers and/or Braille displays (used in particular by blind and partially sighted people).
- Customise the website display to suit individual needs (enlarging text, changing colours, etc.).
- Navigate without using a mouse (using only the keyboard, via a touchscreen, by voice or any other adapted device).
To achieve this, the website must comply with current standards during its development and updates.
Declaration of Compliance with the RGAA
Provence Méditerranée is committed to making its services portal accessible in accordance with Article 47 of Law No. 2005-102 of 11 February 2005. This accessibility statement applies to the online service: https://staging.otipass.cloud/ot/front/provence/.
Compliance status
The https://staging.otipass.cloud/ot/front/provence/ portal is partially compliant with the General Accessibility Improvement Framework (RGAA 4.1.2). The non-compliances are listed below.
Résults
The compliance audit carried out by Otipass reveals that 93% of the RGAA criteria are met*.
This percentage corresponds to: (out of a total of 96 criteria)
• 89 criteria met
• 7 criteria not met
• 68 criteria not applicable
(*) This percentage is provisional. It is calculated based on the automated report, which covers 28 out of 96 criteria.
Non-accessible content
Not applicable
• Criterion 1.2: Is every decorative image correctly ignored by assistive technologies?
• Criterion 1.3: For every image conveying information that has a text alternative, is that alternative relevant?
• Criterion 1.5: Is every decorative vector image correctly ignored by assistive technologies?
• Criterion 1.6: For each information-carrying vector image that has a text alternative, is that alternative relevant?
• Criterion 1.8: Is every decorative image correctly ignored by assistive technologies?
• Criterion 1.9: For every information-carrying image that has a text alternative, is that alternative relevant?
• Criterion 2.2: Does each frame have a relevant description?
• Criterion 4.1: Does each pre-recorded time-based media item have, where necessary, a text transcript or synchronised audio description?
• Criterion 4.2: Does each pre-recorded time-based media item have, where necessary, a synchronised text transcript?
• Criterion 4.3: Does each pre-recorded time-based media item have a synchronised audio description, where necessary?
• Criterion 4.4: For each pre-recorded time-based media item with a text transcript or synchronised audio description, is it relevant?
• Criterion 4.5: Does each pre-recorded time-based media item have a relevant synchronised text transcript?
• Criterion 4.6: Does each pre-recorded time-based media item have a relevant synchronised audio description?
• Criterion 4.7: Does each non-time-based media item have a relevant alternative, where necessary?
• Criterion 4.8: Does each non-time-based media item have an alternative, where necessary?
• Criterion 4.9: For each non-temporal media item that has an alternative, is that alternative relevant?
• Criterion 5.4: For each data table that has a summary, is that summary relevant?
• Criterion 5.5: For each data table that has a caption, is that caption relevant?
• Criterion 6.3: On every web page, is every link visible?
• Criterion 7.1: Is every script compatible with assistive technologies?
• Criterion 7.3: Every script must not trigger a change of context. Is this rule followed?
• Criterion 7.4: Can each script be disabled via an accessible mechanism?
• Criterion 7.5: On every web page, are status messages correctly rendered by assistive technologies?
• Criterion 8.2: For every web page with a default language, is that language appropriate?
• Criterion 8.7: On each web page, does every abbreviation have a relevant definition?
• Criterion 8.8: On each web page, are all citations correctly attributed?
• Criterion 8.9: On each web page, are citations correctly rendered by assistive technologies?
• Criterion 9.2: On every web page, is the document structure consistent?
• Criterion 9.4: On every web page, are citations correctly attributed?
• Criterion 10.1: On every web page, are style sheets used appropriately?
• Criterion 10.2: On every web page, is the generated source code valid for the specified document type (except in specific cases)?
• Criterion 10.3: On every web page, does each style sheet have a specified media type?
• Criterion 10.4: On every web page, can the foreground and background colour properties be set by the user via an alternative style sheet?
• Criterion 10.5: On every web page, can the text size properties be set by the user via an alternative style sheet?
• Criterion 10.7: On every web page, for every external script or stylesheet, is the reference to these files compatible with assistive technologies?
• Criterion 10.8: On every web page, is the source code valid according to the specified document type (except in special cases)?
• Criterion 10.9: On every web page, tags must not be used for presentational purposes. Is this rule being followed?
• Criterion 10.10: On every web page, the use of CSS properties must not reduce the accessibility of the content. Is this rule being followed?
• Criterion 10.11: On every web page, must hidden content be ignored by assistive technologies?
• Criterion 11.2: Is every form field label relevant?
• Criterion 11.5: Is every form field group label relevant?
• Criterion 11.6: Does every form field have a label?
• Criterion 11.7: Is every label associated with a form field relevant?
• Criterion 11.8: Does every form field have a format indicator?
• Criterion 11.9: Is every format specification associated with a form field relevant?
• Criterion 11.11: Is every indication that a field is required relevant?
• Criterion 11.12: Does every form field have input help?
• Criterion 11.13: Is each input prompt relevant?
• Criterion 12.1: Does each set of pages have at least two different navigation systems (except in special cases)?
• Criterion 12.2: On each web page, are the menu and/or navigation bar always in the same place (except in special cases)?
• Criterion 12.3: On every web page, is the content area always in the same place in the source code (except in special cases)?
• Criterion 12.4: On every web page, is the identification of the main content area consistent?
• Criterion 12.5: On each web page, is it possible to access the content without taking the formatting into account?
• Criterion 12.6: On each web page, can the content be presented in a linearised manner without any loss of information?
• Criterion 12.7: On each web page, is the source code organised according to the document’s structure?
• Criterion 12.9: On every web page, are citations correctly attributed?
• Criterion 13.1: For every PDF document, information must not be conveyed solely through colour. Is this rule followed?
• Criterion 13.2: For every PDF document, is the contrast between the text colour and the background colour sufficiently high?
• Criterion 13.3: For each PDF document, do the colours used in information-bearing graphic elements provide sufficient contrast?
• Criterion 13.4: For each PDF document, does every image conveying information have a text alternative?
• Criterion 13.5: For each PDF document, are all decorative images correctly ignored by assistive technologies?
• Criterion 13.6: For each PDF document, does every data table have a summary?
• Criterion 13.6: For each PDF document, does every data table have a summary?
• Criterion 13.7: For each PDF document, does every data table have a caption?
• Criterion 13.8: For each PDF document, are all row headers and column headers correctly defined?
• Criterion 13.9: For each PDF document, is every link self-explanatory (out of context)?
• Criterion 13.10: For each PDF document, does every form field have a label?
• Criterion 13.11: For each PDF document, is the language of the document specified?
• Criterion 13.12: For each PDF document, is the document structure consistent?
Non-compliance
• Criterion 3.2: On each web page, is the contrast between the text colour and the background colour sufficiently high?
• Criterion 3.3: On each web page, do the colours used in interface components or information-bearing graphic elements provide sufficient contrast?
• Criterion 6.1: Is every link self-explanatory (out of context)?
• Criterion 6.2: On every web page, does every link, with the exception of anchors, have a label?
• Criterion 9.1: On every web page, is the information structured through the appropriate use of headings?
• Criterion 9.3: On every web page, is every list correctly structured?
• Criterion 12.8: On every web page, is every list of items structured?
Date of this accessibility statement
This statement was issued on 27 October 2025.
Technologies used to build the website:
• HTML5
• CSS3 / SCSS / Bootstrap
• JavaScript / jQuery
• ARIA
• SVG
User agents, assistive technologies and tools used to verify accessibility
Automated testing
This audit uses the axe-core tool to automatically detect accessibility issues.
Certain RGAA criteria require manual verification and are not covered by this automated audit.
Manual testing
Additional testing is required to ensure content is rendered correctly with assistive technologies in accordance with the test environment described in the RGAA 4.1.2 reference framework:
• Wave (Chrome plugin)
• Lighthouse (Chrome)
• Web Developer (Chrome plugin)
• WCAG Contrast Checker
Web pages that have been checked for compliance:
• https://staging.otipass.cloud/ot/front/provence/
• which-city-card-validity-period-to-choose
• how-to-buy-my-city-card
• sales-points
• faq
• at-partner-outlets
• mobile-app
• bus-boat-bus
• itinerary-ideas
• bus-boats-practical-information
• best-ways-to-get-around
• list-of-services
• discounts-with-my-city-card
• inter-municipal-connections-itinerary-ideas
• list-of-events
• overview-map
• savings
• book
Feedback and contact
If you are unable to access content or a service, you can contact the website manager to be directed to an accessible alternative or to obtain the content in another format.
Appeal procedures
This procedure should be used in the following situation.
You have reported an accessibility issue to Provence Méditerranée’s digital accessibility officer that prevents you from accessing content or one of the services on its portal, and you have not received a satisfactory response.
Send a message to the Defender of Rights: https://formulaire.defenseurdesdroits.fr
Contact the Defender of Rights’ representative in your region: https://www.defenseurdesdroits.fr/saisir/delegues
Send a letter by post (free of charge, no stamp required):
Defender of Rights
Freepost 71120
75342 Paris CEDEX 07