Legal area / Accessibility
1. Accessibility statement
The Armani Group is committed to making its websites accessible in accordance with Legislative Decree No. 106 of 10 August 2018, which transposed Directive (EU) 2016/2102 of the European Parliament and of the Council into Italian law. The accessibility statements for the Armani Group websites listed below are presented in alphabetical order by website name. As required by law, each website’s accessibility statement has been published in a dedicated section accessible from its homepage.
Website name | Web address | Date the statement was updated |
Armani.com (including the Giorgio Armani, Emporio Armani, EA7, Armani Exchange, Armani/Casa, Armani/Fiori, Armani Restaurants and Armani Clubs sections) | 16 September 2026 | |
Armani/Archivio | 14 September 2026 | |
Armani/Dolci | 7 September 2026 | |
Armani/Silos | 22 September 2026 | |
Armani/Values | 7 September 2026 |
1.1.1 How to Submit Feedback and Contact the Service Provider
The process we have begun is very important to us, and feedback from our users is essential. If you encounter any problems while using our websites, or have any comments or suggestions, you can contact us at the following link: www.armani.com/contactus.
1.1.2 How to Submit a Report to AgID
If the response to a notification or request is unsatisfactory, or if no response is received within thirty days, the person concerned may submit a report using the procedure indicated on the official website of AgID.
2. Armani.com accessibility statement
1.1.1 Accessibility Statement for Armani.com
The Armani Group is committed to making its website accessible in accordance with Law No. 4 of 9 January 2004. This accessibility statement applies to www.armani.com.
1.1.2 Compliance Status
Partially compliant – This website is partially compliant with the requirements set out in Annex A to standard EN 301 549 V3.2.1 (2021-03) and with the international Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, due to the instances of non-compliance listed below.
1.1.3 Inaccessible Content
The following content is inaccessible for the reasons given below:
a) Non-compliance with Law No. 4 of 9 January 2004:
1. Some images have alternative text that does not adequately describe their content or function to people with visual impairments who use screen readers, while alternative text is provided for other images that may be purely decorative. Consequently, WCAG Success Criterion 1.1.1 Non-text Content is not met;
2. On the “Store locator” page, some buttons have no accessible name. The button for selecting the user’s country and the button for closing the banner containing it also have no accessible name. This may make it difficult for users with visual impairments who navigate the page using a screen reader to understand the purpose and function of these buttons. Consequently, WCAG Success Criteria 1.1.1 Non-text Content, 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value are not met;
3. On some pages, multiple elements are incorrectly identified as modal dialogs. Consequently, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
4. On the “Store locator” page, some buttons have an aria-labelledby attribute that refers to elements that are not present on the page. Consequently, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
5. Some dialogs and sidebars have no accessible name. Consequently, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
6. On some pages, heading levels do not follow the correct hierarchy; some text that serves as a heading is not marked up with the correct semantics; or headings are missing. Consequently, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
7. On the “Store locator” page, some elements are hidden visually but remain exposed to screen readers used by people with visual impairments. This creates a discrepancy between the content displayed on screen and the content available to these users. Consequently, WCAG Success Criterion 1.3.2 Meaningful Sequence is not met;
8. On the “Store locator” page, the focus state of buttons marking store locations on the map is indicated only by a change in the buttons’ fill colour. Consequently, WCAG Success Criterion 1.4.1 Use of Color is not met;
9. In some places, the contrast between text and its background is insufficient, which may make the text difficult to read. Consequently, WCAG Success Criterion 1.4.3 Contrast (Minimum) is not met;
10. On some pages and in some sidebars, enlarging text to 200% may cause it to overlap adjacent content or become truncated or obscured. Consequently, WCAG Success Criterion 1.4.4 Resize Text is not met;
11. On some pages, content does not reflow optimally, and zooming the page to 400% may truncate product names in product cards and sidebar headings. The fixed positioning of some page elements may reduce the space available for the main content or obscure it entirely. Consequently, WCAG Success Criterion 1.4.10 Reflow is not met;
12. Some user interface components, such as buttons and links, have insufficient contrast against adjacent colours, which may make it difficult to identify and distinguish their interactive areas. Consequently, WCAG Success Criterion 1.4.11 Non-text Contrast is not met;
13. For some elements, the visual indicator that highlights the element receiving keyboard focus may have insufficient contrast against adjacent colours. Examples include the button for closing store-detail sidebars on the “Store locator” page and the buttons for displaying details of products shown in images. Consequently, WCAG Success Criterion 1.4.11 Non-text Contrast is not met;
14. Tabs in some sidebars, such as the “Size guide” sidebar on product pages, do not properly support navigation between tabs using the keyboard arrow keys. On some pages, certain elements are incorrectly identified as modal dialogs, giving assistive technologies misleading information about which elements can be operated with a keyboard. Consequently, WCAG Success Criterion 2.1.1 Keyboard is not met;
15. The “Store locator” page does not have a skip link that allows users to go directly to the main page content. Consequently, WCAG Success Criterion 2.4.1 Bypass Blocks is not met;
16. The title of the “Store locator” page is not descriptive. Consequently, WCAG Success Criterion 2.4.2 Page Titled is not met;
17. After sidebars, dialogs (such as the cookie management dialog), the search flyout and pop-ups (such as the pop-up confirming that a product has been added to or removed from the wishlist) are closed, keyboard focus returns to the beginning of the page. Although the search flyout obscures the underlying page content, it is not managed as a modal dialog, and focus can move to the obscured content. Some buttons that can receive keyboard focus are hidden from assistive technologies, which may announce them as empty elements. Consequently, WCAG Success Criterion 2.4.3 Focus Order is not met;
18. Some links may be ambiguous or meaningless in context, particularly when several links on the same page have the same label or accessible name. Consequently, WCAG Success Criterion 2.4.4 Link Purpose (In Context) is not met;
19. The mobile version of the homepage contains an empty link. Consequently, WCAG Success Criteria 2.4.4 Link Purpose (In Context) and 4.1.2 Name, Role, Value are not met;
20. Some buttons may be ambiguous or meaningless in context, particularly when several buttons on the same page have the same label or accessible name. Consequently, WCAG Success Criterion 2.4.6 Headings and Labels is not met;
21. The keyboard focus indicator is visible on all interactive elements except for some elements that are only visually hidden on the “Store locator” page, the filter checkboxes on the “Store locator” page, the image-carousel buttons in product cards, and selected tabs in some sidebars, such as the “Select size” sidebar on product pages. Consequently, WCAG Success Criterion 2.4.7 Focus Visible is not met;
22. On the “Store locator” page, the sidebars containing store details obscure the underlying page content, and there is no way to dismiss these elements without moving focus. As a result, the element receiving focus remains obscured. Consequently, WCAG Success Criterion 2.4.11 Focus Not Obscured (Minimum) is not met;
23. On some pages, the accessible name of interactive components (links and buttons) does not contain the label visible on screen. Consequently, WCAG Success Criterion 2.5.3 Label in Name is not met;
24. On some pages, words or passages in a language other than the page’s primary language are not identified as such. This may make it difficult for text-to-speech solutions to pronounce them correctly. Consequently, WCAG Success Criterion 3.1.2 Language of Parts is not met;
25. The semantics, function and behaviour of some elements are not conveyed properly to assistive technologies. In some cases, elements hidden from assistive technologies can still be reached using the keyboard. Consequently, WCAG Success Criterion 4.1.2 Name, Role, Value is not met;
26. Some buttons that can receive keyboard focus are hidden from assistive technologies, which may announce them as empty elements. Consequently, WCAG Success Criterion 4.1.2 Name, Role, Value is not met;
27. Some status messages reporting the outcome of an action and some error messages associated with form completion, for example in the registration form or when changing an email address, are not conveyed properly to assistive technologies. The same applies to certain warning messages, such as the warning displayed when the maximum number of identical products in the cart has been reached. Consequently, WCAG Success Criterion 4.1.3 Status Messages is not met;
A chat service is available on www.armani.com, providing users with assistance when searching for and purchasing products. This component has additional instances of non-compliance beyond those listed above, namely:
· Some elements are hidden visually but remain exposed to screen readers used by people with visual impairments. This creates a discrepancy between the content displayed on screen and the content available to these users. Consequently, WCAG Success Criterion 1.3.2 Meaningful Sequence is not met;
· Input fields containing errors are identified only by colour. Consequently, WCAG Success Criterion 1.4.1 Use of Color is not met;
· The level-one heading “Your chat” is an image of text. Consequently, WCAG Success Criterion 1.4.5 Images of Text is not met;
· The chat cannot be opened using the keyboard, which may make this feature very difficult for some users to use. Consequently, WCAG Success Criterion 2.1.1 Keyboard is not met;
· The language of the chat iframe is not specified. Consequently, WCAG Success Criterion 3.1.1 Language of Page is not met;
The Emporio Armani, EA7 and Armani Exchange section homepages include a virtual assistant that provides styling advice. This component also has specific instances of non-compliance, namely:
· The chat panel title is not marked up with the correct heading semantics. Consequently, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
· Enlarging text to 200% may cause fixed-position elements to obscure chat content or may cause text to be truncated, such as the names of suggested products in product cards. Consequently, WCAG Success Criterion 1.4.4 Resize Text is not met;
· Content does not reflow optimally. When the page is zoomed to 400%, the fixed positioning of some elements may reduce the space available to display chat content or obscure it entirely. Consequently, WCAG Success Criterion 1.4.10 Reflow is not met;
· The input field has insufficient contrast against adjacent colours, which may make it difficult to identify and distinguish its interactive area. Consequently, WCAG Success Criterion 1.4.11 Non-text Contrast is not met;
· The quality of the experience cannot be rated using the keyboard. Consequently, WCAG Success Criterion 2.1.1 Keyboard is not met;
· Keyboard focus does not move through the chat panel in a logical and predictable order. Focus returns to the beginning of the page after a user interaction or after the virtual assistant has generated its response. It also returns to the beginning of the page when the chat panel is closed using the designated button. When the “New chat” button is activated, a confirmation pop-up appears, but focus does not move into it automatically. Consequently, WCAG Success Criterion 2.4.3 Focus Order is not met;
· The chat panel is not managed as a modal dialog, so keyboard focus can move to the underlying page. There is no way to dismiss the panel without moving focus; as a result, the element receiving focus remains obscured. Consequently, WCAG Success Criterion 2.4.11 Focus Not Obscured (Minimum) is not met;
· The accessible names of some buttons in the chat panel are in a language other than the page’s primary language, and that language is not identified programmatically. Consequently, WCAG Success Criterion 3.1.2 Language of Parts is not met;
· The buttons for rating a suggestion from the virtual assistant positively or negatively are not implemented correctly. Consequently, WCAG Success Criterion 4.1.2 Name, Role, Value is not met;
· The status messages indicating that the virtual assistant is processing the user’s request, and the assistant’s responses, are not conveyed properly to assistive technologies. Consequently, WCAG Success Criterion 4.1.3 Status Messages is not met.
1.1.4 Preparation of the Accessibility Statement
This statement was prepared on 5 September 2025.
The statement was last reviewed on 16 September 2026 on the basis of an assessment carried out using automated and semi-automated tools by Fondazione LIA ETS, a third-party organisation.
1.1.5 How to Submit Feedback and Contact the Service Provider
The process we have begun is very important to us, and feedback from our users is essential. If you encounter any problems while using our websites, or have any comments or suggestions, you can contact us using the contact options available on the
Contact Us page of the Armani.com website.
1.1.6 How to Submit a Report to AgID
If the response to a notification or request is unsatisfactory, or if no response is received within thirty days, the person concerned may submit a report using the procedure indicated on the official AgID website.
1.1.7 Website Information
· Website publication date: 2024
· Usability tests conducted: No
· Content Management System (CMS) used for the website: proprietary software
1.1.8 Organisational Information
· Number of employees with disabilities employed by the service provider: 194
· Number of workstations for employees with disabilities: 194