Digital accessibility
Accessibility Statement
The RGAA compliance status of our booking engines, non-accessible content and how to contact us.
Contents
Our commitment
INTERFACE TECHNOLOGIES is committed to making its online booking engines accessible, in accordance with Article 47 of French Law No. 2005-102 of 11 February 2005.
To this end, INTERFACE TECHNOLOGIES is implementing the following strategy and actions:
- Implementation of a multi-year accessibility plan;
- Action plan for the current year (2026):
- conducting accessibility audits of the hotel and activities booking engines;
- training and raising awareness among technical teams;
- identifying priority corrective actions.
This statement was established on 2 March 2026. It was last updated on 15 September 2026.
1. Accessibility of the hotel booking engine
Compliance status
Not compliantThe booking engine is not compliant with version 4.1.2 of the French General Accessibility Improvement Framework (RGAA).
Test results
The internal compliance audit revealed that 45.65% of the criteria in RGAA version 4.1.2 are met on the audited pages. Seven criteria require additional verification.
Non-accessible content
List of non-compliant criteria:
- 1.1 – Informative images do not always have a text alternative.
- 3.1 – Some information is conveyed through colour alone.
- 3.2 – The contrast between text colour and background colour is sometimes insufficient.
- 3.3 – Colour contrast within interface components is sometimes insufficient.
- 6.1 – A link is not sufficiently descriptive.
- 6.2 – A link does not have a label.
- 7.1 – Some scripts are not compatible with assistive technologies and do not provide an alternative.
- 7.3 – Some scripts cannot be operated using a keyboard.
- 7.5 – Status messages are not announced by assistive technologies.
- 8.2 – The page source code contains HTML validation errors detected by the W3C validator.
- 8.3 – The default language declaration is missing.
- 9.1 – Headings are missing or improperly structured.
- 9.2 – The document structure contains defects.
- 9.3 – Lists are not properly structured.
- 10.7 – Some elements do not have a visible keyboard focus indicator.
- 10.8 – Hidden content is not intended to be ignored by assistive technologies.
- 11.13 – The purpose of certain input fields cannot be programmatically determined to facilitate autofill using the user’s data.
- 12.6 – Content grouping areas present across multiple pages (header, main navigation, main content, footer, and search engine) cannot be reached or bypassed.
- 12.7 – A skip link or direct access link to the main content area is not provided.
| Item | Details |
|---|---|
| Technologies used | HTML, Angular, REST |
| User agent | Chrome (145) |
| Assistive technology | NVDA (version 2025.3.2) |
| Evaluation tools | RGAA Assistant, Accessibility Insights, W3C HTML Validator, Colour Contrast Checker, Web Developer Toolbar |
Pages included in the compliance audit
As the booking engine is deployed on a dedicated URL for each hotel, the audit was carried out on a representative demonstration property.
The booking process consists of 5 steps:
- Search criteria page
- Offer selection page
- Options selection page
- Contact details and payment page
- Booking confirmation page
Please noteThis statement applies exclusively to the most recent version of the hotel booking engine.
An older version of the engine remains temporarily available for some properties. It has not been audited and is not covered by this statement. It is considered non-compliant with the RGAA and is currently being progressively replaced by the new version.
2. Accessibility of the activities booking engine
Compliance status
Not compliantThe booking engine is not compliant with version 4.1.2 of the French General Accessibility Improvement Framework (RGAA).
Test results
The internal compliance audit revealed that 25.64% of the criteria in RGAA version 4.1.2 are met on the audited pages. 26 criteria require additional verification.
Non-accessible content
List of non-compliant criteria:
- 1.1 – Informative images do not always have a text alternative.
- 1.2 – Decorative images are not correctly ignored by assistive technologies.
- 1.3 – Some text alternatives are generic and not relevant.
- 2.1 – Some frames do not have a title.
- 3.2 – The contrast between text colour and background colour is sometimes insufficient.
- 3.3 – Colour contrast within interface components is sometimes insufficient.
- 6.1 – Some links are not sufficiently descriptive.
- 6.2 – Some links do not have a label.
- 7.1 – Some scripts are not compatible with assistive technologies and do not provide an alternative.
- 7.3 – Some scripts cannot be operated using a keyboard.
- 7.4 – Users are not always warned of a change of context.
- 7.5 – Status messages are not announced by assistive technologies.
- 8.2 – The page source code contains HTML validation errors detected by the W3C validator.
- 8.3 – The default language declaration is missing.
- 8.6 – Page titles are not always relevant.
- 8.9 – Some tags are used for presentation purposes.
- 9.1 – Headings are missing or improperly structured.
- 9.2 – The document structure contains defects.
- 9.3 – Lists are not properly structured.
- 10.7 – Some elements do not have a visible keyboard focus indicator.
- 11.1 – Some form fields do not have a label.
- 11.5 – Fields of the same nature are not grouped.
- 11.6 – Field groups do not have a legend.
- 11.10 – Input validation is not used appropriately for some fields (lack of precision, information not available before submission).
- 11.11 – Some error messages do not help users correct their input (missing information about the expected format).
- 11.13 – The purpose of certain input fields cannot be programmatically determined to facilitate autofill using the user’s data.
- 12.6 – Content grouping areas present across multiple pages (header, main navigation, main content, footer, and search engine) cannot be reached or bypassed.
- 12.7 – A skip link or direct access link to the main content area is not provided.
- 12.11 – Some additional content is not keyboard accessible.
| Item | Details |
|---|---|
| Technologies used | HTML, jQuery, REST |
| User agent | Chrome (145) |
| Assistive technology | NVDA (version 2025.3.2) |
| Evaluation tools | RGAA Assistant, Accessibility Insights, W3C HTML Validator, Colour Contrast Checker, Web Developer Toolbar |
Pages included in the compliance audit
As the booking engine is deployed on a dedicated URL for each property, the audit was carried out on a representative demonstration property.
The number of steps in the booking process may vary depending on the type of property and services offered. The representative property audited offers a 6-step process:
- Date selection page
- Service selection page
- Time slot selection page
- Basket validation page
- Contact details and payment page
- Booking confirmation page
3. Feedback and contact
If you are unable to access any content or service, you can contact us to be directed to an accessible alternative or to obtain the content in another form.
Digital accessibility officer
Email: accessibilite@reservit.com
4. Enforcement procedure
This procedure applies if you have reported an accessibility issue to the website manager that prevents you from accessing content or a service, and you have not received a satisfactory response.
- Write a message to the Defender of Rights (Défenseur des droits)
- Contact your local Defender of Rights delegate
By post (free of charge, no stamp required, France only)
Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07
© Interface Technologies, 2026

