SITE INFORMATION / EN
Accessibility
The site is designed so that the research content remains usable across devices and input methods. This page describes practical design choices; it is not a claim of formal accessibility certification.
AT A GLANCE
Before the detail
- Keyboard-friendly primary navigation and a skip-to-content link.
- Text labels for form fields and readable error messages.
- Responsive layout and support for prefers-reduced-motion.
- WCAG 2.2 is used as a reference without claiming an audit that has not been performed.
01 / NOTE
Content should remain understandable without decoration
Pages use semantic HTML, heading structure and descriptive links. Decorative shapes are not intended to carry essential information. A reader should not need a particular animation or colour to understand a source, warning or instruction.
On smaller screens multi-column layouts collapse rather than requiring horizontal scrolling for ordinary text.
02 / NOTE
Keyboard and focus
A skip-to-content link appears when focused. Buttons, menu controls, links and form fields remain native HTML controls so browsers and assistive technologies can provide their standard interaction behaviour.
The design does not intentionally suppress the browser’s focus indicator. Any future visual change that makes keyboard position unclear should be treated as a defect.
03 / NOTE
Forms and errors
Consultation fields have text labels rather than relying on placeholders alone. The form does not use a visual puzzle or short timer as a condition for submission.
Only information needed to understand and answer the request is requested, and the form warns against sending passwords or financial credentials.
04 / NOTE
Motion preferences
The stylesheet respects prefers-reduced-motion. When the operating system requests less motion, decorative transitions and animations are reduced.
Movement is not the only way an important state is communicated, so reducing it should not block navigation or form use.
05 / NOTE
Language and readability
Italian and English editions declare their document language. Copy aims to explain specialist terms in context and uses link text that describes where a link goes.
Contrast and responsive typography are part of the design, but real devices, zoom levels and user settings can reveal issues that were not anticipated. Specific reports are therefore welcome.
06 / NOTE
WCAG 2.2 is a reference, not a badge
The project uses the W3C Web Content Accessibility Guidelines 2.2 as a reference for perceivability, operability, understanding and robustness. It does not claim that a formal AA or AAA conformance audit has been completed.
That distinction matters: a useful accessibility statement should describe what has been done and how to report a barrier, rather than claiming a certificate that does not exist.
07 / NOTE
Report a barrier
Please provide the page URL, browser or device if known, what you were trying to do and what prevented you from doing it. You can contact Ettore Dore at +39 334 243 5154 or use the consultation form and label the request as an accessibility issue.
There is no need to disclose a medical diagnosis. A description of the technical behaviour is enough to investigate the problem.
08 / NOTE
External official sources
Authority websites and public registers are operated by third parties. We can make the link and context clear, but we cannot change a third-party PDF, captcha, navigation system or accessibility implementation.
If a primary source is difficult to use, report it and we can try to identify an alternative official route without replacing the source with an unverified copy.