Villa Stuart Private Clinic
Villa Stuart is committed to making its website accessible, in compliance with Law 4/2004 (Legislative Decree of January 9, 2004) and in line with the principles of universal accessibility provided by the Web Content Accessibility Guidelines (WCAG) 2.1 – Level AA.
The website https://www.villastuart.it represents a significant advancement in terms of accessibility compared to the previous Squarespace platform.
| Aspect | Squarespace (Old) | WordPress + Elementor (New) |
|---|---|---|
| Alternative Text (Alt Text) | Absent or generic (alt=””) on galleries and images | Complete and descriptive on all visual assets |
| Focus Indicators | Not visible; limited keyboard navigation | Clear and visible on all interactive elements |
| Semantic HTML | Structure with generic <div> without semantics | HTML5 with semantic elements (<nav>, <main>, <section>, <article>) |
| Color Contrast | Not verified; possible contrast issues | Verified according to WCAG AA (ratio ≥4.5:1) |
| Keyboard Navigation | Mouse dependency; inline JavaScript without fallback | Fully accessible with Tab, Shift+Tab, Enter |
| ARIA Labels | Not implemented | Complete WAI-ARIA 1.2 for custom components |
| Language Declaration | Not explicit in code | Declared with lang=”it” in root HTML |
| Target Size (Interactive Elements) | Variable; some buttons too small | Minimum 48×48 pixels (WCAG AAA standard) |
| JavaScript Dependencies | Multiple proprietary Squarespace libraries | Minimalist; progressive fallback implemented |
| Accessibility Tools | Absent | Iubenda plugin with controls: zoom, contrast, guided reading, screen reader |
Features not available on Squarespace:
Solid foundations:
Problem in Old Site: Squarespace did not provide visible focus indicators; keyboard navigation was practically unusable for users who do not use a mouse.
Improvement: Clear and visible focus indicators on all interactive elements (colored outlines and focus rings).
Benefit: Users navigating with keyboard can easily identify the selected element; complete support for users with reduced mobility.
Implementation: Standardized CSS styling with visible outlines (min 3px) and focus rings with high contrast color.
Problem in Old Site: Squarespace HTML analysis reveals dozens of images with alt=”” (empty alt text), especially in service galleries.
Improvement: Descriptive and meaningful alt text on all visual assets (images, icons, galleries).
Benefit: Blind and visually impaired users fully understand content through screen readers; better SEO.
Implementation: Systematic auditing process on all images; templates with mandatory alt text fields; guidelines for meaningful descriptions.
Problem in Old Site: Generic links (“Read more”, “Click here”) common in Squarespace; difficult for screen readers to understand function.
Improvement: Link text always contextual and descriptive (“Discover cardiology services”, “Contact orthopedics department”).
Benefit: Users with screen readers clearly understand the function of each link without visual context.
Implementation: Systematic elimination of generic text; template review with descriptive link naming rules.
Problem in Old Site: Squarespace did not provide tools to verify contrast; Squarespace palette might not meet WCAG AA.
Improvement: Contrast ratio greater than 4.5:1 for text and buttons; systematic verification on all elements.
Benefit: Visually impaired users (5-8% of population) can read text without difficulty; text on colored backgrounds clearly readable.
Implementation: Design tokens with pre-verified WCAG AA contrast values (4.5:1 for text, 3:1 for components); validation tool in build.
Problem in Old Site: Squarespace uses non-semantic heading structures; visual builder does not guarantee logical H1→H2→H3.
Improvement: Logical and semantically correct H1→H2→H3 structure on all pages.
Benefit: Intuitive hierarchical navigation for screen reader users; ability to skip between main sections.
Problem in Old Site: Squarespace inline JavaScript does not support keyboard access; mobile menu depends on mouse clicks.
Improvement: All components navigable with Tab, Shift+Tab, Enter and arrows (expandable menus, dropdowns, carousels).
Benefit: Users who do not use a mouse (paralysis, tremors, motor disabilities) have complete access to all functions.
Problem in Old Site: Squarespace does not implement WAI-ARIA; custom components not correctly announced to screen readers.
Improvement: Correct ARIA-label, aria-describedby, aria-hidden and role attributes on custom components (menu, modal, tab).
Benefit: Screen readers correctly announce function, state and description of each element; consistent experience for blind users.
Problem in Old Site: Squarespace uses color only to indicate status (red error, green success); problematic for colorblind users.
Improvement: Status indicators with text, icons and patterns in addition to color (e.g.: error = red + X + “Error” text).
Benefit: Colorblind users (8% of men) and visually impaired understand messages, errors and states independently of color.
Problem in Old Site: Squarespace does not explicitly declare lang in HTML tag; screen readers use browser default language.
Improvement: lang=”it” attribute correctly declared on root HTML element.
Benefit: Screen readers correctly pronounce Italian text with appropriate intonation, accents and speed.
Problem in Old Site: Squarespace template has variable buttons and links; some interactive elements <40px (problematic for touch).
Improvement: All interactive elements with minimum 48×48 pixels (WCAG AAA standard; mobile-friendly).
Benefit: Users with reduced mobility, tremors or on touch devices (smartphones) have comfortable clickable areas; reduces errors.
Comparative analysis of HTML code based on direct analysis of the previous site (on Squarespace):
| Criterion | Squarespace HTML | WordPress + Elementor | Impact for Users |
|---|---|---|---|
| Alt Text on Images | <img alt=”” /> (empty) | Descriptive alt text | Blind users understand content |
| Focus Indicators | Absent | Colored outlines 3px minimum | Users navigating with keyboard |
| Semantic Elements | Generic divs | Semantic HTML5 | Screen readers read correct structure |
| Language Declaration | Not present | <html lang=”it”> | Screen readers pronounce correct Italian |
| ARIA Labels | No implementation | Complete aria-label, role | Screen readers announce element function |
| Keyboard Accessibility Menu | No Tab access | Complete Tab, Enter, Arrow access | Users who don’t use mouse |
| Color Contrast | Not verified | WCAG AA (4.5:1 minimum) | Visually impaired users read text |
| Link Text | “Read more” | “Discover services…” | Screen readers provide context |
| Cookie Consent | Script without labels | Iubenda with ARIA labels | Screen reader users accessible |
| Target Size | Some <40px | Minimum 48x48px | Touch and reduced mobility users |
The site has been subjected to security assessment regarding accessibility functions. 2 low-severity security vulnerabilities have been identified:
Status: No personal or sensitive data exposed through accessibility functions. GDPR compliance verified.
No content has been identified for which the application of accessibility criteria would constitute a disproportionate burden according to art. 3-ter, paragraph 7 of the Stanca Law.
However, we recognize that some historical content (videos, presentations) may require significant time for complete adaptation. These will be addressed in Phase 3 of the correction plan.
Aware that accessibility is a continuous process, Villa Stuart will implement a progressive improvement plan with coordinated releases:
Objective: Rapid implementation of critical features
Objective: Solid foundations for long-term accessibility
Objective: Accessibility excellence and external certification
The site implements the Iubenda Accessibility Plugin which provides users with:
If you encounter difficulties accessing any content or functionality of the site, we invite you to contact us through the following channels:
We commit to responding to all accessibility requests within 5 working days and to providing the requested information in an accessible format (e.g., large text, audio, simple format, etc.).
If you are not satisfied with our response or the solution provided, you can submit a complaint to the following competent authorities:
AgID is responsible for monitoring compliance with the Stanca Law.
For issues related to transparency in accessibility.
The accessibility of Villa Stuart’s website is based on the following technologies:
This declaration has been developed based on:
This declaration covers the following scope:
Villa Stuart is committed to: