Accessibility Statement of Website and mobile application for entities covered by Art. 3, paragraph 1-bis of Italian Law 9 January 2004, No. 4

Oro Caffè is committed to making its website accessible, in compliance with Italian Law 9 January 2004, No. 4 (“Legge Stanca”), published in the Official Gazette No. 13 of 17/01/2004, and with Legislative Decree 10 August 2018, No. 106, which transposes EU Directive 2016/2102 of the European Parliament and of the Council.

This accessibility statement applies to the domain: shoporocaffe.com

Compliance status

Partially compliant in accordance with the UNI CEI EN 301549:2022 standard.

This website is partially compliant with the requirements set out in Appendix A of the UNI CEI EN 301549:2022 standard due to the non-conformities listed below and described in detail in the related evaluation model held by the provider.

Non-accessible content

Some content is not accessible due to partial or incomplete compliance with Appendix A of the UNI CEI EN 301549:2022 standard:

  • 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.3.1 – Info and Relationships – WCAG 1.3.1 Level A: In some cases, information, structure, or relationships conveyed through presentation cannot be programmatically determined or are not available in text.
  • C.9.1.3.5 – Identify Input Purpose – WCAG 1.3.5 Level AA: the purpose of some user input fields cannot be programmatically determined.
  • C.9.1.4.1 – Use of Color – WCAG 1.4.1 Level A: in some cases, color is used as the only visual means of conveying information, indicating actions, prompting a response, or distinguishing a visual element.
  • C.9.1.4.3 – Contrast (Minimum) – WCAG 1.4.3 Level AA: in some cases, the visual presentation of text and images containing text has a contrast ratio lower than 4.5:1, except where permitted by the standard.
  • C.9.1.4.10 – Reflow – WCAG 1.4.10 Level AA: in some cases, content requires two-dimensional scrolling, causing loss of information or functionality on devices with a width of 320 px and height of 256 px.
  • C.9.2.1.2 – No Keyboard Trap – WCAG 2.1.2 Level A: some components receiving keyboard focus do not allow consistent keyboard input or exit from the component.
  • C.9.2.4.3 – Focus Order – WCAG 2.4.3 Level A: on some pages, the order in which objects receive focus does not preserve the meaning and operability of the page.
  • 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 from the link text alone or from the link text together with its surrounding context.
  • C.9.2.4.6 – Headings and Labels – WCAG 2.4.6 Level AA: in some interface components, headings and labels describing topics or purpose are missing.
  • C.9.2.5.3 – Label in Name – WCAG 2.5.3 Level A: in some cases, the name of interface components with labels that include text or images of text does not contain the visually presented text.
  • C.9.3.2.2 – On Input – WCAG 3.2.2 Level A: in some cases, changing the setting of a user interface component causes a context change without informing the user.
  • C.9.3.3.2 – Labels or Instructions – WCAG 3.3.2 Level A: in some cases, labels or instructions are not provided when user input is required.
  • C.9.3.3.3 – Error Suggestions – WCAG 3.3.3 Level AA: in some cases, when an input error is detected and suggestions are known, the element in error is not identified and/or the suggestion 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 programmatically determined; states, properties and values set by the user are not programmatically determinable or notifications of state 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 programmatically determined via role or property without receiving focus.

Drafting of the statement

  • Date of drafting: 15/09/2025
  • Evaluation: carried out by third parties with UNI 11621-3 qualification (register number ECFPROFESSIONAL2025-000080), using both objective and subjective analyses (see Art. 3, paragraph 1 of EU Commission Implementing Decision 2018/1523).
  • Evaluation methodology: technical check and manual check.

Techniques used

  • Automatic and semi-automatic validators: tools promoted by the W3C (see W3C Evaluation Tools List).
  • Assistive technologies: NVDA, JAWS, ChromeVox, Magnifier, Gboard, Voice Access, TalkBack, Accessibility Scanner, Switch Access, VoiceOver, SpokenContent.
  • Manual inspection: manipulation of the Document Object Model (DOM) using DevTools, Web Developer toolbar, Lighthouse, Pagespeed, WebIAM, Siteimprove, A11y, AxeCore, Silktide inspector, AccessiWeb scanner/API, AgilityPack, AccessiWeb Webserver, tests with zoom, high contrast, “Emulate vision deficiencies,” checks of ARIA roles/attributes, markup semantics, and parsing.
  • Testing on multiple combinations: browsers, devices, resolutions, orientations and user agents, for a total of 117 control techniques (described in detail in the evaluation model held by the provider).

Reporting and contacts

  • To report non-compliance or request information or content excluded from the scope of the directive: email digital@orocaffe.com

.

.

Website information

  • Website publication date: 19/10/2022
  • Usability tests performed: Yes
  • CMS used: Shopify

Company information

  • Employees with disabilities: 0
  • Workstations for employees with disabilities: 0
  • Last update: 08/09/2025

The “Accessibility Statement Template for websites and mobile applications for entities covered by Art. 3, paragraph 1-bis of Italian Law 9 January 2004, No. 4” was created in accordance with the law “Provisions to promote and simplify user access, particularly for people with disabilities, to IT tools” (Law 9 January 2004, No. 4, “Legge Stanca”).

Source: AGID – Agency for Digital Italy

“Annex 1 to the Guidelines on the Accessibility of IT Tools”.