Legal area / Apps accessibility
1 Accessibility Statement - Armani Exchange Connected iOS
1.1 Section 1
The Armani Group undertakes to make its mobile application accessible, in accordance with Italian Law no. 4 of 9 January 2004.
Content in compliance with EU Implementing Decision 2018/1523.
The following accessibility statement applies to the Armani Exchange Connected mobile application 5.1.8.
1.1.1 Compliance status
Partially compliant.
This mobile application is partially compliant with the requirements of Appendix A of the UNI EN 301549:2018 standard (WCAG 2.1) and the requirements pursuant to annex A of the Italian Ministerial Decree of 5 July 2005 (WCAG 2.0) due to the cases of non-compliance listed below.
1.1.2 Inaccessible content
The contents listed below are not accessible for the following reasons:
· non-compliance with Italian Law no. 4 of 9 January 2004
1. There are buttons without labels; therefore, the WCAG 1.1.1 success criterion Non-text Content, WCAG 2.4.6 success criterion Headings and Labels and the WCAG 4.1.2 success criterion Name, Role, Value are not met;
2. There are input fields without labels; therefore, the WCAG 1.1.1 success criterion Non-text Content, WCAG 1.3.1 success criterion Info and Relationships and the WCAG 4.1.2 success criterion Name, Role, Value are not met;
3. In some places, magnification of the text is blocked and the application text does not resize uniformly; therefore, the WCAG 1.4.4 success criterion Resize text is not met;
4. In some places, magnification of the text causes overlap with neighbouring content; therefore, the WCAG 1.4.4 success criterion Resize text is not met;
5. Some elements that can be activated by touch cannot be operated using a keyboard connected to the touchscreen device (e.g. the buttons to access the application via Apple, Facebook and Google, the 'Birthday' input field during creation or modification of a user profile, some controls to set weight and height and some controls in the main screen of the application); therefore, the WCAG 2.1.1 success criterion Keyboard is not met;
6. Some elements that can be activated by touch do not receive the keyboard focus; therefore, the WCAG success criterion 2.4.3 Focus Order is not met;
7. The keyboard focus is not always visible; therefore, the WCAG success criterion 2.4.7 Focus Visible is not met;
8. The semantics and function of some elements are not correctly conveyed to Assistive Technologies; therefore, the WCAG success criterion 1.3.1 Info and Relationships and the WCAG success criterion 4.1.2 Name, Role, Value are not met.
1.1.3 Drafting the Accessibility Statement
This statement was drawn up on 4 November 2022.
The information in the statement is derived from an assessment carried out by third parties.
The statement was most recently reviewed on 28 August 2024.
The statement was updated using an evaluation compliant with the requirements of Directive (EU) 2016/2012 through an assessment carried out by the third-party LIA Foundation.
1.1.4 How to send suggestions and contact details of the provider
The process we have launched is very important to us and feedback from our users is essential: if you encounter any problems or have any advice or suggestions while using our websites, please contact us at axconnected@wearablessupport.com
1.1.5 How to send reports to AgID
If the response receives is unsatisfactory or if none is provided to a suggestion or request within thirty days, the interested party can submit a report using the method indicated on the AgID company website.
1.2 Section 2
1.2.1 Information requested by AGI
Information on the mobile application
· Date of publication of the mobile application: 2017
· Usability tests conducted?: NO
· Mobile application is prepared for the following operating systems: iOS
Information on the structure
· Number of employees with disabilities hired by the provider: 96
· Number of workstations for employees with disabilities: 96
2 Accessibility Statement - Armani Exchange Connected Android
2.1 Section 1
The Armani Group undertakes to make its mobile application accessible, in accordance with Italian Law no. 4 of 9 January 2004.
Content in compliance with EU Implementing Decision 2018/1523.
This accessibility statement applies to the Armani Exchange Connected mobile application 5.1.8.
2.1.1 Compliance status
Partially compliant
This mobile application is partially compliant with the requirements of Appendix A of the UNI EN 301549:2018 standard (WCAG 2.1) and the requirements pursuant to annex A of the Italian Ministerial Decree of 5 July 2005 (WCAG 2.0) due to the cases of non-compliance listed below.
2.1.2 Inaccessible content
The contents listed below are not accessible for the following reasons:
· non-compliance with Italian Law no. 4 of 9 January 2004
1. There are buttons without labels; therefore, the WCAG 1.1.1 success criterion Non-text Content, WCAG 2.4.6 success criterion Headings and Labels and the WCAG 4.1.2 success criterion Name, Role, Value are not met;
2. The application only supports vertical screen orientation; therefore, the WCAG 1.3.4 success criterion Orientation is not met;
3. In some places, the contrast between the text contained within the buttons and the background is inadequate, so reading could be difficult; therefore, the WCAG 1.4.3 success criterion Contrast (Minimum) has not been met;
4. In some places, magnification of the text causes overlap with neighbouring content; therefore, the WCAG 1.4.4 success criterion Resize text is not met;
5. Some elements that can be activated by touch cannot be operated using a keyboard connected to the touchscreen device (e.g. the buttons to access the application via Facebook and Google, the 'Birthday' input field during creation of a user profile, some controls to set weight and height and some controls in the main screen of the application); therefore, the WCAG 2.1.1 success criterion Keyboard is not met;
6. Some elements that can be activated by touch do not receive the keyboard focus; therefore, the WCAG success criterion 2.4.3 Focus Order is not met;
7. The keyboard focus is not always visible; therefore, it fails the WCAG success criterion 2.4.7 Focus Visible;
8. The semantics and function of some elements are not correctly conveyed to Assistive Technologies; therefore, the WCAG success criterion 1.3.1 Info and Relationships and the WCAG success criterion 4.1.2 Name, Role, Value are not met;
9. The size of some buttons does not meet the minimum requirements of the guidelines for the accessibility of mobile applications.
2.1.3 Drafting the Accessibility Statement
This statement was drawn up on 4 November 2022.
The information in the statement is derived from an assessment carried out by third parties.
The statement was most recently reviewed on 28 August 2024.
The statement was updated using an evaluation compliant with the requirements of Directive (EU) 2016/2012 through an assessment carried out by the third-party LIA Foundation.
2.1.4 How to send suggestions and contact details of the provider
The process we have launched is very important to us and feedback from our users is essential: if you encounter any problems or have any advice or suggestions while using our websites, please contact us at axconnected@wearablessupport.com
2.1.5 How to send reports to AgID
If the response receives is unsatisfactory or if none is provided to a suggestion or request within thirty days, the interested party can submit a report using the method indicated on the AgID company website.
2.2 Section 2
2.2.1 Information requested by AGI
Information on the mobile application
· Date of publication of the mobile application: 2017
· Usability tests conducted?: NO
· The mobile application is prepared for the following operating systems: Android
Information on the structure
· Number of employees with disabilities hired by the provider: 96
· Number of workstations for employees with disabilities: 96
3 Accessibility Statement - Emporio Armani Connected iOS
3.1 Section 1
The Armani Group undertakes to make its mobile application accessible, in accordance with Italian Law no. 4 of 9 January 2004.
Content in compliance with EU Implementing Decision 2018/1523.
The following accessibility statement applies to the Emporio Armani Connected mobile application 5.1.8.
3.1.1 Compliance status
Partially compliant
This mobile application is partially compliant with the requirements of Appendix A of the UNI EN 301549:2018 standard (WCAG 2.1) and the requirements pursuant to annex A of the Italian Ministerial Decree of 5 July 2005 (WCAG 2.0) due to the cases of non-compliance listed below.
3.1.2 Inaccessible content
The contents listed below are not accessible for the following reasons:
· non-compliance with Italian Law no. 4 of 9 January 2004.
1. There are buttons without labels; therefore, the WCAG 1.1.1 success criterion Non-text Content, WCAG 2.4.6 success criterion Headings and Labels and the WCAG 4.1.2 success criterion Name, Role, Value are not met;
2. There are input fields without labels; therefore, the WCAG 1.1.1 success criterion Non-text Content, WCAG 1.3.1 success criterion Info and Relationships and the WCAG 4.1.2 success criterion Name, Role, Value are not met;
3. In some places, magnification of the text is blocked and the application text does not resize uniformly; therefore, the WCAG 1.4.4 success criterion Resize text is not met;
4. In some places, magnification of the text causes overlap with neighbouring content; therefore, the WCAG 1.4.4 success criterion Resize text is not met;
5. Some elements that can be activated by touch cannot be operated using a keyboard connected to the touchscreen device (e.g. the buttons to access the application via Apple, Facebook and Google, the 'Birthday' input field during creation or modification of a user profile, some controls to set weight and height and some controls in the main screen of the application); therefore, the WCAG 2.1.1 success criterion Keyboard is not met;
6. Some elements that can be activated by touch do not receive the keyboard focus; therefore, the WCAG success criterion 2.4.3 Focus Order is not met;
7. The keyboard focus is not always visible; therefore, the WCAG success criterion 2.4.7 Focus Visible is not met;
8. The semantics and function of some elements are not correctly conveyed to Assistive Technologies; therefore, the WCAG success criterion 1.3.1 Info and Relationships and the WCAG success criterion 4.1.2 Name, Role, Value are not met.
3.1.3 Drafting the Accessibility Statement
This statement was drawn up on 4 November 2022.
The information in the statement is derived from an assessment carried out by third parties.
The statement was most recently reviewed on 28 August 2024.
The statement was updated using an evaluation compliant with the requirements of Directive (EU) 2016/2012 through an assessment carried out by the third-party LIA Foundation.
3.1.4 How to send suggestions and contact details of the provider
The process we have launched is very important to us and feedback from our users is essential: if you encounter any problems or have any advice or suggestions while using our websites, please contact us at emporioarmaniconnected@wearablessupport.com.
3.1.5 How to send reports to AgID
If the response receives is unsatisfactory or if none is provided to a suggestion or request within thirty days, the interested party can submit a report using the method indicated on the AgID company website.
3.2 Section 2
3.2.1 Information requested by AGI
Information on the mobile application
· Date of publication of the mobile application: 2016
· Usability tests conducted?: NO
· Mobile application is prepared for the following operating systems: iOS
Information on the structure
· Number of employees with disabilities hired by the provider: 96
· Number of workstations for employees with disabilities: 96
4 Accessibility Statement - Emporio Armani Connected Android
4.1 Section 1
The Armani Group undertakes to make its mobile application accessible, in accordance with Italian Law no. 4 of 9 January 2004.
Content in compliance with EU Implementing Decision 2018/1523.
The following accessibility statement applies to the Emporio Armani Connected mobile application 5.1.8.
4.1.1 Compliance status
Partially compliant
This mobile application is partially compliant with the requirements of Appendix A of the UNI EN 301549:2018 standard (WCAG 2.1) and the requirements pursuant to annex A of the Italian Ministerial Decree of 5 July 2005 (WCAG 2.0) due to the cases of non-compliance listed below.
4.1.2 Inaccessible content
The contents listed below are not accessible for the following reasons:
· non-compliance with Italian Law no. 4 of 9 January 2004.
1. There are buttons without labels; therefore, the WCAG 1.1.1 success criterion Non-text Content, WCAG 2.4.6 success criterion Headings and Labels and the WCAG 4.1.2 success criterion Name, Role, Value are not met;
2. The application only supports vertical screen orientation; therefore, the WCAG 1.3.4 success criterion Orientation is not met;
3. In some places, the contrast between the text contained within the buttons and the background is inadequate, so reading could be difficult; therefore, the WCAG 1.4.3 success criterion Contrast (Minimum) has not been met;
4. In some places, magnification of the text causes overlap with neighbouring content; therefore, the WCAG 1.4.4 success criterion Resize text is not met;
5. Some elements that can be activated by touch cannot be operated using a keyboard connected to the touchscreen device (e.g. the buttons to access the application via Facebook and Google, the 'Birthday' input field during creation of a user profile, some controls to set weight and height and some controls in the main screen of the application); therefore, the WCAG 2.1.1 success criterion Keyboard is not met;
6. Some elements that can be activated by touch do not receive the keyboard focus; therefore, the WCAG success criterion 2.4.3 Focus Order is not met;
7. The keyboard focus is not always visible; therefore, the WCAG success criterion 2.4.7 Focus Visible is not met;
8. The semantics and function of some elements are not correctly conveyed to Assistive Technologies; therefore, the WCAG success criterion 1.3.1 Info and Relationships and the WCAG success criterion 4.1.2 Name, role, Value are not met;
9. The size of some buttons does not meet the minimum requirements of the guidelines for the accessibility of mobile applications.
4.1.3 Drafting the Accessibility Statement
This statement was drawn up on 2 November 2022.
The information in the statement is derived from an assessment carried out by third parties.
The statement was most recently reviewed on 28 August 2024.
The statement was updated using an evaluation compliant with the requirements of Directive (EU) 2016/2012 through an assessment carried out by the third-party LIA Foundation.
4.1.4 How to send suggestions and contact details of the provider
The process we have launched is very important to us and feedback from our users is essential: if you encounter any problems or have any advice or suggestions while using our websites, please contact us at emporioarmaniconnected@wearablessupport.com.
4.1.5 How to send reports to AgID
If the response receives is unsatisfactory or if none is provided to a suggestion or request within thirty days, the interested party can submit a report using the method indicated on the AgID company website.
4.2 Section 2
4.2.1 Information requested by AGI
Information on the mobile application
· Date of publication of the mobile application: 2016
· Usability tests conducted?: NO
· The mobile application is prepared for the following operating systems: Android
Information on the structure
· Number of employees with disabilities hired by the provider: 96
· Number of workstations for employees with disabilities: 96
5 Accessibility Statement - Nobu Milano - iOS App
5.1 Section 1
The Armani Group undertakes to make its mobile application accessible, in accordance with Italian Law no. 4 of 9 January 2004.
Content in compliance with EU Implementing Decision 2018/1523.
This accessibility statement applies to the Nobu Milano 3.0.0+ mobile application (iOS)
5.1.1 Compliance status
Partially compliant
This mobile application is partially compliant with the requirements of Appendix A of the UNI EN 301549:2018 standard (WCAG 2.1) and the requirements pursuant to annex A of the Italian Ministerial Decree of 5 July 2005 (WCAG 2.0) due to the cases of non-compliance listed below.
5.1.2 Inaccessible content
The contents listed below are not accessible for the following reasons:
· non-compliance with Italian Law no. 4 of 9 January 2004
1. There are buttons without labels; therefore, the WCAG 1.1.1 success criterion Non-text Content, WCAG 2.4.6 success criterion Headings and Labels and the WCAG 4.1.2 success criterion Name, Role, Value are not met;
2. In some cases, the semantics and function of some elements are not correctly conveyed to Assistive Technologies; therefore, the WCAG success criterion 1.3.1 Info and Relationships and the WCAG success criterion 4.1.2 Name, Role, Value are not met;
3. In some cases, the elements are not read in the right order; therefore, the WCAG success criterion 1.3.2 Meaningful Sequence is not met;
4. In some places, the contrast between the text and the background is inadequate, so reading could be difficult; therefore, the WCAG 1.4.3 success criterion Contrast (Minimum) has not been met;
5. In some places, the magnification of the text is not supported correctly, as increasing the size of the text may cause overlap with the neighbouring content, or information may be lost because the content is no longer readable; therefore, the WCAG 1.4.4 success criterion Resize Text is not met;
6. The elements that can be activated by touch cannot be operated using a keyboard connected to the touchscreen device; therefore, the WCAG 2.1.1 success criterion Keyboard is not met;
7. The size of some buttons does not meet the minimum requirements of the accessibility guidelines; therefore, the WCAG success criterion 2.5.8 Target Size (Minimum) is not met.
8. In some cases, errors connected with the completion of forms are not identified in text form; therefore, the WCAG success criterion 3.3.1 Error Identification is not met;
9. Some status messages are not conveyed correctly to Assistive Technologies; therefore, the WCAG 4.1.3 success criterion Status Messages is not met;
5.1.3 Drafting the Accessibility Statement
This statement was drawn up on 12 February 2025.
The statement was drafted using an evaluation compliant with the requirements of Directive (EU) 2016/2012 through an assessment carried out by the third-party LIA Foundation.
The information in the statement is derived from an automated assessment.
5.1.4 How to send suggestions and contact details of the provider
The process we have launched is very important to us and feedback from our users is essential: if you encounter any problems or have any advice or suggestions while using our websites, please contact us at deliveryb59@giorgioarmani.it.
5.1.5 How to send reports to AgID
If the response receives is unsatisfactory or if none is provided to a suggestion or request within thirty days, the interested party can submit a report using the method indicated on the AgID company website.
5.2 Section 2
5.2.1 Information requested by AGI
Information on the mobile application
· Date of publication of the mobile application: 25/02/25
· Usability tests conducted?: NO
· Mobile application is prepared for the following operating systems: iOS
Information on the structure
· Number of employees with disabilities hired by the provider: 96
· Number of workstations for employees with disabilities: 96
6 Accessibility Statement - Nobu Milano - Android App
6.1 Section 1
The Armani Group undertakes to make its mobile application accessible, in accordance with Italian Law no. 4 of 9 January 2004.
Content in compliance with EU Implementing Decision 2018/1523.
This accessibility statement applies to the Nobu Milano 2.0.2+ mobile application (Android)
6.1.1 Compliance status
Partially compliant
This mobile application is partially compliant with the requirements of Appendix A of the UNI EN 301549:2018 standard (WCAG 2.1) and the requirements pursuant to annex A of the Italian Ministerial Decree of 5 July 2005 (WCAG 2.0) due to the cases of non-compliance listed below.
6.1.2 Inaccessible content
The contents listed below are not accessible for the following reasons:
· non-compliance with Italian Law no. 4 of 9 January 2004
1. There are buttons without labels; therefore, the WCAG 1.1.1 success criterion Non-text Content, WCAG 2.4.6 success criterion Headings and Labels and the WCAG 4.1.2 success criterion Name, Role, Value are not met;
2. In some cases, the semantics and function of some elements are not correctly conveyed to Assistive Technologies; therefore, the WCAG success criterion 1.3.1 Info and Relationships and the WCAG success criterion 4.1.2 Name, Role, Value are not met;
3. In some cases, the elements are not read in the right order; therefore, the WCAG success criterion 1.3.2 Meaningful Sequence is not met;
4. In some places, the contrast between the text and the background is inadequate, so reading could be difficult; therefore, the WCAG 1.4.3 success criterion Contrast (Minimum) has not been met;
5. In some places, the magnification of the text is not supported correctly, as increasing the size of the text may cause overlap with the neighbouring content, or information may be lost because the content is no longer readable; therefore, the WCAG 1.4.4 success criterion Resize Text is not met;
6. The elements that can be activated by touch cannot be operated using a keyboard connected to the touchscreen device; therefore, the WCAG 2.1.1 success criterion Keyboard is not met;
7. The size of some buttons does not meet the minimum requirements of the accessibility guidelines; therefore, the WCAG success criterion 2.5.8 Target Size (Minimum) is not met.
8. In some cases, errors connected with the completion of forms are not identified in text form; therefore, the WCAG success criterion 3.3.1 Error Identification is not met;
9. Some status messages are not conveyed correctly to Assistive Technologies; therefore, the WCAG 4.1.3 success criterion Status Messages is not met;
6.1.3 Drafting the Accessibility Statement
This statement was drawn up on 12 February 2025.
The statement was drafted using an evaluation compliant with the requirements of Directive (EU) 2016/2012 through an assessment carried out by the third-party LIA Foundation.
The information in the statement is derived from an automated assessment.
6.1.4 How to send suggestions and contact details of the provider
The process we have launched is very important to us and feedback from our users is essential: if you encounter any problems or have any advice or suggestions while using our websites, please contact us at deliveryb59@giorgioarmani.it.
6.1.5 How to send reports to AgID
If the response receives is unsatisfactory or if none is provided to a suggestion or request within thirty days, the interested party can submit a report using the method indicated on the AgID company website.
6.2 Section 2
6.2.1 Information requested by AGI
Information on the mobile application
· Date of publication of the mobile application: 25/02/25
· Usability tests conducted?: NO
· The mobile application is prepared for the following operating systems: Android
Information on the structure
· Number of employees with disabilities hired by the provider: 96
· Number of workstations for employees with disabilities: 96