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 following Vezpa digital services:
| 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 (for property managers) | Android, iOS, Windows, macOS | Remediation in progress |
| Django admin website (for managers and staff) | Web | Remediation in progress |
Marketing website and Booking Engine, as consumer-facing services within the EAA scope, were audited and remediated on 22 May 2026. 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 treatment radios, 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 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, success criterion 1.3.1); the frequently asked questions accordions on the public pages, now keyboard operable and with their state announced (success 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 (success 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. The PMS app and the Django admin are undergoing voluntary remediation (not in the mandatory EAA scope as they are professional B2B management software).
3. Accessible content
Our consumer services 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 20 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 with screen readers NVDA (Windows), VoiceOver (macOS/iOS), TalkBack (Android)
4. Non-accessible or partially accessible content
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 to 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
- Modern browsers: Chrome, Firefox, Safari, Edge (last 2 stable versions)
- Screen readers: NVDA (Windows), VoiceOver (macOS, iOS), TalkBack (Android), Narrator (Windows desktop)
- 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
6. Evaluation methodology
- Static code audit of HTML/CSS/JavaScript templates
- Mapping of violations to WCAG 2.1 Success Criteria (Level A and AA)
- Keyboard navigation testing across the full booking flow
- Functional testing with screen readers across major browsers
- Colour contrast verification on the design system
- Planned runtime checks with automated tools (axe-core, Pa11y) integrated into the release process
7. Feedback procedure
If you encounter accessibility obstacles using our services, or wish to report a problem, please contact us:
Email: [email protected]
WhatsApp: +39 351 651 3663
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 required by Italian Legge Stanca Article 3-quinquies for accessibility feedback).
8. Enforcement procedure
If you receive an unsatisfactory response, or no response within 30 days, you may contact the Italian Digital Agency (AgID), the national authority responsible for accessibility monitoring, through the dedicated form:
- form.agid.gov.it/view/eaa/ — AgID feedback 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.