Accessibility Statement

Gewiss S.p.A. is committed to making its application accessible, in accordance with Italian Law No. 4 of 9 January 2004.

This Accessibility Statement applies to the app "ThermoICE 2.0 - Android".

Compliance status

This application is partially compliant with the requirements set out in Annex A of the UNI EN 301 549 (WCAG 2.1), due to the cases of non-compliance and/or exemptions listed below.

Non-accessible content

The contents listed below are not accessible for the following reason: non-compliance with Law No. 4 of 9 January 2004.

In preparing this accessibility statement, we took into account the WCAG 2.1 standards and the user experience of a test panel made up of people with different disabilities, who tested the app using the assistive technologies and accessibility features available on Android devices, such as the TalkBack screen reader for blind people and the magnification features.

The cases of non-compliance and the related WCAG success criteria are listed below:

• 1.1.1 Non-text Content: some meaningful graphical content does not have an adequate text alternative or is exposed to assistive technologies with meaningless information.
• 1.3.1 Info and Relationships: in some cases, the information, structure and relationships conveyed visually are not available in text form or cannot be correctly recognised by assistive technologies.
• 1.3.2 Meaningful Sequence: in some cases, the reading order detected by assistive technologies does not reflect the logical and visual sequence of the content, making the relationships between pieces of information unclear.
• 1.3.4 Orientation: some content or functionality is only available in a specific screen orientation, even when that orientation is not essential.
• 1.4.1 Use of Color: in some cases, colour is the only means used to convey information, indicate a status, distinguish an element or signal a required action.
• 1.4.3 Contrast (Minimum): in some cases, the contrast between text and background is not sufficient to ensure adequate readability.
• 1.4.4 Resize Text: when text size is increased up to 200%, some content or functionality does not remain fully available or appears overlapping, cut off or difficult to use.
• 1.4.11 Non-text Contrast: some user interface components, status indicators and graphical elements required for understanding have insufficient contrast against adjacent colours.
• 2.1.1 Keyboard: some functionality cannot be fully operated via a keyboard or an equivalent interface, preventing access for users who do not use a pointing device.
• 2.1.2 No Keyboard Trap: in some cases, keyboard focus remains trapped within a component and cannot be moved away using standard navigation commands.
• 2.2.1 Timing Adjustable: where time limits are set, it is not always possible to turn them off, adjust them or extend them when this would be necessary to allow the user to complete the task.
• 2.4.4 Link Purpose (In Context): the purpose of some links cannot be determined from the link text or its associated context, making it difficult to predict the destination or the action triggered.
• 2.4.6 Headings and Labels: some headings or labels do not describe clearly enough the topic, purpose or function of the associated content and controls.
• 2.4.7 Focus Visible: during keyboard navigation, the focus indicator is not always visible or sufficiently recognisable, making it difficult to identify the active element.
• 2.5.1 Pointer Gestures: some functionality requires complex, path-based or multipoint gestures, without offering an alternative that can be operated with a single pointer.
• 3.2.2 On Input: changing the value or state of some controls causes an unexpected change of context without the user having been informed beforehand.
• 3.3.2 Labels or Instructions: some fields or controls requiring data input do not have sufficiently clear labels or instructions to understand their purpose and how to fill them in.
• 3.3.3 Error Suggestion: when an error is detected and the way to correct it is known, useful guidance for resolving it is not always provided.
• 4.1.2 Name, Role, Value: for some user interface components, the name, role, state or value is not correctly communicated to assistive technologies, or the related changes are not made programmatically available.

Accessibility statement preparation

This statement was prepared on October 13th, 2026.

It was written after completing an accessibility evaluation by means of a third-party assessment.

How to send reports and contact details of the provider

Users can, at any time, report any accessibility issues. To do so, they can write directly to: accessibility@polifin.it.

Any questions and reports will be answered within 30 days of receipt.

Reports falling outside the scope of accessibility legislation cannot be handled; we therefore recommend that you use the contact details provided on the website of the company to which the report is addressed.

Personal data will be processed in accordance with the privacy notice.

How to send reports to Italian Authority for Digital Accessibility (AgID)

In the event of an unsatisfactory response or no response within thirty days of the notification or request, the person concerned may submit a report using the following link https://www.agid.gov.it.

Application information

Application publication date: September 11th, 2026

Did the owner of the website run usability tests? Yes

Framework used: Flutter

Operating system: Android

Inclusion in the workplace

Number of employees with disabilities in the company: 85

Number of adapted workstations for employees with disabilities: 0