Accessibility Statement

Last updated: October 10, 2025

This document was provided by AccessiWay to comply with the European Accessibility Act obligations until the competent National Authority provides the official template.

Each complex paragraph is introduced by a plain‑language explanation.

Introduction

We want everyone, including people with disabilities, to use our service easily. This document explains what we do to make it accessible and compliant with laws and standards such as the European Accessibility Act and the WCAG.

Scarpa is committed to accessibility and inclusivity. We want all our customers, including people with disabilities, to successfully use our service.

This document describes the accessibility features of https://scarpa.com, how we meet the requirements of the European Accessibility Act, EN 301 549, WCAG 2.2, the ADA and Section 508, and what we are doing to maintain and improve accessibility. This statement covers only https://scarpa.com

We review this information regularly as we improve https://scarpa.com

Overview

Service description

The site provides an online retail service, allowing users to browse the catalog, manage the shopping cart, and complete purchases via the e‑commerce platform.

How to use https://scarpa.com (Accessibility & Operability)

We strive to make https://scarpa.com simple for everyone. Here is an overview of how to navigate and use our service when assistive technologies or special configurations are used:

The service is accessible via a web interface from the main menu, which lets users navigate among product categories. Users can open product pages, add items to the cart, and complete the purchase through the guided checkout.
Customer support is available through the Contacts section of the site.

Accessibility of https://scarpa.com

The site uses the standard modes of interaction provided by the operating system and assistive technologies.

If you need additional explanations on using any part of https://scarpa.com, please contact our support team for personalized assistance. We aim to provide any further descriptions or explanations necessary for the correct use of the service.

 

Accessibility conformance  (How we meet the requirements)

We evaluated https://scarpa.com against the requirements of the European Accessibility Act (and any applicable local implementation), the ADA, WCAG 2.2, and Section 508, and it is:

Perceivable

• No pre‑recorded video lacks captions.

• No synchronized media that requires it lacks descriptions or alternative versions.

• No video that requires it lacks audio description.

• Content is presented in an order that reflects logical and semantic structure, enabling assistive technologies to interpret it correctly.

• Instructions for understanding and operating content do not rely solely on sensory characteristics such as shape, color, size, visual location, orientation, or sound.

• Content adapts correctly to screen orientation, maintaining consistent display and operation.

• Where present, the purpose of input fields that accept specific data is correctly conveyed to assistive technologies and implemented accordingly.

• Content is adaptable, allowing users to customize text size while maintaining a fully usable interface.

• Content that does not require a two‑dimensional layout reflows correctly when the user agent’s viewport changes.

• Adjusting text spacing (line height, paragraph spacing, letter or word spacing) does not cause loss of content or functionality.

Operable

• No keyboard traps are present (it is possible to navigate freely into and out of all components).

• There is no interference with single‑character keyboard shortcuts (letters, numbers, or symbols).

• No time limits are imposed by content, or if present they are user‑controllable, adjustable, extendable, or justified by functional or regulatory needs.

• All moving content, if present, includes controls to pause and/or control playback.

• No flashing or blinking content at levels that could trigger seizures; content remains within safety limits.

• Skip links are implemented to allow quick navigation to the main content, improving accessibility and UX.

• Pages within the service flow have titles that describe their topic or purpose.

• In sequences where navigation order affects meaning or operation, focusable objects receive focus in an order that preserves meaning and operability.

• The purpose of links can be determined from the link text itself or from its context with adjacent content.

• Multiple ways exist to locate content within the environment.

• Headings and labels clarify content and functionality.

• The keyboard focus indicator is visible on all interactive elements.

• Elements that can receive keyboard focus are always at least partially visible within the viewport.

• No complex gestures are required to use any functionality.

• Functionalities do not trigger immediately on touch; they can be canceled before completion and do not require press‑and‑hold to operate.

• For UI components with labels that include text or images of text, the accessible name includes the text presented visually.

• All features are usable without relying solely on device or user motion.

• All features are usable without requiring drag gestures.

• Click/touch targets are sufficiently large to ensure comfortable interaction.

Understandable

• The language of each page is correctly defined and used consistently throughout the service.

• All language parts that require it can be determined programmatically.

• When keyboard focus moves to UI components, no unexpected context changes occur that could disorient the user.

• When UI components are activated via keyboard or assistive technologies, no unexpected context changes occur that could disorient the user.

• Navigation mechanisms are placed consistently throughout the service flow.

• Repeated interface elements are defined consistently to make them easy to identify.

• Within the environment, help/support request mechanisms are consistent.

• When an input error is automatically detected, the error is identified and described with text.

• When an input error is identified and suggestions are known, those suggestions are provided unless prohibited by regulations.

• Mechanisms are in place to prevent errors, such as confirmation, undo, or reversibility for sensitive actions.

• Where possible, users are not asked to provide the same data more than once.

• When present, complex authentication systems have accessible alternatives.

• We write content in clear and simple language.

Robust

• We use standard development technologies that can be interpreted by assistive technologies.

We have tested https://scarpa.com with common assistive technologies across a wide range of OS–browser configurations:

• Screen readers (such as NVDA and JAWS on Windows, VoiceOver on Mac and iOS) to confirm that all interactive elements are announced correctly and are operable.

• We also test screen magnification and high‑contrast modes.

We aim for compatibility with current versions of major assistive technologies. Our code follows best practices outlined in WCAG 2.2 and EN 301 549 for robust implementation, which means it should remain accessible as technology evolves.

Standards. Based on the above, we apply the latest WCAG 2.2 AA and EN 301 549 criteria to ensure accessibility. Compliance with these standards creates a presumption of conformity with EAA, ADA, and other regulations based on the same technical standards.

 

Continuous monitoring and maintenance

Accessibility is not a one‑time effort, but an ongoing process. Here is how we ensure https://scarpa.com remains accessible over time:

• Our accessibility coordinator, who oversees the accessibility of https://scarpa.com, can be reached at accessibility@scarpa.net

• With AccessiWay’s support, on October 10, 2025 we conducted an external expert‑led manual audit to verify our accessibility compliance. We maintain a cycle of continuous testing and improvements, with recurring support to ensure comprehensive audits— including manual testing by professionals using assistive technologies—at least once a year.

• We use automated testing tools integrated into our development process to promptly identify common accessibility issues (such as missing alt text or form labeling). Each code update passes through these checks.

 

Feedback and contacts

We welcome your suggestions to make https://scarpa.com better. If you find issues or have suggestions, contact us by email, phone, or mail. Please explain the problem in detail so we can assist you.

We value user feedback, especially when you tell us something isn’t working. If you have difficulty accessing any part of https://scarpa.com encounter an accessibility issue, or have suggestions for improvement, please let us know.

Email: accessibility@scarpa.net

Company address: Calzaturificio SCARPA — Viale Enrico Fermi 1, 31011 Asolo (TV), Italy

When you contact us, please include as many details as possible (which page or feature, what happened, and which assistive technology you used, if any). We will strive to acknowledge your feedback within 15 business days and will do our best to resolve the issue quickly or keep you informed of progress.

Enforcement. If you believe your accessibility concerns have not been properly addressed, you have the right to escalate your complaint. We sincerely hope to resolve any issues with you before it reaches that stage.

Document history. This document was last reviewed and updated on October 10, 2025. We plan to review it at least annually, or whenever significant changes to the service occur.

 

EN 301 549 — Technical report

Chapter 5: General requirements

Criteria → Conformance level(s) → Notes

• 5.1 Closed functionality → Header cell — no response required → Header cell — no response required

• 5.1.2 General → Header cell — no response required → Header cell — no response required

• 5.1.2.1 Closed functionality → See 5.2 to 13 → See information in 5.2 to 13

• 5.1.2.2 Assistive technology → See 5.1.3 to 5.1.6 → See information in 5.1.3 to 5.1.6

5.1.3 Non‑visual access
All subclauses below are Not applicable:
5.1.3.1 Audio output of visual information; 5.1.3.2 Playback of audio output including speech; 5.1.3.3 Correlation of audio output; 5.1.3.4 User control of speech output; 5.1.3.5 Automatic interruption of speech output; 5.1.3.6 Speech output for non‑text content; 5.1.3.7 Speech output for video information; 5.1.3.8 Masked input; 5.1.3.9 Private access to personal data; 5.1.3.10 Interference‑free audio output; 5.1.3.11 Private listening volume; 5.1.3.12 Speaker volume; 5.1.3.13 Volume reset; 5.1.3.14 Spoken languages; 5.1.3.15 Non‑visual error identification; 5.1.3.16 Receipts, tickets, transactional results.

• 5.1.4 Closed functionality for text magnification → Not applicable

• 5.1.5 Visual output for audio information → Not applicable

5.1.6 Operation without keyboard interface

• 5.1.6.1 Closed functionality → See 5.1.3.1 to 5.1.3.16 → See information in 5.1.3.1 to 5.1.3.16

• 5.1.6.2 Input focus → Not applicable

• 5.1.7 Speech‑free access → Not applicable

• 5.2 Enabling accessibility features → Not applicable

• 5.3 Biometrics → Not applicable

• 5.4 Preservation of accessibility information during conversion → Not applicable

5.5 Usable parts

• 5.5.1 Modes of operation → Not applicable

• 5.5.2 Discernibility of usable parts → Not applicable

5.6 Locking or toggling controls

• 5.6.1 Tactile or auditory state → Not applicable

• 5.6.2 Visual state → Not applicable

• 5.7 Key repeat → Not applicable

• 5.8 Double‑stroke acceptance → Not applicable

• 5.9 Simultaneous user actions → Not applicable

 

Chapter 6: ICT with two‑way voice communication

All listed criteria are Not applicable, including:
6.1 Audio bandwidth for speech; 6.2 Real‑Time Text (RTT) features (6.2.1.1 RTT communication; 6.2.1.2 Concurrent voice and text; 6.2.2.1 Visually distinguishable display; 6.2.2.2 Programmatically determinable send/receive direction; 6.2.2.3 Speaker identification; 6.2.2.4 Visual indicator of audio with RTT; 6.2.3 Interoperability; 6.2.4 RTT responsiveness); 6.3 Caller identification; 6.4 Alternatives to voice‑based services.

6.5 Video communications

• 6.5.1 General (informative) → Header cell — no response required
  All other subclauses (6.5.2–6.5.6) → Not applicable

6.6 Alternatives to video‑based services (informative) → Advisory — no response required

 

Chapter 7: ICT with video functionality

7.1 Caption processing technology

• 7.1.1 Caption playback → Not applicable

• 7.1.2 Caption synchronization → Not applicable

• 7.1.3 Caption preservation → Not applicable

• 7.1.4 Caption features → Not applicable

• 7.1.5 Spoken captions → Not applicable

7.2 Audio description technology

• 7.2.1 Audio description playback → Not applicable

• 7.2.2 Audio description synchronization → Not applicable

• 7.2.3 Audio description preservation → Not applicable

7.3 User controls for captions and audio description → Not applicable

 

Chapter 8: Hardware

All listed criteria are Not applicable, including:
8.1.2 Standard connections; 8.1.3 Color; 8.2 Voice‑output hardware (8.2.1.1 Voice volume range; 8.2.1.2 Incremental volume control; 8.2.2.1 Fixed‑line devices; 8.2.2.2 Wireless communication systems); 8.3 Fixed ICT (all approach/clearance/visibility/installation subclauses); 8.4 Mechanically operable parts (numeric keys, methods and force of operation, keys/tickets/fare cards); 8.5 Tactile indication of voice mode.

 

Chapter 9: Web (applies also to 10, 11, and 12)

Corresponding to WCAG 2.2 Level A

Corresponding to WCAG 2.2 Level AA

 

Chapter 10: Non‑web documents

• 10.0 General (informative) → Header cell — no response required

• 10.1.1.1 to 10.4.1.3 → See WCAG 2.2 section → See information in WCAG 2.2 section

• 10.5 Caption placement → Not applicable

• 10.6 Audio description timing → Not applicable

 

Chapter 11: Software

• 11.0 General (informative) → Header cell — no response required

• 11.1.1.1 to 11.4.1.3 → See WCAG 2.2 section → See information in WCAG 2.2 section

11.5 Interoperability with assistive technology

• 11.5.1 Closed functionality → Header cell — no response required

• 11.5.2 Accessibility services → Header cell — no response required

• 11.5.2.1–11.5.2.3 → See 11.5.2.5 to 11.5.2.17 → See information in 11.5.2.5 to 11.5.2.17

Subclauses Not applicable:
11.5.2.4 Assistive technology; 11.5.2.5 Object information; 11.5.2.6 Row, column, and headers; 11.5.2.7 Values; 11.5.2.8 Label relationships; 11.5.2.9 Parent–child relationships; 11.5.2.10 Text; 11.5.2.11 List of available actions; 11.5.2.12 Execution of available actions; 11.5.2.13 Tracking focus and selection attributes; 11.5.2.14 Modifying focus and selection attributes; 11.5.2.15 Notification of changes; 11.5.2.16 Changes of states and properties; 11.5.2.17 Changes of values and text.

11.6 Documentation of accessibility usage

• 11.6.1 User control of accessibility features → Not applicable

• 11.6.2 No disruption of accessibility features → Not applicable

11.7 User preferences → Not applicable

11.8 Authoring tools

• 11.8.1 Content technology → Header cell — no response required

• 11.8.2 Creation of accessible content → See WCAG 2.2 section (If the software is not an authoring tool, indicate “Not applicable”) → See information in WCAG 2.2 section

• 11.8.3 Preservation of accessibility information in transformations → Not applicable

• 11.8.4 Repair suggestions → Not applicable

• 11.8.5 Templates → Not applicable

 

Chapter 12: Documentation and support services

12.1 Product documentation → Header cell — no response required

• 12.1.1 Accessibility features and compatibility → Not applicable

• 12.1.2 Accessible documentation → See WCAG 2.2 section → See information in WCAG 2.2 section

12.2 Support services → Header cell — no response required

• 12.2.2 Information on accessibility features and compatibility → Not applicable

• 12.2.3 Effective communication → Not applicable

• 12.2.4 Accessible documentation → See WCAG 2.2 section → See information in WCAG 2.2 section

 

 

Chapter 13: ICT that provides relay or access to emergency services

13.1 Relay service requirements → Header cell — no response required

• 13.1.2 Text relay services → Not applicable

• 13.1.3 Sign relay services → Not applicable

• 13.1.4 Lip‑reading relay services → Not applicable

   

• 13.2 Access to relay services → Not applicable

• 13.3 Access to emergency services → Not applicable