Accessibility statement

Fictilis S.r.l. is committed to making Calciopoly usable by as many people as possible, including those who navigate with the keyboard alone, with a screen reader, with the screen greatly magnified or without distinguishing colours.

This is not a decorative commitment: every technical choice listed below is in the site's code and is checked on every change by an automated tool that is part of the project. Where we have not got there yet, we say so in section 6 rather than keep quiet about it.

This statement covers the website calciopoly.it: the public pages, the tournament pages and the organiser's area, in all five languages in which the site is available.

Italian Legislative Decree 82/2022, which implements the European Accessibility Act, requires providers of e-commerce services to state in their general terms how the service meets accessibility requirements. The same decree exempts micro-enterprises providing services. Fictilis S.r.l. falls within that threshold: this statement is therefore not required of us.

We publish it anyway, and from here on it binds us as though it were. We say so precisely, because precision is the point: we do not claim an obligation we do not have, and we do not use the exemption as a reason not to do the work.

The technical reference is the European standard EN 301 549, which for web content refers to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. It is the same reference set out in the Guidelines of the Agency for Digital Italy on the accessibility of services, adopted by determination no. 38 of 4 March 2026.

WCAG 2.2 is not yet referenced by the harmonised European standard, and so is not our reference: when it becomes so, this page will say it.

Partially compliant with WCAG 2.1 level AA: most criteria are met, some are not, for the reasons listed in section 6.

The assessment is a self-assessment, carried out by whoever develops the site. No third-party audit has been commissioned: saying so is part of the honesty of this page. If we ever commission one, this line will change and will name who carried it out and when.

Keyboard. Every function is reachable with the Tab key, with no traps. Focus is always visible with sufficient contrast. The first element on every page is a «Skip to content» link that bypasses the menus, and that genuinely moves focus — not just the page position.

Structure. One first-level heading per page, heading hierarchy respected, landmark regions declared (header, content, footer). Standings and fixtures are real tables, with column and row headers declared: the abbreviations «P», «W», «GD», «Pts» carry their full names alongside, read out by assistive technology.

Colour and contrast. Contrast ratios are measured, not eyeballed: a project tool computes every colour pair on the site on every change and blocks release if one falls below the threshold. No information is conveyed by colour alone: match outcomes and statuses always carry a word as well.

Language. Every page declares its own language, and every entry in the language selector declares its own: an Italian screen reader does not read «Deutsch» as Italian.

Motion. Animations are few and all stop when the operating system says less motion is preferred. Nothing flashes, no carousel scrolls by itself.

Magnification. Zoom is not blocked and pages stay usable up to 200%. No text is inside an image.

Touch. Tappable areas measure at least 44 pixels a side, even where the icon drawn inside is smaller.

Forms. Every field has an associated label. On the sign-in and registration pages the error message receives focus as soon as it appears: those who cannot see the screen are taken to the error, instead of facing an apparently identical page.

Content uploaded by organisers. Names, descriptions, rules, team logos and colours are written and chosen by whoever organises the tournament, not by us. A logo uploaded without a sensible name, or rules pasted in as one block, make that page less accessible, and we can only limit the damage: the colour of the text on team badges, for instance, is computed by us so that it stays readable whatever shade is chosen.

The payment page. It is Stripe's, not ours: its accessibility is Stripe's responsibility.

Live coverage. During a match, minutes, scores and events update by themselves. On a busy match, listening with a screen reader remains tiring. The single-match page, static and complete, is always available as an equivalent alternative.

What the automated check does NOT cover. The tool we use checks page structure and the site's colour contrasts, but cannot replace a real trial: actual focus order, behaviour with real screen readers, reflow beyond 200% magnification and text contrast over images and gradients all fall outside it. Those we check by hand, and less often. Saying so is more useful than promising a coverage no automated tool can give.

If a page, a function or a piece of content on Calciopoly is inaccessible to you, write to the address below. Give the page address, what you were trying to do and with which tool (browser, screen reader, magnification): two lines are enough.

We reply within thirty days. If the barrier comes from content uploaded by an organiser, we contact them; if it comes from us, we tell you when we expect to remove it — and if we cannot remove it, we offer you another way to obtain the same information.

If our reply does not satisfy you, you may turn to the Agency for Digital Italy (AgID), which supervises the accessibility of digital services and since March 2026 provides a platform for reporting non-compliance.

This statement was drawn up on 28 July 2026, using the self-assessment method described in section 4. We review it at least once a year and in any case whenever the interface changes significantly.

If you find a sentence on this page that does not match how the site actually behaves, that sentence is a defect: report it to us as you would a broken button.

The latest automated check dates from 28 July 2026 and examined 24 pages and 16 colour combinations, finding no blocking violations. The check is repeatable: anyone with the code can run it again and obtain the same outcome, because the result is archived together with the exact version of the site it refers to.