Accessibility statement

Summary

After the fixes of October and November, axe finds no violations across the 156 pages, and the manual checks confirm contrast, focus, the 320 px layout and control names. No issues remain open.

What conforms

• Text alternatives on every image, and a description for every video 1.1.1 · 1.2.1
• Headings, lists, tables, landmarks and header sentences exposed to assistive technology 1.3.1
• Meaningful reading order, no instructions that rely on shape or position, any orientation 1.3.2 · 1.3.3 · 1.3.4
• Personal form fields declare their purpose 1.3.5
• Text contrast on every background, video included; colour is never the only cue 1.4.1 · 1.4.3
• The calligraphic “tomorrow” on the home page is a 21 group brand element, as on the other 21 sites, and falls under the logotype exception; the real text is there for assistive technology 1.4.5
• Pages readable at 320 px, text resizable to 200%, custom text spacing without loss 1.4.4 · 1.4.10 · 1.4.12
• A focus ring at 3:1 on every background, light or dark, always visible 1.4.11 · 2.4.7
• Menus and filters close with Esc and never trap the content beneath 1.4.13
• Everything works from the keyboard with no traps; the mobile menu and the bios hand focus back 2.1.1 · 2.1.2 · 2.4.3
• A pause control on each of the four videos that play by themselves 2.2.2
• Nothing flashes 2.3.1
• A skip link, first in the tab order on every page 2.4.1
• Every page has a title; every link has a name and says when it opens a new tab 2.4.2 · 2.4.4
• More than one way to reach a page; descriptive headings and labels 2.4.5 · 2.4.6
• The focused element never slides under the fixed bar 2.4.11
• No complex gestures, actions fire on release, targets at least 24 px or well spaced 2.5.1 · 2.5.2 · 2.5.8
• Every control’s name contains its visible label 2.5.3
• Language declared on every page 3.1.1
• Consistent navigation and naming, no unexpected change of context, contact details always in the same place 3.2.1 · 3.2.2 · 3.2.3 · 3.2.4 · 3.2.6
• Contact form with labels, described errors and focus moved to the first field to fix 3.3.1 · 3.3.2 · 3.3.3
• Correct name, role and state on every control; the cookie banner keeps focus while it is open 4.1.2
• The newsroom filter announces its result 4.1.3

Method and scope

• Automated testing with axe-core against the WCAG 2.2 A and AA rules, on all 156 pages of the built site, in English and Italian.
• Manual checks for what axe cannot judge: text contrast over video and photos, pixel by pixel across several frames; the keyboard on every page template, with each focus ring photographed on and off; the pause controls; a 320 px viewport on every page; text spacing; the contact form; the cookie banner.
• Contrast ratios computed with the WCAG formula from the actual colours, not judged by eye.
• Regression check: npm run test:a11y checks the structural fixes already made against the built site.

The four videos are silent, with no audio track in the files, which is why captions, audio description and audio control do not apply.

The cookie widget (iubenda) is third-party software: the site embeds it but does not build it. It is measured all the same, in production on 21tages.eu, because it is the first thing every visitor meets: on the first Tab, focus moves into the banner and stays there, the container is a named alert dialog, and axe finds no violations.