Accessibility Statement
1. Accessibility commitment
Vezpa is committed to making its website and digital services accessible in accordance with the obligations of the European Accessibility Act (EU Directive 2019/882), transposed in Italy by Legislative Decree 82/2022, in force from 28 June 2025 for consumer-facing e-commerce services. The technical standard applied is WCAG 2.1 Level AA (Web Content Accessibility Guidelines, W3C).
2. Compliance status
This statement applies to the Vezpa digital services listed in the following table:
| Service | Platform | WCAG 2.1 AA conformance |
|---|---|---|
| Booking Engine (consumer-facing reservation engine for our clients' properties) | Responsive web (desktop, tablet, mobile) | Conformant |
| Wellness Portal (SPA) (service booking and shop for guests of the properties) | Responsive web | Conformant |
| Marketing website (vezpa.it, landing pages, blog, guides) | Responsive web | Partially conformant |
| PMS application (reserved for property managers) | Android, iOS, Windows, macOS | Remediation in progress |
| Django admin website (reserved for managers and staff) | Web | Remediation in progress |
The marketing website and the Booking Engine, as consumer-facing services within the EAA scope, underwent an accessibility audit completed on 22 May 2026, followed by remediation. On 6 June 2026 a further runtime audit of colour contrast (axe-core and Pa11y) was carried out on all consumer pages — home, landing pages, blog, Booking Engine, statement — which now meet WCAG 2.1 AA criterion 1.4.3 (minimum contrast) with no exceptions detected by the automated tools. On 23 June 2026 a full remediation of the Booking Engine funnel was completed (BE templates): skip-link, <main> landmark, dynamic lang, focus-visible, form labels, modal ARIA, heading hierarchy, fieldset/legend for meal plans, Flatpickr role=group — the BE funnel is now conformant to WCAG 2.1 Level AA (0 axe violations on /prenota/casamia). One residual item (property logo on /pagamentoGrazie, criterion 1.4.3) is fixed in source CSS but requires collectstatic to propagate to the CDN. On 9 August 2026 an internal review extended the assessment to areas that had never fallen within the scope of the previous rounds and to files created after May. The following were fixed: the form labels of the online check-in (47 guest-details fields with no accessible name, criterion 1.3.1); the frequently asked questions accordions on the public pages, now keyboard operable and with their state announced (criteria 2.1.1 and 4.1.2); the top-level heading on six guest-facing pages (1.3.1); the check-in language selector (4.1.2); the labels of the services section in the Booking Engine (1.3.1); the alternative text on the identity document previews (1.1.1); the language declared by the translated guide pages, which were all served as Italian (criterion 3.1.1); and the Booking Engine navigation strings in Japanese, which fell back to Italian. In the internal management panel, the controls that opened dialog windows were made keyboard reachable. Also on 9 August 2026 a runtime audit with axe-core was carried out on ten sample pages (public website, booking engine, pricing pages, four guide pages in two languages, this statement and the tourist tax calculator). After the fixes the tool detects no confirmed violation of WCAG 2.1 A and AA criteria on the pages examined, and in particular no problem with accessible field names, heading hierarchy, declared language or ARIA attributes. There remain reports that the tool classifies as «to be checked manually», mostly concerning the contrast of text overlaid on gradient backgrounds, where the automated measurement is not conclusive. On 26 September 2026 those reports — 237 in all — were examined one by one, measuring contrast on the pixels actually drawn rather than on the style sheet alone. This revealed real defects that the tool did not declare as such: the booking engine calendar cells, which carried an accessible name ignored by screen readers because they had no role (61 cells, fixed); the language button, which announced a menu without having its semantics (fixed); and three low-contrast texts, fixed on all the translated pages to which they had been copied. The remaining reports were verified as conformant, with the measurement of each one recorded, and persist only because the automated tool cannot determine the background colour (gradients, pseudo-elements, overlaps). On 4 November 2026 automated verification was extended to all public pages in the sitemap, in all languages and on both desktop and phone (2,041 pages), and for the first time to the guest pages that do not appear there: online check-in, payment, cancellation, password recovery and the wellness portal. The following were fixed: the guest counters in the booking engine, now announced with their own label; the contrast of subtitles, notices and buttons on those pages, on legal documents and in emails; the tables and code blocks that scroll on phones, now keyboard reachable (criterion 2.1.1). On the same day keyboard navigation was tested on sample pages, finding no unreachable elements or traps. The contrast of buttons on mouse hover on an ochre background, which no automated check detects, remains to be defined. Automated checks do not replace testing with real users and assistive technologies, which remains our benchmark. The PMS app and the Django admin are undergoing voluntary remediation (not within the mandatory scope of the Italian EAA, as they are professional B2B management software).
3. Accessible content
The consumer services (Booking Engine, marketing website) are designed and maintained to meet the following requirements:
- Semantic HTML with landmarks (
header,nav,main,footer) and correct heading hierarchy - Skip-to-content link on every page, activatable by keyboard
- ARIA attributes for dynamic state of interactive components (menus, dropdowns, calendar, guest counters, tabs, modals)
- Text labels on all form controls, localised across 22 languages for booking engine buttons
- Descriptive alternative text on content images (room photos, property photos)
- Carousels with keyboard-accessible prev/next controls and pause on mouse hover
- Dynamic
langattribute on the page aria-current="page"on the active navigation link- Respect for the
prefers-reduced-motionsystem preference - AA-level colour contrast on text, controls and status indicators
- Keyboard focus visibility maintained on all interactive elements
- All
target="_blank"external links protected withrel="noopener noreferrer" - Tested on 5 November 2026 with the NVDA screen reader (Windows, Chrome) on the home, pricing, contact, booking, online check-in, cancellation and payment pages
4. Non-accessible or partially accessible content
The following content has known accessibility limitations, which are being resolved:
Known limitations
- PMS app (desktop and mobile): some custom widgets (planning grid, Gantt calendars) do not yet fully implement accessible semantics for screen readers. Remediation roadmap targets end of 2026.
- Django admin website: reserved for property staff, the interface contains some controls (admin dropdown menus) requiring further ARIA semantics.
- Third-party integrations: Stripe payment widget. These are maintained by their providers; Vezpa monitors their accessibility level.
- User-uploaded content: room photos, descriptions and content created by property operators may not always meet accessibility requirements (descriptive alt text, etc.). We provide tools and guidelines to help operators improve their content accessibility.
5. Assistive technology compatibility
The consumer services have been tested and are compatible with:
- Modern browsers: Chrome, Firefox, Safari, Edge (last 2 stable versions)
- Screen reader: NVDA (Windows, with Chrome), tested on 5 November 2026 on the main pages
- Keyboard-only navigation (Tab, Shift+Tab, Enter, Space, Esc, arrow keys)
- Content zoom up to 200% without loss of functionality
- System preferences: high contrast, reduced motion
VoiceOver, TalkBack and Narrator have not been tested yet.
6. Evaluation methodology
The conformance assessment was carried out through:
- Static code audit of the HTML/CSS/JavaScript of the main templates
- Mapping of violations to WCAG 2.1 Success Criteria (Level A and AA)
- Keyboard navigation testing across the full booking flow (excluding card payment, handled by Stripe)
- Test with the NVDA screen reader in Chrome (5 November 2026)
- Colour contrast verification on the design system
- Runtime contrast checks with automated tools (axe-core, Pa11y) carried out on the consumer pages (June 2026) and integrated into the release process
7. Feedback procedure
If you encounter accessibility obstacles using our services, find inaccessible content or wish to report a problem, you can contact us at the following addresses.
Email: info@vezpa.it
WhatsApp: +39 351 651 3663 (opens in a new tab)
Please include in your report: page or feature affected, type of problem, assistive technology used (if applicable), operating system and browser.
We commit to responding to accessibility reports within 30 days (procedure provided for by Article 3-quinquies of the Italian Legge Stanca for accessibility reports).
8. Enforcement procedure
If you receive an unsatisfactory response, or no response within 30 days of your report, you may contact the Agency for Digital Italy (AgID), the national authority designated for accessibility oversight, through the reporting form available on its institutional website:
- form.agid.gov.it/view/eaa/ (opens in a new tab) — AgID reporting form for the European Accessibility Act
9. Statement update
This statement is reviewed and updated at least annually, or when material changes to digital services occur or new remediation cycles are completed.