Version [LEGAL:policy-version-pending] · effective date [LEGAL:effective-date-pending]
The product targets accessible use across the website and mobile app, but this draft does not claim WCAG conformance before an independent audit and real-device testing.
Version [LEGAL:policy-version-pending] · effective date [LEGAL:effective-date-pending]
This statement covers the first-party website and mobile app. Legal scope, including any microenterprise exemption, depends on the confirmed provider and must be assessed rather than assumed.
The statement covers https://anthonystilo.com and the Anthony Stilo iOS and Android application. The current status is: assessment in progress and not yet declared conformant. The accountable accessibility review status in configuration is pending.
The design and engineering target is WCAG 2.2 Level AA, using perceivable, operable, understandable and robust interaction as working principles. A target is not a certification. The applicable requirements for e-commerce services and mobile applications under Spanish and EU law must be confirmed against the final entity and service.
The website includes a skip link, semantic landmarks and headings, keyboard-native controls, visible labels, responsive layouts and localized content. The product uses text alternatives for curated images and status text for important states. These implementation details require automated and manual verification and do not by themselves establish conformance.
The intended experience supports keyboard navigation, screen readers, zoom and reflow, colour-independent meaning, reduced-motion preferences where motion exists, and portrait or landscape use on common mobile and desktop sizes. A supported browser, assistive-technology and operating-system matrix has not yet been approved.
Independent WCAG testing, screen-reader journeys, switch/voice control, 200–400% zoom, high contrast, reduced motion, authentication/OAuth, Turnstile, charts or game interaction, error recovery and native WebView semantics remain launch checks. Dynamic and AI-generated text may have quality issues. Any inaccessible critical path must be fixed or given an equivalent accessible route before launch.
Booksy, Google, Apple and other external interfaces are outside direct control, although an accessible first-party explanation and alternative contact route should be provided where a critical service relies on them. User-submitted or legacy media may not initially meet the same standard and requires moderation, captions or alternatives where applicable.
If you encounter a barrier, contact [LEGAL:support-contact-pending] with the page or app screen, what you were trying to do, your device or assistive technology if you wish to share it, and the format or assistance you need. Do not include passwords, authentication codes or unnecessary sensitive data. Response times and escalation ownership must be approved before launch.
If a reported barrier is not resolved, any statutory complaint or enforcement route depends on the applicable accessibility and consumer law and the confirmed provider status. This draft does not name an authority or claim an exemption without that assessment. Mandatory remedies remain available.
This draft was prepared from a source and content review dated 1 August 2026, not from a completed independent audit. It must be updated after automated checks, manual keyboard and screen-reader testing, native iOS/Android testing, third-party-flow review and remediation. Material releases should repeat those checks.
Help improve access
The support route will be published only with a real, monitored contact.
