Accessibility
declaration

Accessibility Declaration Model for website and mobile application for subjects referred to in art.3 paragraph 1-bis of Law No. 4 of 9 January 2004
Gi.Di. Meccanica s.p.a. undertakes to make its website accessible, in accordance with law no. 4 of 9 January 2004 (“Legge Stanca”) published in the Gazzetta Ufficiale no. 13 of 17/01/2004 and subsequent Legislative Decree no. 106 of 10/08/2018, which implemented EU Directive 2016/2102 of the European Parliament and of the Council. This declaration of accessibility applies to the domain gidimeccanica.com

Compliance

Partially compliant in accordance with UNI CEI EN 301549:2022 Reference technical specifications used: WCAG 2.1 This site is partially compliant with the requirements of Appendix A of standard UNI CEI EN 301549:2022 due to the cases of non-compliance listed below and better described in the relevant assessment model held by the provider.

Non-accessible contents

Some contents are not accessible due to partial or incomplete non-compliance with the provisions of Appendix A of standard EN 301549:2022

● C.9.1.1.1 – Non-text content – WCAG 1.1.1 level A Some non-text content presented to the user does not have an equivalent text alternative that serves the same purpose;
● C.9.1.2.1 – Audio-only and video-only (pre-recorded) – WCAG 1.2.1 level A Some timed media elements do not have text alternatives that are useful for defining their purpose or meaning;
● C.9.1.3.1 – Info and relationships – WCAG 1.3.1 level A In some cases, information, structure, or relationships conveyed by the presentation cannot be determined programmatically or are not available through text;
● C.9.1.3.5 – Identify Input Purpose – WCAG 1.3.5 level AA The purpose of some input fields for user information cannot be determined programmatically;
● C.9.1.4.1 – Use of color – WCAG 1.4.1 level A In some cases, colour is used as the sole visual means of representing information, actions, requesting responses or as a visual distinguishing feature;
● C.9.1.4.3 – Contrast (minimum) – WCAG 1.4.3 level AA In some cases, the visual representation of text and images containing text has a contrast ratio of less than 4.5:1, except where provided for by law;
● C.9.1.4.5 – Images of text – WCAG 1.4.5 level AA In some cases, text images are used to convey information instead of actual text, even though the technology allows for it;
● C.9.1.4.10 – Reflow – WCAG 1.4.10 level AA In some cases, the content requires scrolling in two dimensions, resulting in a loss of information or functionality for devices with a width of 320px and a height of 256px;
● C.9.1.4.11 – Non-text contrast – WCAG 1.4.11 level AA In some cases, the visual presentation has a contrast ratio of less than 3:1 compared to adjacent colours;
● C.9.2.1.2 – No keyboard trap – WCAG 2.1.2 level A Some components that receive keyboard focus do not allow consistent use of the keyboard when entering or exiting the component itself;
● C.9.2.4.4 – Link purpose (in context) – WCAG 2.4.4 level A In some cases, the purpose of certain links cannot be determined solely from the text of the link or from the text of the link together with the contextual content;
● C.9.2.4.7 – Focus visible – WCAG 2.4.7 level AA The focus indicator is not visible when the user interface is operated using a keyboard;
● C.9.3.1.2 – Language of parts – WCAG 3.1.2 level AA The language of each passage or sentence in the content cannot be determined programmatically, even when it does not involve proper names, technical terms, or jargon;
● C.9.3.3.1 – Error identification – WCAG 3.3.1 level A In some cases, when an input error is automatically detected, the item in error is not identified or the error is not described in text form;
● C.9.3.3.3 – Error suggestion – WCAG 3.3.3 level AA In some cases, when an input error is detected and suggestions are known, the erroneous element is not identified and/or the error is not provided to the user;
● C.9.4.1.2 – Name, role, value – WCAG 4.1.2 level A In some cases, the name or role of components cannot be determined programmatically; statuses, properties, and values that can be set by the user cannot be set by the program, or notifications about status changes are not available.
● C.9.4.1.3 – Status messages – WCAG 4.1.3 level AA In some cases, status messages in markup content cannot be determined programmatically by role or property without receiving focus

Drafting the accessibility declaration

Date of drafting this declaration: 13/07/2025 The information contained in this accessibility statement has been obtained from an assessment carried out by third-party assessment with UNI 11621-3 qualifications, registration number ECFPROFESSIONAL2025-000080, through objective and subjective analysis (see Article 3, paragraph 1, of Commission Implementing Decision EU 2018/1523). Assessment methodology: technical and manual assessment

Techniques used to verify criteria

A mix of automatic and semi-automatic validators promoted by the W3C, listed in the W3C Evaluation Tools List, were used. Assistive technologies such as screen readers, voice access, keyboard navigation and talkback, including NVDA, JAWS, ChromeVox, Amplificatore, Gboard, Voice Access, TalkBack, Accessibility Scanner, Switch access, VoiceOver and SpokenContent, were used. A manual inspection was conducted with manipulation of the ‘DOM’ (Document Object Model) source code using DevTools, Web Developer toolbar, Lighthouse, Pagespeed, WebIAM, Siteimprove, A11y, AxeCore, Silktide inspector, AccessiWeb scanner, AccessiWeb API with AgilityPack, AccessiWeb Webserver, zoom, high contrast, rendering with ‘Emulate vision deficiencies’, verification of ARIA roles and attributes, markup semantics and parsing. Testing on different combinations of browsers, devices, resolutions, orientations and user agents for a total of 117 control techniques, which are described in more detail in the relevant assessment model held by the provider.

Reporting and contact details

The provider provides the feedback mechanism to be used to notify cases of non-compliance and to request information and content that is excluded from the scope of the Directive. For this purpose, any complaints should be sent to: accessibilita@gidimeccanica.com

How to send reports to AgID

In the event of an unsatisfactory reply or failure to reply within thirty days to the notification or request, the person concerned may send a complaint using the link www.agid.it or by writing to protocollo@pec.agid.gov.it

Site information

Website publication date: 29/06/2026
Usability test carried out: YES
Content Management System (CMS) used: WordPress
Framework used: n.d.
O.S.: n.d.

Company information

Number of employees with disabilities present: 4
Number of workstations for employees with disabilities: 0
Last updated: 06/07/2026
The Accessibility Declaration model for website and mobile application has been created in compliance with the Law “Provisions to favour and simplify the access of users and, in particular, of persons with disabilities to IT tools”, Law 9 January 2004, n.4 or “Legge Stanca” following the “Declaration of Accessibility model website and mobile application for the subjects referred to in Article 3 paragraph 1-bis of Law 9 January 2004, n.4” Annex 1.