Accessibility Statement
Last update: 23/06/2026
This document is drafted in a simplified form and in clear and understandable language in accordance with the principles and accessibility requirements established by Directive (EU) 2019/882 and Legislative Decree 27 May 2022, n. 82, with particular reference to the obligation to provide perceptible, usable, understandable and robust information for all users, including people with disabilities.
Pursuant to Article 12 of Legislative Decree 82/2022 and Annex I, sections III and IV, information relating to the accessibility of services must be presented clearly, understandably and accessibly, including through the use of simple language and a non-complex structure.
The choice of conciseness and simplicity of this document therefore constitutes a direct implementation of a regulatory obligation and does not represent a limitation of the available information, which remains fully governed by the technical and legal reference documentation.
This document has been provided by Accessiway to comply with the obligations of the European Accessibility Act until the competent National Authority provides the official template.
Every complex paragraph is introduced by an explanation in simpler language.
Introduction
We want everyone, including people with disabilities, to easily use our service. This document explains what we do to make it accessible and compliant with laws and standards such as the European Accessibility Act or WCAG.
CSP International Fashion Group is committed to accessibility and inclusivity. We want all our customers, including people with disabilities, to be able to successfully use our service.
This document illustrates the accessibility features of https://www.perofil.com, how we meet the requirements of the European Accessibility Act, EN 301549 standard, WCAG 2.2, ADA and Sec. 508, and what we are doing to maintain and improve accessibility. This statement only covers https://www.perofil.com.
We regularly review this information as we improve https://www.perofil.com.
Overview
Service description
This is a B2C e-commerce platform for purchasing intimate apparel products.
How to use https://www.perofil.com
(Accessibility & Operability)
We strive to make https://www.perofil.com simple to use for everyone. Here's an overview of how to navigate and use our service with assistive technologies or special configurations:
How to use https://www.perofil.com
Users can browse the catalog, add products to their cart, create an account, and complete a purchase. They can also contact customer service.
Accessibility of https://www.perofil.com
It uses standard methods of interaction with the operating system and assistive technologies.
If you need further explanation on the use of any part of https://www.perofil.com, please contact our support for personalized assistance. We aim to provide any additional description or explanation necessary for the correct functioning of the service.
Accessibility Compliance
(How we meet the requirements)
We have evaluated https://www.perofil.com against the requirements of the European Accessibility Act (and its local application where necessary), the ADA, WCAG 2.2, Section 508 and it is:
Perceivable
- The content is presented in an order that reflects the logical and semantic structure, allowing assistive technologies to interpret it correctly.
- The instructions provided for understanding and operating on content do not rely exclusively on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.
- Content adapts correctly to screen orientation, maintaining consistent display and functionality.
- Where present, the purpose of input fields that accept specific data is correctly communicated to assistive devices and is implemented in a compliant manner.
- Information is not conveyed solely through color, or an accessible alternative such as text or symbols is provided.
- Information is presented using text, avoiding non-essential and non-customizable text images.
- Essential components, even in different states, have a color contrast with adjacent elements that meets the minimum ratio of 3:1.
- Changing text spacing, regarding line height, spacing between paragraphs, letters or words, does not result in loss of information or content.
Usable
- There are no keyboard traps (it is possible to navigate freely within and outside all components).
- There is no interference with shortcut keys made of single letters, numbers or symbols.
- Content-imposed time limits are not present or, if present, are user-controllable, adjustable, extendable or justified by functional or regulatory needs.
- All moving content, if present, is provided with pause and/or playback controls.
- Flashing or flickering content is not used at levels that could cause epileptic seizures, remaining within safety limits.
- Skiplinks are implemented to allow quick navigation to main content, improving accessibility and user experience.
- Service flow screens have titles that describe their topic or purpose.
- There are multiple ways to identify content within the environment.
- Elements that can receive keyboard navigation focus are always at least partially visible in the viewport.
- All functionalities do not require complex gestures to be used.
- Functions do not start immediately on touch, can be cancelled before completion, and do not require holding down to operate.
- For user interface components with labels that include text or text images, the name read by assistive devices contains the visually presented text.
- All functionalities are usable without relying exclusively on device or user movement.
- All functionalities are usable without necessarily having to be dragged.
- The clickable area of interactive elements is large enough to ensure smooth interaction for users.
Understandable
- The language of each page is appropriately defined and used consistently throughout the service.
- All language parts that require it are programmatically determinable.
- User interface components, when they receive keyboard navigation focus, do not generate unexpected context changes that could disorient the user.
- User interface components, when activated by the user via keyboard or assistive technologies, do not generate unexpected context changes that could disorient the user.
- The navigation mechanisms present are positioned consistently throughout the entire service flow.
- Repeated interface elements are defined consistently to facilitate their identification.
- Within the environment, mechanisms for requesting support or help are consistent.
- When an input error is automatically detected, the erroneous element is identified and the error is described via text.
- When an input error is identified and suggestions for correction are known, these suggestions are provided to the user, except in cases provided for by law.
- We write content in clear and simple language.
Robust
- Standard development technologies interpretable by assistive technologies are used.
We have tested https://www.perofil.com with the most common assistive technologies in a wide variety of Operating System-Browser configurations:
- Screen readers (such as NVDA and JAWS on Windows, VoiceOver on Mac and iOS) to confirm that all interactive elements are correctly announced and can be used.
- We also test screen magnification and high contrast modes.
We aim for compatibility with current versions of leading assistive technologies. Our code follows best practices outlined in WCAG 2.2 and EN 301 549 for robust implementation, meaning it should remain accessible even 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 the requirements of the EAA, ADA and other regulations based on the same technical standards.
Continuous monitoring and maintenance
For us, accessibility is not a one-time commitment, but an ongoing process. Here's how we ensure that https://www.perofil.com remains accessible over time:
- Our accessibility coordinator, who oversees the accessibility of https://www.perofil.com can be contacted at this email address compliance@cspinternational.it.
- With the support of AccessiWay, on 23/06/2026 we conducted an external manual audit guided by experts to verify our accessibility compliance. We maintain a continuous testing and improvement cycle, with recurring support to ensure that comprehensive audits, including manual testing by professionals using assistive technologies, are conducted at least once a year.
- We use automated testing tools integrated into our development process to identify common accessibility issues early (such as missing alt text or form labeling). Every code update goes through these checks.
Feedback and Contact
We welcome your suggestions to improve https://www.perofil.com. If you find problems or have suggestions, please contact us via email, phone or mail. Explain the details of the problem so we can help you.
We value the input of our users, especially if they inform us that something is not working. If you have difficulty accessing any part of https://www.perofil.com, if you encounter an accessibility issue or if you have suggestions for improvement, please let us know.
Email: compliance@cspinternational.it
Phone: +3903768101
Company address: via Piubega 5c, Ceresara (MN) Italy
When contacting us, please provide as many details about the issue as possible (which page or function, what happened, and what assistive technology you are using, if applicable). We will endeavor to acknowledge your feedback within 15 business days and will do our best to resolve the issue quickly or inform you of progress.
Application: In the event that you feel your accessibility issues have not been adequately addressed, you have the right to escalate your complaint. We sincerely hope to resolve any issues with you before they reach this stage.
Document History: This document was last reviewed and updated on 23/06/2026. We plan to review it at least annually, or whenever significant changes to the service occur.
EN301549 Technical Report
Chapter 5: Generic Requirements
| Criteria | Compliance Levels | Annotations |
|---|---|---|
| 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 from 5.2 to 13 |
| 5.1.2.2 Assistive technology | See 5.1.3 to 5.1.6 | See information from 5.1.3 to 5.1.6 |
| 5.1.3 Non-visual access | Header cell no response required | Header cell no response required |
| 5.1.3.1 Audio output of visual information | Not applicable | |
| 5.1.3.2 Playback of audio output including speech | Not applicable | |
| 5.1.3.3 Correlation of audio output | Not applicable | |
| 5.1.3.4 User control of speech output | Not applicable | |
| 5.1.3.5 Automatic interruption of speech output | Not applicable | |
| 5.1.3.6 Speech output for non-text content | Not applicable | |
| 5.1.3.7 Speech output for video information | Not applicable | |
| 5.1.3.8 Masked input | Not applicable | |
| 5.1.3.9 Private access to personal data | Not applicable | |
| 5.1.3.10 Audio output without interference | Not applicable | |
| 5.1.3.11 Private listening volume | Not applicable | |
| 5.1.3.12 Speaker volume | Not applicable | |
| 5.1.3.13 Volume restoration | Not applicable | |
| 5.1.3.14 Spoken languages | Not applicable | |
| 5.1.3.15 Non-visual error identification | Not applicable | |
| 5.1.3.16 Receipts, tickets, transactional results | Not applicable | |
| 5.1.4 Closed functionality with text enlargement | Not applicable | |
| 5.1.5 Visual output for audio information | Not applicable | |
| 5.1.6 Operation without keyboard interface | Header cell no response required | Header cell no response required |
| 5.1.6.1 Closed functionality | See 5.1.3.1 to 5.1.3.16 | See information from 5.1.3.1 to 5.1.3.16 |
| 5.1.6.2 Input focus | Not applicable | |
| 5.1.7 Non-speech access | Not applicable | |
| 5.2 Activation of accessibility features | Not applicable | |
| 5.3 Biometrics | Not applicable | |
| 5.4 Retention of accessibility information during conversion |
Not applicable | |
| 5.5 Usable parts | Header cell no response required | Header cell no response required |
| 5.5.1 Modes of use | Not applicable | |
| 5.5.2 Discernibility of usable parts | Not Applicable | |
| 5.6 Latching or Toggle Controls | Heading cell No response required | Heading cell No response required |
| 5.6.1 Tactile or Auditory Status | Not Applicable | |
| 5.6.2 Visual Status | Not Applicable | |
| 5.7 Key Repeat | Not Applicable | |
| 5.8 Double-Strike Acceptance | Not Applicable | |
| 5.9 Simultaneous User Actions | Not Applicable |
Chapter 6: ICT with Two-Way Voice Communication
| Criteria | Levels of Conformance | Remarks |
|---|---|---|
| 6.1 Audio Bandwidth for Speech | Not Applicable | |
| 6.2 Real-Time Text (RTT) Functionality | Heading cell No response required | Heading cell No response required |
| 6.2.1.1 Real-Time Text (RTT) Communication | Not Applicable | |
| 6.2.1.2 Voice and Text Concurrently | Not Applicable | |
| 6.2.2.1 Visually Distinct Display | ||
| 6.2.2.2 Programmatically Determinable Send and Receive Direction | Not Applicable | |
| 6.2.2.3 Speaker Identification | Not Applicable | |
| 6.2.2.4 Visual Indicator of Audio with Real-Time Text (RTT) | Not Applicable | |
| 6.2.3 Interoperability | Not Applicable | |
| 6.2.4 Real-Time Text (RTT) Responsiveness | Not Applicable | |
| 6.3 Caller ID | Not Applicable | |
| 6.4 Alternatives to Voice-Based Services | Not Applicable | |
| 6.5 Video Communications | Heading cell No response required | Heading cell No response required |
| 6.5.1 General (Advisory) | Heading cell No response required | Heading cell No response required |
| 6.5.2 Resolution | Not Applicable | |
| 6.5.3 Frame Rate | Not Applicable | |
| 6.5.4 Audio and Video Synchronization | Not Applicable | |
| 6.5.5 Visual Indicator of Audio with Video | Not Applicable | |
| 6.5.6 Speaker Identification with Video Communication (Sign Language) | Not Applicable | |
| 6.6 Alternatives to Video-Based Services (Advisory) | Advisory No response required | Advisory No response required |
Chapter 7: ICT with Video Functionality
| Criteria | Levels of Conformance | Remarks |
|---|---|---|
| 7.1 Caption Processing Technology | Heading cell No response required | Heading cell No response required |
| 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 Characteristics | Not Applicable | |
| 7.1.5 Spoken Captions | Not Applicable | |
| 7.2 Audio Description Technology | Header cell no response required | Header cell no response required |
| 7.2.1 Audio description playback | Not applicable | |
| 7.2.2 Audio description synchronization | Not applicable | |
| 7.2.3 Storage of audio description | Not applicable | |
| 7.3 User controls for captions and audio description | Not applicable |
Chapter 8: Hardware
| Criteria | Conformance Levels | Remarks |
|---|---|---|
| 8.1.1 General requirements | Header cell no response required | Header cell no response required |
| 8.1.2 Standard Connections | Not applicable | |
| 8.1.3 Colour | Not applicable | |
| 8.2 Hardware Products with Voice Output | Header cell no response required | Header cell no response required |
| 8.2.1.1 Speech volume range | Not applicable | |
| 8.2.1.2 Incremental volume control | Not applicable | |
| 8.2.2.1 Landline devices | Not applicable | |
| 8.2.2.2 Wireless communication systems | Not applicable | |
| 8.3 Fixed ICT | Header cell no response required | Header cell no response required |
| 8.3.2.1 Unobstructed forward approach high | Not applicable | |
| 8.3.2.2 Unobstructed forward approach low | Not applicable | |
| 8.3.2.3.1 Clear floor or ground space | Not applicable | |
| 8.3.2.3.2 Obstructed forward approach (< 510 mm) | Not applicable | |
| 8.3.2.3.3 Obstructed forward approach (< 635 mm) | Not applicable | |
| 8.3.2.4 Knee and toe clearance width | Not applicable | |
| 8.3.2.5 Toe clearance | Not applicable | |
| 8.3.2.6 Knee clearance | Not applicable | |
| 8.3.3.1 Unobstructed side approach high | Not applicable | |
| 8.3.3.2 Unobstructed side approach low | Not applicable | |
| 8.3.3.3.1 Obstructed side approach (< 255 mm) | Not applicable | |
| 8.3.3.3.2 Obstructed side approach (< 610 mm) | Not applicable | |
| 8.3.4.1 Change of level | Not applicable | |
| 8.3.4.2 Clear floor or ground space or operating area | Not applicable | |
| 8.3.4.3.2 Forward approach | Not applicable | |
| 8.3.4.3.3 Side approach | Not applicable | |
| 8.3.5 Visibility | Not applicable | |
| 8.3.6 Installation instructions | Not applicable | |
| 8.4 Mechanically Operated Parts | Header cell no response required | Header cell no response required |
| 8.4.1 Numeric keys | Not applicable | |
| 8.4.2.1 Operating methods for mechanical parts | Not applicable | |
| 8.4.2.2 Operating force for mechanical parts | Not applicable | |
| 8.4.3 Keys, Tickets and Tariff Cards | Not applicable | |
| 8.5 Tactile Indication of Speech Mode | Not applicable |
Chapter 9: Web (also applies to 10, 11 and 12)
Corresponding to WCAG 2.2 Level A
| Criteria | Compliance Levels | Annotations |
|---|---|---|
| 1.1.1 Non-text Content | Partially supported | There is non-text content shown to the user that does not have an equivalent text alternative. |
| 1.2.1 Audio Only and Video Only (Prerecorded) | Supported | |
| 1.2.2 Captions (Prerecorded) | Supported | |
| 1.2.3 Audio Description or Alternative Media (Prerecorded) | Supported | |
| 1.3.1 Information and Relationships | Partially supported | In some cases, information, structure, or relationships conveyed by page presentation cannot be programmatically determined (or are not available via text); |
| 1.3.2 Meaningful Sequence | Supported | |
| 1.3.3 Sensory Characteristics | Supported | |
| 1.4.1 Use of Color | Supported | |
| 1.4.2 Audio Control | Supported | |
| 2.1.1 Keyboard | Partially supported | Some functionalities cannot be used via keyboard (or similar input interface); |
| 2.1.2 No Keyboard Trap | Supported | |
| 2.1.4 Shortcut Keys | Supported | |
| 2.2.1 Timing Adjustable | Supported | |
| 2.2.2 Pause, Stop, Hide | Supported | |
| 2.3.1 Three Flashes or Below Threshold | Supported | |
| 2.4.1 Bypass Blocks | Supported | |
| 2.4.2 Page Titled | Supported | |
| 2.4.3 Focus Order | Partially supported | In some sections that can be navigated sequentially and where the navigation sequence affects their meaning and functionality, some objects that could receive focus do not receive it in an order that maintains their meaning and operability; |
| 2.4.4 Link Purpose (In Context) | Partially supported | The purpose of some links cannot be determined from the link text or from the link text combined with adjacent content; |
| 2.5.1 Pointer Gestures | Supported | |
| 2.5.2 Pointer Cancellation | Supported | |
| 2.5.3 Label in Name | Supported | |
| 2.5.4 Motion Actuation | Supported | |
| 3.1.1 Language of Page | Supported | |
| 3.2.1 On Focus | Supported | |
| 3.2.2 On Input | Supported | |
| 3.2.6 Consistent Help | Supported | |
| 3.3.1 Error Identification | Supported | |
| 3.3.2 Labels or Instructions | Partially supported | In some cases, labels or instructions are not provided when the content requires user input actions; |
| 3.3.7 Redundant Entry | Supported | |
| 4.1.1 Parsing | Supported | |
| 4.1.2 Name, Role, Value | Partially supported | In some cases, user interface components (including: form elements, links and script-generated components...), name, role, states, properties and values are not correct or set, or the user and their assistive technologies are not notified when these change; |
Corresponding to WCAG 2.2 Level AA
| Criteria | Conformance levels | Notes |
|---|---|---|
| 1.2.5 Audio Description (Prerecorded) | Supported | |
| 1.3.4 Orientation | Supported | |
| 1.3.5 Identify Input Purpose | Supported | |
| 1.4.3 Contrast (Minimum) | Partially Supported | The visual presentation of text and images of text does not always have the required minimum contrast ratio, except for foreseen exceptions (e.g., logos); |
| 1.4.4 Text Resizing | Partially Supported | Some text, excluding captions and images of text, cannot be resized up to 200 percent without assistive technologies and without losing content and functionality; |
| 1.4.5 Images of Text | Supported | |
| 1.4.10 Reflow | Partially Supported | Content that does not require a two-dimensional layout (such as data tables or maps) does not reflow when the viewport size changes; |
| 1.4.11 Non-text Contrast | Supported | |
| 1.4.12 Text Spacing | Supported | |
| 1.4.13 Content on Hover or Focus | Partially Supported | In some cases, when content is made visible and hidden by mouse hover or keyboard focus, there is no mechanism to dismiss the additional content without moving the mouse pointer or keyboard focus, the pointer cannot be moved over the additional content without it disappearing, or the additional content does not remain visible until the hover or focus event is removed, the user dismisses it, or its information is no longer valid, with some exceptions; |
| 2.4.5 Multiple Ways | Supported | |
| 2.4.6 Headings and Labels | Partially Supported | Headings and/or labels do not sufficiently clarify content or functionality; |
| 2.4.7 Focus Visible | Partially Supported | On some interactive elements, the focus indicator is not visible; |
| 2.4.11 Focus Not Obscured (Minimum) | Supported | |
| 2.5.7 Dragging Movements | Supported | |
| 2.5.8 Target Size (Minimum) | Supported | |
| 3.1.2 Language of Parts | Supported | |
| 3.2.3 Consistent Navigation | Supported | |
| 3.2.4 Consistent Identification | Supported | |
| 3.3.3 Error Suggestion | Supported | |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supported | |
| 3.3.8 Accessible Authentication (Minimum) | Supported | |
| 4.1.3 Status Messages | Partially Supported | In some cases, status messages are not presented to the user in a way that assistive technologies can interpret them without having to move the focus; |
Chapter 10: Non-web Documents
| Criteria | Conformance levels | Notes |
|---|---|---|
| 10.0 General (Informative) | Header cell no response required | Header cell no response required |
| From 10.1.1.1 to 10.4.1.3 | See WCAG 2.2 section | See information in WCAG 2.2 section |
| 10.5 Caption positioning | Not applicable | |
| 10.6 Audio description timing | Not applicable |
Chapter 11: Software
| Criteria | Conformance levels | Notes |
|---|---|---|
| 11.0 General (Informative) | Header cell no response required | Header cell no response required |
| From 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 | Header cell no response required | Header cell no response required |
| 11.5.1 Closed Functionality | Header cell no response required | Header cell no response required |
| 11.5.2 Accessibility Services | Header cell no response required | Header cell no response required |
| 11.5.2.1 Platform Accessibility Service Support for Software that Provides a User Interface |
See 11.5.2.5 to 11.5.2.17 | See information from 11.5.2.5 to 11.5.2.17 |
| 11.5.2.2 Platform Accessibility Service Support for Assistive Technologies | See 11.5.2.5 to 11.5.2.17 | See information from 11.5.2.5 to 11.5.2.17 |
| 11.5.2.3 Use of Accessibility Services | See 11.5.2.5 to 11.5.2.17 | See information from 11.5.2.5 to 11.5.2.17 |
| 11.5.2.4 Assistive Technology | Not applicable | |
| 11.5.2.5 Object Information | Not applicable | |
| 1.5.2.6 Row, Column, and Headers | Not applicable | |
| 11.5.2.7 Values | Not applicable | |
| 11.5.2.8 Label Relationships | Not applicable | |
| 11.5.2.9 Parent-Child Relationships | Not applicable | |
| 11.5.2.10 Text | Not applicable | |
| 11.5.2.11 List of Available Actions | Not applicable | |
| 11.5.2.12 Perform Available Actions | Not applicable | |
| 11.5.2.13 Tracking Focus and Selection Attributes | Not applicable | |
| 11.5.2.14 Modifying Focus and Selection Attributes | Not applicable | |
| 11.5.2.15 Notification of Changes | Not applicable | |
| 11.5.2.16 Changes to States and Properties | Not applicable | |
| 11.5.2.17 Changes to Values and Text | Not applicable | |
| 11.6 Accessibility Usage Documentation | Header cell no response required | Header cell no response required |
| 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 Development Tools | Header cell no response required | Header cell no response required |
| 11.8.1 Content Technology | Header cell no response required | Header cell no response required |
| 11.8.2 Accessible Content Authoring | See WCAG 2.2 section (If the software is not a development tool, enter "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
| Criteria | Conformance Levels | Remarks |
|---|---|---|
| 12.1 Product Documentation | Header cell no response required | Header cell no response required |
| 12.1.1 Accessibility and Compatibility Features | Not applicable | |
| 12.1.2 Accessible Documentation | See WCAG 2.2 section | See information in WCAG 2.2 section |
| 12.2 Support Services | Heading Cell No Response Required | Heading Cell No Response Required |
| 12.2.2 Information on Accessibility and Compatibility Features | 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 Providing Emergency Service Relays or Access
| Criteria | Conformance Levels | Notes |
|---|---|---|
| 13.1 Relay Service Requirements | Heading Cell No Response Required | Heading 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.1.5 Captioned Telephone Services | Not Applicable | |
| 13.1.6 Text-to-Speech Services | Not Applicable | |
| 13.2 Access to Relay Services | Not Applicable | |
| 13.3 Access to Emergency Services | Not Applicable |
WEB Accessibility
Disability is defined as: any limitation of activity or restriction of participation in society, experienced by a person as a result of a substantial, lasting or permanent alteration of one or more physical, sensory, mental, cognitive or psychic functions, of a multiple disability or of an incapacitating health condition.
Web accessibility consists of making online public communication services accessible to people with disabilities and is based on four fundamental principles:
Perceivable: Information and user interface components must be presented to users in a way they can perceive. For example, by providing text alternatives for all non-text content that can then be presented in other forms according to user needs: large print, braille, speech, symbols, or simpler language.
Operable: User interface components and navigation must be operable. For example, by making all functionality available via keyboard.
Understandable: Information and the operation of user interface must be understandable. Text content must be readable, and navigation must be consistent.
Robust: Content must be robust enough to be interpreted reliably by a wide range of user agents, including assistive technologies.
Test Environments
Operating Systems
- Apple Mac OS X (latest version)
- Microsoft Windows (latest version)
- Apple iOS (latest version)
- Google Android (latest version)
We did not use Linux as it is currently very uncommon among users with disabilities.
Browsers and User Software
In the latest versions available on different operating systems:
- Google Chrome
- Windows Edge
- Safari
- Adobe Acrobat Reader / Preview on Mac (for PDFs only)
Screen Readers and Assistive Technologies
To obtain the most standard evaluation possible, we test everything with the default configuration of assistive technologies.
To make the evaluation more realistic, we also test:
- Graphical adaptations present in different systems (colors, contrasts, subtitles, etc.)
- Mouse emulations, magnifiers, and on-screen keyboards or advanced keyboard settings, also from different systems
- VoiceOver – only on Apple systems
- TalkBack – only on Android
- NVDA (latest version) and Freedom Scientific JAWS (penultimate version) – only on PC systems
Methodology
Objective Manual and Semi-Automatic Verification Methodology
We analyze content with various automatic and semi-automatic systems and compare the results between tools to achieve the most complete and objective verification possible. The reference standard, unless specifically requested, is always the latest available (WCAG 2.2), to ensure compliance in all countries from which the touchpoint (website, app, etc.) can be accessed.
Our verification is therefore compliant with WCAG 2.2 level AA and the requirements of UNI EN 301549 Guidelines or their application in the French RGAA. Each tool produces results that are then analyzed by our experts: it is therefore possible that not all tool results appear, as they may be deemed false negatives.
Automatic Tools for Syntax Control
- W3C Markup Validation Service: Used with generated code, as it is the official tool for checking HTML, XHTML, MathML, etc.
- W3C CSS Validation service: Although CSS correctness does not directly impact accessibility, it could affect some related aspects if not interpreted correctly due to errors. Verification is therefore appropriate and is carried out with the W3C CSS Validation Service.
- PAC PDF checker
Automatic and Semi-Automatic Tools for Color Verification
- Color Contrast Analyzer (CCA): Used specifically for doubtful contrasts.
- WCAG Color contrast checker: Used as a first check to verify the contrasts of colors used in the CSS of pages.
- Text on background image a11y check: Used to check cases where text should overlap images.
- Color contrast accessibility evaluator: Used as an additional check for some online pages.
Automatic and Semi-Automatic Tools for Accessibility Checking
Some online validators used as a sample on pages:
- Accescan
- Wave
And other tools:
- Web developer toolbar: Used to support manual verification. It allows identifying images without alternative text, fields without labels, etc.
- AXE and Lighthouse for Chrome: Provide precise indications of accessibility flaws in HTML code, as well as WAI-ARIA attributes, which are fundamental for web applications and interactive components.
Terminology
The terms used in the Conformance Levels information are defined as follows:
Supported: The product's functionality has at least one method that meets the criterion without known defects or meets it with equivalent facilitation.
Partially Supported: Some of the product's functionalities do not meet the criterion.
Not Supported: Most of the product's functionalities do not meet the criterion.
Not Applicable: The criterion is not relevant for the product.
Not Evaluated: The product has not been evaluated against the criterion. This can only be used for WCAG AAA level criteria.
Not Evaluated: The product has not been evaluated against the criterion. This can only be used for WCAG AAA level criteria.
