---
title: "Accessibility · Ing. Massimiliano Brasile"
description: "Which standard this site is measured against, with which tools, what automated checks cannot see and how to report a barrier."
url: https://brasile.pro/en/accessibility/
lang: en
---
Accessibility

# Accessibility is measured, not claimed.

The reference is WCAG 2.2 level AA. Below is what was checked, with which tool, and what stays outside any automated check.

## The standard

WCAG 2.2 level AA, in force since 5 October 2023, which includes 2.1: every earlier criterion still applies. The European standard EN 301 549, in the version cited in the Italian Official Journal, still refers to 2.1, so measuring against 2.2 covers both.

## How the site is built

- static pages with no JavaScript, which work even if scripts are off or never arrive
- one level of navigation, the same items on every page, and a link to skip it
- text that resizes without losing content, no zoom lock
- no automatic animation, and transitions switch off with the system preference
- tables carry real headers, not just bold text

## What was measured

The static check runs on every page. The others run on a sample, one page per type in both languages: pages come from nine templates, and a defect in a template repeats identically across all its pages.

| Tool | What it checks | Result |
|---|---|---|
| **axe-core** | the WCAG 2.2 A and AA rules that only show when the page runs, contrast included | no violation across fourteen pages, one per type, Italian and English |
| **a11y_check** | language, title, heading order, tables with headers, links that say where they go | no finding across 47 pages |
| **wcag22.py** | the new 2.2 criteria, obscured focus (2.4.11) and targets under 24 px (2.5.8) | no obscured focus; the only targets under 24 px are links inside a sentence, which the criterion exempts because their height is the height of the line |
| **larghezza.py** | whether a text block leaves half the page empty on a wide screen | no narrow block at 1600 and 1920 px |
| **W3C Nu, Jigsaw** | valid HTML and CSS, on the served pages and not on the sources | zero errors on all 47 pages and the stylesheet |

## What no automated check can see

A clean report says there are no mechanical barriers, not that the site is accessible. Four things stay outside every tool, and on those a reader's report is worth more than any measurement.

- the reading order with a screen reader
- the full keyboard path, from the first item to the last
- the contrast of text that ends up over an image
- whether an alternative text really says what needs knowing

## If you hit a barrier

Write what you were doing, with which software and on which page. The answer arrives within five working days, and if the fix takes longer I say so with a date.

[info@brasile.pro](mailto:info@brasile.pro)

## Why this page exists

Directive (EU) 2019/882 exempts microenterprises providing services, and a single professional's practice is one. So this statement is voluntary: it is here because a site selling compliance software cannot get away with saying that the rule does not apply to itself.

Last revised: 18 September 2026

## Sources

- [WCAG 2.2, the W3C guidelines](https://www.w3.org/TR/WCAG22/)
- [Directive (EU) 2019/882, European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj)
- [EN 301 549 version 3.2.1 (ETSI, PDF)](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf)