Accessibility Statement

Partially conformant. The site was self-assessed and manually reviewed on 2 October 2026 against WCAG 2.2 level AA.

Most content and components meet the criteria. Known exceptions are listed in section 5 and are limited to third-party components I do not control.

The site is evaluated against:

WCAG 2.2, Web Content Accessibility Guidelines, level AA (W3C Recommendation, October 2023)
Italian Law 13 March 1988 no. 104 and subsequent amendments, articles 55 onwards
AgID guidelines for the measurability and monitoring of web accessibility (2021)
European Accessibility Act, transposed in Italy, applicable to e-commerce services

All level A and AA criteria of WCAG 2.2 were reviewed. In particular the criteria covering structure and orientation (1.3.1, 1.3.2), text alternatives (1.1.1), minimum contrast (1.4.3, 1.4.11), keyboard navigation (2.1.1, 2.1.2, 2.4.1, 2.4.3, 2.4.7), changes of context (3.2.1, 3.2.2, 3.2.3, 3.2.4), accessible name and role (4.1.2), status messages (4.1.3) and ARIA landmarks (2.4.1).

Semantic structure with identified header, nav, main and footer; a 'Skip to main content' link as the first focusable element.

Consistent heading hierarchy on every page, with no skipped levels.

Colour contrast verified against the real theme, not only the default one.

All interactive controls are reachable and operable by keyboard, with a focus indicator that is always visible.

Decorative icons marked aria-hidden; meaningful icons carry alternative text.

Forms with explicit labels, required states declared, and error messages associated to their input via aria-describedby.

Status messages (form submission, loading) announced with role=status or aria-live.

Dynamic content (response messages) announced without moving focus.

Reduced motion: animations respect prefers-reduced-motion and the cookie banner can be printed without interference.

Selectable text and 200% zoom without loss of content or functionality, including on mobile.

No information conveyed by colour alone.

Cookie banner: while the consent window is open, the underlying content remains in the document flow because the banner does not use a modal dialog that traps navigation. Some screen reader users may need to dismiss it explicitly to reach the content.

Third-party advertising: the content and behaviour of ads depend on Google AdSense and are outside my control. They are not always labelled as advertising in an accessible way and may not meet the required contrast. They appear only if you accept the advertising category.

Amazon affiliate links: visually labelled, but the textual indication for screen reader users is not always complete.

Netlify Identity widget: the third-party script is also loaded on public pages, where it is never used. It introduces no visible content or focus traps, but it does add an unnecessary network request.

Semantic HTML with ARIA landmarks; role and aria-* attributes only where native markup is insufficient.

Visible focus that is never removed, managed with :focus-visible so mouse users are not penalised.

Support for prefers-reduced-motion, prefers-contrast and forced-colors where applicable.

No text baked into images: information is always available as real, selectable, indexable text.

Lighthouse Accessibility (Chrome), axe DevTools and WAVE, run on the main pages in both Italian and English.

Manual keyboard verification across all flows: navigation, services page, contact form, playbook download and the cookie panel.

This check is part of the definition of 'done' for every change, alongside TypeScript and ESLint at build time.

If you find an accessibility problem, write to [email protected] with the page, the problem and, if possible, the assistive technology you use. I reply within 5 business days and, when the problem affects a shared component, the fix goes into the next development cycle.

Reports are logged with the page, the WCAG criterion involved and the impact. Issues that block reading or use of content take top priority and are fixed before any new feature.

If you consider the response inadequate you can lodge a complaint with AgID or the Italian Data Protection Authority.

This statement is reviewed at least once a year, and whenever site content, structure or components change significantly. The date at the top always reflects the latest review. Substantial changes are announced on the home page.