What is digital accessibility?
An accessible website is a website that allows people with disabilities to access its content and features without difficulty.
An accessible website allows, for example:
- Navigation using screen readers and/or braille displays (particularly used by blind and visually impaired people).
- Customization of the site’s display according to user needs (text enlargement, color changes, etc.).
- Navigation without using a mouse (keyboard-only navigation, via touchscreen, voice control, or any other suitable input device).
To achieve this, the website must comply with applicable standards during its development and updates.
RGAA Compliance Statement
G-Pass Business is committed to making its service portal accessible in accordance with Article 47 of Law No. 2005-102 of February 11, 2005.
This accessibility statement applies to the online service: https://business.grenoblealpespass.com/.
Compliance Status
The portal https://business.grenoblealpespass.com/ is partially compliant with the General Accessibility Improvement Framework (RGAA 4.1.2). Non-compliances are listed below.
Test Results
The compliance audit carried out by Otipass shows that 68% of RGAA criteria are met*.
This percentage corresponds to: (out of a total of 31 applicable criteria)
- 21 compliant criteria
- 10 non-compliant criteria
- 18 non-applicable criteria
- 57 untested criteria
(*) This percentage is provisional. It is based on the automated report covering 49 out of 106 criteria.
Non-accessible Content
Untested
- Criterion 1.3: For each informative image with a text alternative, is this alternative relevant?
- Criterion 1.4: For each image used as a CAPTCHA or test image with a text alternative, does this alternative identify the nature and function of the image?
- Criterion 1.5: For each image used as a CAPTCHA, is there an alternative way to access the content or function of the CAPTCHA?
- Criterion 1.6: Does each informative image have, if necessary, a detailed description?
- Criterion 1.7: For each informative image with a detailed description, is this description relevant?
- Criterion 1.8: Each text image conveying information, in the absence of a replacement mechanism, should if possible be replaced with styled text. Is this rule respected (except in special cases)?
- Criterion 1.9: Is each image caption, if necessary, correctly associated with the corresponding image?
- Criterion 2.2: For each frame with a frame title, is this title relevant?
- Criterion 4.1: Does each pre-recorded time-based media have, if necessary, a text transcript or synchronized audio description?
- Criterion 4.2: Does each pre-recorded time-based media have, if necessary, a synchronized text transcript?
- Criterion 4.3: Does each pre-recorded time-based media have a synchronized audio description, if necessary?
- Criterion 4.4: For each pre-recorded time-based media with a text transcript or synchronized audio description, is it relevant?
- Criterion 4.5: Does each pre-recorded time-based media have a relevant synchronized text transcript?
- Criterion 4.6: Does each pre-recorded time-based media have a relevant synchronized audio description?
- Criterion 4.9: For each non-time-based media with an alternative, is this alternative relevant?
- Criterion 5.1: Does each complex data table have a summary?
- Criterion 5.2: For each complex data table with a summary, is it relevant?
- Criterion 5.3: For each layout table, does the linearized content remain understandable?
- Criterion 5.5: If there is a title, is it relevant?
- Criterion 7.2: For each script with an alternative, is this alternative relevant?
- Criterion 7.5: On each web page, are status messages correctly conveyed by assistive technologies?
- Criterion 8.1: Is each web page defined by a document type?
- Criterion 8.2: For each web page, is the generated source code valid according to the specified document type?
- Criterion 8.6: For each web page with a page title, is this title relevant?
- Criterion 8.10: On each web page, are changes in reading direction indicated?
- Criterion 9.4: On each web page, is each quotation correctly identified?
- Criterion 10.1: On the website, are style sheets used to control the presentation of information?
- Criterion 10.2: On each web page, does visible informative content remain present when style sheets are disabled?
- Criterion 10.3: On each web page, does information remain understandable when style sheets are disabled?
- Criterion 10.5: On each web page, are CSS declarations for background colors and fonts used correctly?
- Criterion 10.7: On each web page, is focus visible for each element receiving focus?
- Criterion 10.9: On each web page, information must not be conveyed solely by shape, size, or position. Is this rule respected?
- Criterion 10.10: On each web page, information must not be conveyed solely by shape, size, or position. Is this rule implemented appropriately?
- Criterion 10.11: For each web page, can content be presented without loss of information or functionality and without requiring vertical scrolling for a window height of 256 px or horizontal scrolling for a window width of 320 px (except in special cases)?
- Criterion 10.13: On each web page, are additional contents appearing on focus or hover of an interface component controllable by the user (except in special cases)?
- Criterion 11.3: In each form, are labels associated with fields having the same function and repeated on the same page or across a set of pages consistent?
- Criterion 11.4: In each form, are each field label and its associated field adjacent (except in special cases)?
- Criterion 11.5: In each form, are fields of the same type grouped together when necessary?
- Criterion 11.6: In each form, does each group of fields of the same type have a legend?
- Criterion 11.7: In each form, is each legend associated with a group of fields of the same type relevant?
- Criterion 11.8: In each form, are items of the same type in a selection list grouped in a relevant way?
- Criterion 11.12: For each form that modifies or deletes data, or submits answers to a test or exam, or whose validation has financial or legal consequences, can the entered data be modified, updated, or retrieved by the user?
- Criterion 12.1: Does each set of pages provide at least two different navigation systems (except in special cases)?
- Criterion 12.2: In each set of pages, are menus and navigation bars always in the same place (except in special cases)?
- Criterion 12.3: Is the "site map" page relevant?
- Criterion 12.4: In each set of pages, is the "site map" page accessible through an identical feature?
- Criterion 12.5: In each set of pages, is the search engine accessible in a consistent way?
- Criterion 12.10: On each web page, are single-key keyboard shortcuts (lowercase or uppercase letters, punctuation, numbers, or symbols) controllable by the user?
- Criterion 13.2: On each web page, opening a new window must not be triggered without user action. Is this rule respected?
- Criterion 13.3: On each web page, does each downloadable office document have, if necessary, an accessible version (except in special cases)?
- Criterion 13.4: For each office document with an accessible version, does this version provide the same information?
- Criterion 13.5: On each web page, does each cryptic content (ASCII art, emoticon, cryptic syntax) have an alternative?
- Criterion 13.6: On each web page, for each cryptic content (ASCII art, emoticon, cryptic syntax) with an alternative, is this alternative relevant?
- Criterion 13.7: On each web page, are sudden brightness changes or flashing effects used appropriately?
- Criterion 13.10: On each web page, can functionalities requiring complex gestures also be performed using simple gestures (except in special cases)?
- Criterion 13.11: On each web page, can actions triggered by a pointing device at a single point on the screen be canceled (except in special cases)?
- Criterion 13.12: On each web page, can functionalities that involve device motion or movement toward the device be achieved through an alternative method (except in special cases)?
Non-compliance
- Criterion 2.1: Does each frame have a frame title?
- Criterion 3.2: On each web page, is the contrast between text color and background color sufficiently high?
- Criterion 3.3: On each web page, are the colors used in interface components or informative graphical elements sufficiently contrasted?
- Criterion 4.13: Is each time-based and non-time-based media compatible with assistive technologies (except in special cases)?
- Criterion 6.1: Is each link explicit (except in special cases)?
- Criterion 6.2: On each web page, does each link have a label?
- Criterion 7.1: Is each script, if necessary, compatible with assistive technologies?
- Criterion 8.9: On each web page, tags must not be used solely for presentation purposes. Is this rule respected?
- Criterion 9.3: On each web page, is each list correctly structured?
- Criterion 11.9: In each form, is the label of each button relevant (except in special cases)?
Not applicable
Criteria for which the relevant content is absent from the audited pages (automatic detection via axe-core).
- Criterion 4.10: Is each automatically triggered sound controllable by the user?
- Criterion 4.11: Is the playback of each time-based media, if necessary, controllable via keyboard and any pointing device?
- Criterion 4.12: Is the use of each non-time-based media controllable via keyboard and any pointing device?
- Criterion 5.6: For each data table, are row and column headers correctly defined?
- Criterion 5.7: Is the cell/header association technique appropriate (except in special cases)?
- Criterion 5.8: Layout tables must not use elements specific to data tables. Is this rule respected?
- Criterion 7.4: For each script that triggers a change of context, is the user informed or in control?
- Criterion 8.7: On each web page, is each language change indicated in the source code (except in special cases)?
- Criterion 8.8: On each web page, is the language code for each language change valid and relevant?
- Criterion 10.14: On each web page, can additional contents appearing only via CSS be made visible using the keyboard and any pointing device?
- Criterion 11.1: Does each form field have a label?
- Criterion 11.2: Do labels make it possible to understand the exact function of the field?
- Criterion 11.10: In each form, is input validation used appropriately (except in special cases)?
- Criterion 11.11: In each form, is input validation accompanied, if necessary, by suggestions to help correct input errors?
- Criterion 11.13: Can the purpose of an input field be determined to facilitate autofill with the user’s data?
- Criterion 12.11: On each web page, are additional contents appearing on hover, focus, or activation of an interface component reachable via keyboard when necessary?
- Criterion 13.1: For each web page, does the user have control over each time limit that modifies content (except in special cases)?
- Criterion 13.8: On each web page, is each moving or blinking content controllable by the user?
Preparation of this Accessibility Statement
This statement was prepared on 24 April 2026.
Technologies used to build the website:
- HTML5
- CSS3 / SCSS / Bootstrap
- JavaScript / jQuery
- ARIA
- SVG
User Agents, Assistive Technologies, and Tools Used to Test Accessibility
Automated tests
This audit uses the axe-core tool to automatically detect accessibility issues.
Some RGAA criteria require manual verification and are not covered by this automated audit.
Manual tests
Additional tests are required to ensure proper rendering of content with assistive technologies, in accordance with the test environment described in the RGAA 4.1.2 reference baseline:
- Wave (Chrome plugin)
- Lighthouse (Chrome)
- Web Developer (Chrome plugin)
- WCAG Contrast Checker
Pages of the website that were subject to compliance checks:
- grenoblebusiness
- how-does-it-work
- the-app
- faq-frequently-asked-questions
- 18-bike-rental-mvelo
- 124-unlimited-access-to-public-bus-tram-transport
- 125-unlimited-access-to-public-bus-tram-transport-72hours
- 142-mon-cab-vert-lyon-grenoble-airport-transfer
- 143-mon-cab-vert-trajet-aeroport-geneve-grenoble
- 145-taxis-grenoblois-airport-transfer-grenoble-geneva
- 146-taxis-grenoblois-airport-transfer-grenoble-lyon
- 150-taxis-grenoblois-city-transfer
- 152-voi
- mobility-services
- all-offers
- advantages-discounts
- unlimited-public-transports
- online-shop
- terms-of-sales
- legal-notice
- g-pass-grenoble-alpes
- site-map
Feedback and Contact
If you are unable to access any content or service, you may contact the website administrator to be directed to an accessible alternative or to obtain the content in another format.
Remedies
This procedure should be used in the following case.
You have reported an accessibility issue to the digital accessibility contact at G-Pass Business that prevents you from accessing content or one of the portal’s services, and you have not received a satisfactory response.
Send a message to the Défenseur des droits: https://formulaire.defenseurdesdroits.fr
Contact the Défenseur des droits representative in your region: https://www.defenseurdesdroits.fr/saisir/delegues
Send a letter by post (free of charge, no stamp required):
Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07