Accessibility Statement — miamily.org
MiaMily is committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. MiaMily is actively working to increase the accessibility and usability of its website and, in doing so, aims to align with recognized accessibility standards and guidelines.
Need Help Right Now?
If you experience any difficulty using our website — including placing an order — please contact us directly. We are ready to assist you manually to complete your purchase or answer any questions:
Email: questions@miamily.com
Response time: 1–2 business days
Overtea SA – MiaMily | Via Muzzano 15a, 6924 Sorengo – Switzerland
Scope of This Statement
This Accessibility Statement applies to the website
www.miamily.org
Compliance Status
As of April 2026, the website has been evaluated against the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and Level AA success criteria. Based on the assessment results, the website is partially conformant with WCAG 2.1 because some parts of the content do not yet fully meet the standard.
MiaMily is currently executing a structured remediation plan to address the issues identified during the audit and to progressively improve the experience for all users.
What We Are Actively Improving
The following areas were identified during the April 2026 audit as requiring improvement. For each issue, we describe both the technical finding and its real-world impact on users.
Screen reader descriptions for images
103 images currently lack descriptive text alternatives. We are adding alt text to all meaningful images so that users who are blind or have low vision — and rely on screen readers — can fully understand the content of each page.
Color contrast for readability
96 instances of insufficient color contrast were identified. This affects users with low vision or color blindness who may find certain text difficult or impossible to read. We are updating color combinations across the site to meet the minimum contrast ratio required by WCAG (4.5:1 for standard text). Color contrast is one of the most common and impactful accessibility issues, and we are prioritizing it accordingly.
Text resizing compatibility
29 issues were found where enlarging text up to 200% caused content to break or become unusable. We are fixing these so that users who need larger text — including those with low vision — can still access all content and features without loss of functionality.
Skip navigation links
25 pages are missing a mechanism that allows keyboard and screen reader users to skip past repeated navigation menus and jump directly to the main content. We are adding skip-to-content links across all pages to make navigation faster and less frustrating for these users.
Form behavior on input
1 instance was found where a form element triggers an unexpected page change when a user makes a selection. We are correcting this so that changes only happen when explicitly confirmed by the user, preventing confusion especially for users relying on assistive technologies.
Page code structure and semantics
12 code-level issues were found that may cause assistive technologies — such as screen readers — to misinterpret or skip content. We are cleaning up the underlying HTML to ensure all tools can read and present the page correctly.
Interactive element labeling
5 interactive components (such as buttons and form fields) lack proper names or roles. We are adding appropriate labels so that screen reader users know what each element does before interacting with it.
What Is Already Working Well
At the time of the assessment, no failures were identified for the following areas. These represent aspects of the site that already support accessible use:
Logical structure and relationships within content (SC 1.3.1)
Correct identification of form input fields such as name, email, and address (SC 1.3.5)
Text spacing flexibility — users can adjust line height, letter spacing, and word spacing (SC 1.4.12)
Time limits on interactive processes — users are given enough time to complete tasks (SC 2.2.1)
Moving or auto-updating content can be paused or stopped (SC 2.2.2)
Every page has a clear, descriptive title (SC 2.4.2)