Accessibility
Accessibility Conformance Report – www.iporticihotel.com
Last updated: 23/10/2026
This document is written in a simplified form and in clear, understandable language in accordance with the accessibility principles and requirements established by Directive (EU) 2019/882 and Italian Legislative Decree no. 82 of 27 May 2022, with particular reference to the obligation to provide information that is perceivable, operable, understandable and robust for all users, including persons with disabilities.
Pursuant to Article 12 of Legislative Decree 82/2022 and Annex I, sections III and IV, information on the accessibility of services must be presented in a clear, understandable and accessible way, including through the use of plain language and a simple structure.
The concise and simple form of this document is therefore a direct implementation of a legal obligation and does not limit the information available, which remains fully governed by the relevant technical and legal documentation.
This document was provided by Accessiway to fulfil 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 be able 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 WCAG.
RBR IMMOBILIARE SRL is committed to accessibility and inclusion. We want all our customers, including people with disabilities, to be able to use our service successfully.
This document describes the accessibility features of www.iporticihotel.com, how we meet the requirements of the European Accessibility Act, the EN 301 549 standard, WCAG 2.2, the ADA and Section 508, and what we are doing to maintain and improve accessibility. This statement applies only to www.iporticihotel.com.
We regularly review this information as we improve www.iporticihotel.com.
Overview
Service description
Website presenting Hotel I Portici and its services. In addition to rooms, the hotel offers restaurants, the Portici Shop e-commerce and bookable services and experiences.
How to use www.iporticihotel.com (Accessibility & Operation)
We strive to make www.iporticihotel.com easy to use for everyone. Here is an overview of how to navigate and use our service with assistive technologies or special configurations:
How to use www.iporticihotel.com
Simple browsing. There is no reserved area. Users can download PDF files to consult menus or commercial information. They are redirected to external platforms for the actual booking.
Accessibility of www.iporticihotel.com
It uses the standard interaction methods of the operating system and assistive technologies.
If you need further explanation on how to use any part of www.iporticihotel.com, please contact our support for personalised assistance. We aim to provide any additional description or explanation needed for the service to work properly.
Accessibility conformance (How we meet the requirements)
We have assessed www.iporticihotel.com against the requirements of the European Accessibility Act (and, where necessary, its national implementation), the ADA, WCAG 2.2 and Section 508, and it is:
Perceivable
- Content is presented in a clear, logical order that assistive technologies can interpret.
- Instructions do not rely solely on characteristics such as shape, colour, size, location or sound.
- Content adapts correctly to screen orientation, keeping display and operation consistent.
- Where present, the purpose of input fields is clearly conveyed to assistive technologies.
- Information is not conveyed by colour alone, or clear text or a symbol is also provided.
- Information is presented as text rather than images of text, unless necessary.
- Important components have sufficient colour contrast against adjacent elements, in all their states.
- Changing text spacing does not cause loss of information.
- Where present, content shown on pointer hover or focus does not disappear unexpectedly and can be dismissed easily.
Operable
- Users can move freely with the keyboard and never get trapped in a component.
- Where present, single-character keyboard shortcuts do not trigger unexpected actions.
- There are no time limits, or users can control or extend them when needed.
- There is no flashing or blinking content that could cause seizures.
- Skip links make it easy to reach the main content.
- When navigation order is meaningful, focus follows a clear and correct order.
- Content can be reached in more than one way.
- Headings and labels clearly describe content and functionality.
- Elements receiving keyboard focus are always visible on screen.
- All functionality can be used without complex gestures.
- Functions are not triggered immediately on touch, can be cancelled and do not require a long press.
- The name read by assistive technologies matches the visible label text.
- All functionality works without requiring device or user motion.
- All functionality works without requiring dragging movements.
- Interactive elements have a target area large enough to be used easily.
Understandable
- Each page has a defined language that is used consistently.
- Where present, changes of language in the text can be recognised by assistive technologies.
- Keyboard focus on an element does not cause unexpected changes.
- Activating an element does not cause unexpected changes.
- Navigation options are always in the same place throughout the service.
- Repeated interface elements are always the same and easy to recognise.
- Help and support options are consistent throughout the service.
- When an input error is detected, the field in error is identified and described in text.
- Input fields have labels or instructions when needed.
- When an input error occurs, suggestions for correcting it are provided where possible.
- We write content in clear and plain language.
Robust
- Standard technologies are used that assistive technologies can interpret.
- Status messages can be read by assistive technologies without moving focus.
We have tested www.iporticihotel.com with the most common assistive technologies across a wide range of operating system and 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 can be operated.
- We also test screen magnification and high-contrast modes.
We aim for compatibility with current versions of the main assistive technologies. Our code follows the best practices outlined in WCAG 2.2 and EN 301 549 for a 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 the requirements of the EAA, the ADA and other regulations based on the same technical standards.
Ongoing monitoring and maintenance
For us, accessibility is not a one-off effort but an ongoing process. This is how we ensure that www.iporticihotel.com remains accessible over time:
- With the support of AccessiWay, on 23/10/2026 we carried out an external, expert-led manual audit to verify our accessibility conformance. We maintain a cycle of continuous testing and improvement, with recurring support to ensure that full audits, including manual testing by professionals using assistive technologies, are carried out at least once a year.
- Our developers and content creators regularly receive training in accessible design (for example, on ARIA techniques, colour contrast and writing descriptive link text). We keep everyone up to date on accessibility best practices.
- We use automated testing tools integrated into our development process to detect the most common accessibility issues early (such as missing alt text or form labels). Every code update goes through these checks.
Feedback and contacts
We welcome your suggestions to make www.iporticihotel.com better. If you find problems or have suggestions, contact us by email, phone or post. Describe the problem in detail so we can help you.
We greatly value our users’ input, especially when they tell us that something is not working. If you have difficulty accessing any part of www.iporticihotel.com, encounter an accessibility problem or have suggestions for improvement, please let us know.
Email: info@iporticihotel.com
Phone: 051 421 8564
Company address: Via Indipendenza 69, 40121 Bologna, Italy
When contacting us, please give as much detail as possible about the problem (which page or feature, what happened and which assistive technology you are using, if any). We will try to acknowledge your feedback within 15 working days and will do our best to resolve the problem quickly or keep you informed of progress.
Enforcement: if you believe your accessibility issues have not been adequately addressed, you have the right to file a complaint. We sincerely hope to resolve any problem together with you before it reaches this stage.
Document history: this document was last reviewed and updated on 23/10/2026. We plan to review it at least annually, or whenever significant changes are made to the service.
EN 301 549 technical report
Chapter 5: Generic requirements
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 5.1 Closed functionality | Heading cell – no response required | Heading cell – no response required |
| 5.1.2 General | Heading cell – no response required | Heading 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 | Heading cell – no response required | Heading cell – no response required |
| 5.1.3.1 Audio output of visual information | Not applicable | |
| 5.1.3.2 Auditory output delivery including speech | Not applicable | |
| 5.1.3.3 Auditory output correlation | Not applicable | |
| 5.1.3.4 Speech output user control | Not applicable | |
| 5.1.3.5 Speech output automatic interruption | 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 entry | Not applicable | |
| 5.1.3.9 Private access to personal data | Not applicable | |
| 5.1.3.10 Non-interfering audio output | Not applicable | |
| 5.1.3.11 Private listening volume | Not applicable | |
| 5.1.3.12 Speaker volume | Not applicable | |
| 5.1.3.13 Volume reset | 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, and transactional outputs | Not applicable | |
| 5.1.4 Functionality closed to text enlargement | Not applicable | |
| 5.1.5 Visual output for auditory information | Not applicable | |
| 5.1.6 Operation without keyboard interface | Heading cell – no response required | Heading cell – no response required |
| 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 Access without speech | Not applicable | |
| 5.2 Activation of accessibility features | Not applicable | |
| 5.3 Biometrics | Not applicable | |
| 5.4 Preservation of accessibility information during conversion | Not applicable | |
| 5.5 Operable parts | Heading cell – no response required | Heading cell – no response required |
| 5.5.1 Means of operation | Not applicable | |
| 5.5.2 Operable parts discernibility | Not applicable | |
| 5.6 Locking 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 key acceptance | Not applicable | |
| 5.9 Simultaneous user actions | Not applicable |
Chapter 6: ICT with two-way voice communication
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 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 RTT communication | Not applicable | |
| 6.2.1.2 Concurrent voice and text | Not applicable | |
| 6.2.2.1 Visually distinguishable 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 RTT | Not applicable | |
| 6.2.3 Interoperability | Not applicable | |
| 6.2.4 RTT responsiveness | Not applicable | |
| 6.3 Caller ID | Not applicable | |
| 6.4 Alternatives to voice-based services | Not applicable | |
| 6.5 Video communication | Heading cell – no response required | Heading cell – no response required |
| 6.5.1 General (informative) | 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 Synchronization between audio and video | Not applicable | |
| 6.5.5 Visual indicator of audio with video | Not applicable | |
| 6.5.6 Speaker identification with video (sign language) communication | Not applicable | |
| 6.6 Alternatives to video-based services (informative) | Advisory – no response required | Advisory – no response required |
Chapter 7: ICT with video capabilities
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 7.1 Caption processing technology | Heading cell – no response required | Heading cell – no response required |
| 7.1.1 Captioning playback | Not applicable | |
| 7.1.2 Captioning synchronization | Not applicable | |
| 7.1.3 Preservation of captioning | Not applicable | |
| 7.1.4 Captions characteristics | Not applicable | |
| 7.1.5 Spoken subtitles | Not applicable | |
| 7.2 Audio description technology | Heading cell – no response required | Heading cell – no response required |
| 7.2.1 Audio description playback | Not applicable | |
| 7.2.2 Audio description synchronization | Not applicable | |
| 7.2.3 Preservation of audio description | Not applicable | |
| 7.3 User controls for captions and audio description | Not applicable |
Chapter 8: Hardware
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 8.1.1 Generic requirements | Heading cell – no response required | Heading cell – no response required |
| 8.1.2 Standard connections | Not applicable | |
| 8.1.3 Colour | Not applicable | |
| 8.2 Hardware products with speech output | Heading cell – no response required | Heading 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 Fixed-line devices | Not applicable | |
| 8.2.2.2 Wireless communication devices | Not applicable | |
| 8.3 Stationary ICT | Heading cell – no response required | Heading cell – no response required |
| 8.3.2.1 Unobstructed high forward reach | Not applicable | |
| 8.3.2.2 Unobstructed low forward reach | Not applicable | |
| 8.3.2.3.1 Clear space | Not applicable | |
| 8.3.2.3.2 Obstructed (< 510 mm) forward reach | Not applicable | |
| 8.3.2.3.3 Obstructed (< 635 mm) forward reach | 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 high side reach | Not applicable | |
| 8.3.3.2 Unobstructed low side reach | Not applicable | |
| 8.3.3.3.1 Obstructed (≤ 255 mm) side reach | Not applicable | |
| 8.3.3.3.2 Obstructed (≤ 610 mm) side reach | Not applicable | |
| 8.3.4.1 Change in level | Not applicable | |
| 8.3.4.2 Clear floor or ground space | Not applicable | |
| 8.3.4.3.2 Forward approach | Not applicable | |
| 8.3.4.3.3 Parallel approach | Not applicable | |
| 8.3.5 Visibility | Not applicable | |
| 8.3.6 Installation instructions | Not applicable | |
| 8.4 Mechanically operable parts | Heading cell – no response required | Heading cell – no response required |
| 8.4.1 Numeric keys | Not applicable | |
| 8.4.2.1 Means of operation of mechanical parts | Not applicable | |
| 8.4.2.2 Force of operation of mechanical parts | Not applicable | |
| 8.4.3 Keys, tickets and fare 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 | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially supports | Some images, icons or other non-text content do not have a text alternative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Supports | |
| 1.2.2 Captions (Prerecorded) | Supports | |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Supports | |
| 1.3.1 Info and Relationships | Partially supports | In some cases the structure or meaning of content is only visual and cannot be read by assistive technologies. |
| 1.3.2 Meaningful Sequence | Supports | |
| 1.3.3 Sensory Characteristics | Supports | |
| 1.4.1 Use of Color | Supports | |
| 1.4.2 Audio Control | Supports | |
| 2.1.1 Keyboard | Partially supports | Some functionality cannot be operated with the keyboard. |
| 2.1.2 No Keyboard Trap | Supports | |
| 2.1.4 Character Key Shortcuts | Supports | |
| 2.2.1 Timing Adjustable | Supports | |
| 2.2.2 Pause, Stop, Hide | Partially supports | It is not possible to pause, stop or hide moving or auto-updating content that lasts more than 5 seconds alongside other content. |
| 2.3.1 Three Flashes or Below Threshold | Supports | |
| 2.4.1 Bypass Blocks | Supports | |
| 2.4.2 Page Titled | Partially supports | Some screens do not have a title describing their topic or purpose. |
| 2.4.3 Focus Order | Supports | |
| 2.4.4 Link Purpose (In Context) | Partially supports | The purpose of some links or controls is not clear from their text or context. |
| 2.5.1 Pointer Gestures | Supports | |
| 2.5.2 Pointer Cancellation | Supports | |
| 2.5.3 Label in Name | Supports | |
| 2.5.4 Motion Actuation | Supports | |
| 3.1.1 Language of Page | Supports | |
| 3.2.1 On Focus | Supports | |
| 3.2.2 On Input | Supports | |
| 3.2.6 Consistent Help | Supports | |
| 3.3.1 Error Identification | Supports | |
| 3.3.2 Labels or Instructions | Supports | |
| 3.3.7 Redundant Entry | Supports | |
| 4.1.1 Parsing | Supports | |
| 4.1.2 Name, Role, Value | Partially supports | Some components do not correctly expose their name, role, state or value to assistive technologies, or do not notify them of changes. |
Corresponding to WCAG 2.2 Level AA
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.5 Audio Description (Prerecorded) | Supports | |
| 1.3.4 Orientation | Supports | |
| 1.3.5 Identify Input Purpose | Supports | |
| 1.4.3 Contrast (Minimum) | Partially supports | Text and images of text do not always have sufficient contrast (logos excluded). |
| 1.4.4 Resize Text | Partially supports | Some text cannot be resized up to 200% without loss of content or functionality (captions and images of text excluded). |
| 1.4.5 Images of Text | Supports | |
| 1.4.10 Reflow | Partially supports | Content that does not require a two-dimensional layout does not reflow when the screen size changes. |
| 1.4.11 Non-text Contrast | Supports | |
| 1.4.12 Text Spacing | Supports | |
| 1.4.13 Content on Hover or Focus | Supports | |
| 2.4.5 Multiple Ways | Supports | |
| 2.4.6 Headings and Labels | Supports | |
| 2.4.7 Focus Visible | Partially supports | The keyboard focus indicator is not visible on some interactive elements. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | |
| 2.5.7 Dragging Movements | Supports | |
| 2.5.8 Target Size (Minimum) | Supports | |
| 3.1.2 Language of Parts | Supports | |
| 3.2.3 Consistent Navigation | Supports | |
| 3.2.4 Consistent Identification | Supports | |
| 3.3.3 Error Suggestion | Supports | |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | |
| 3.3.8 Accessible Authentication (Minimum) | Supports | |
| 4.1.3 Status Messages | Supports |
Chapter 10: Non-web documents
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 10.0 General (informative) | Heading cell – no response required | Heading 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 positioning | Not applicable | |
| 10.6 Audio description timing | Not applicable |
Chapter 11: Software
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 11.0 General (informative) | Heading cell – no response required | Heading 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 | Heading cell – no response required | Heading cell – no response required |
| 11.5.1 Closed functionality | Heading cell – no response required | Heading cell – no response required |
| 11.5.2 Accessibility services | Heading cell – no response required | Heading 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 in 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 in 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 in 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 | |
| 11.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 Execution of available actions | Not applicable | |
| 11.5.2.13 Tracking of focus and selection attributes | Not applicable | |
| 11.5.2.14 Modification of focus and selection attributes | Not applicable | |
| 11.5.2.15 Change notification | Not applicable | |
| 11.5.2.16 Modifications of states and properties | Not applicable | |
| 11.5.2.17 Modifications of values and text | Not applicable | |
| 11.6 Documented accessibility usage | Heading cell – no response required | Heading 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 Authoring tools | Heading cell – no response required | Heading cell – no response required |
| 11.8.1 Content technology | Heading cell – no response required | Heading cell – no response required |
| 11.8.2 Accessible content creation | See WCAG 2.2 section | See information in WCAG 2.2 section |
| 11.8.3 Preservation of accessibility information in transformations | Not applicable | |
| 11.8.4 Repair assistance | Not applicable | |
| 11.8.5 Templates | Not applicable |
Chapter 12: Documentation and support services
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 12.1 Product documentation | Heading cell – no response required | Heading 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 relay or emergency service access
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 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 telephony services | Not applicable | |
| 13.1.6 Speech to speech relay 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 impairment of one or more physical, sensory, mental, cognitive or psychological functions, of multiple disabilities or of a disabling health condition.
Web accessibility means making online public communication services accessible to people with disabilities, and it is based on four fundamental principles:
Perceivable: information and user interface components must be presented to users in ways they can perceive. For example, by providing text alternatives for all non-text content so that it can 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 from a keyboard.
Understandable: information and the operation of the 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 variety of user agents, including assistive technologies.
Test environments
Operating systems
- Apple macOS (latest version)
- Microsoft Windows (latest version)
- Apple iOS (latest version)
- Google Android (latest version)
We did not use Linux, as it is currently very little used among users with disabilities.
Browsers and user software
In the latest versions available on the different operating systems:
- Google Chrome
- Microsoft Edge
- Safari
- Adobe Acrobat Reader / Preview on Mac (PDF only)
Screen readers and assistive technologies
To obtain the most standard assessment possible, we test everything with the default configuration of assistive technologies.
To make the assessment more realistic, we also test:
- Graphic adaptations available in the different systems (colours, contrast, captions, etc.)
- Mouse emulation, magnifiers and on-screen keyboards or advanced keyboard settings of the different systems
- VoiceOver – Apple systems only
- TalkBack – Android only
- NVDA (latest version) and Freedom Scientific JAWS (previous version) – PC systems only
Methodology
Objective manual and semi-automatic testing methodology
We analyse content with several automatic and semi-automatic tools and compare the results across tools to obtain the most complete and objective assessment possible. Unless otherwise requested, the reference standard is always the latest available (WCAG 2.2), to ensure conformance in all countries from which the touchpoint (website, app, etc.) can be accessed.
Our assessment therefore conforms to WCAG 2.2 Level AA and to the requirements of UNI EN 301 549 or their implementation in the French RGAA. Each tool produces results that are then analysed by our experts: not all tool results may therefore appear, as some are judged to be false positives.
Automatic syntax-checking tools
- W3C Markup Validation Service: used on generated code, as it is the official tool for checking HTML, XHTML, MathML, etc.
- W3C CSS Validation Service: although CSS correctness does not directly affect accessibility, it may affect related aspects if it is not interpreted correctly because of errors. Checking it is therefore appropriate and is done with the W3C CSS Validation Service.
- PAC PDF checker
Automatic and semi-automatic colour-checking tools
- Color Contrast Analyser (CCA): used for specific checks on doubtful contrasts.
- WCAG Color contrast checker: used as a first check of the colour contrasts used in the page CSS.
- Text on background image a11y check: used to check cases where text overlaps images.
- Color contrast accessibility evaluator: used as an additional check on some online pages.
Automatic and semi-automatic accessibility-checking tools
Some online validators used as a sample on the pages:
- Accescan
- WAVE
And other tools:
- Web Developer Toolbar: used to support manual testing. It helps find images without alternative text, fields without labels, etc.
- axe and Lighthouse for Chrome: they give precise indications of accessibility defects in the HTML code and in WAI-ARIA attributes, which are essential for web applications and interactive components.
Terminology
The terms used in the conformance level information are defined as follows:
Supports: the functionality of the product has at least one method that meets the criterion without known defects or meets it with equivalent facilitation.
Partially supports: some functionality of the product does not meet the criterion.
Does not support: the majority of the product functionality does not meet the criterion.
Not applicable: the criterion is not relevant to the product.
Not evaluated: the product has not been evaluated against the criterion. This can only be used for WCAG Level AAA criteria.