Accessibility conformance report

https://mare.unionlido.com/

Digital accessibility

    This document is intentionally drafted in a simplified form and using clear, plain language, in accordance with the principles and accessibility requirements set out in Directive (EU) 2019/882 (European Accessibility Act).

    Pursuant to Article 4 and Annex I of Directive (EU) 2019/882, accessibility-related information must be provided in a manner that is perceivable, operable, understandable and robust, including through clear and comprehensible language and a non-complex structure.

    Accordingly, the simplified nature of this document represents direct compliance with a legal requirement and does not replace or restrict the validity of more detailed technical or legal documentation, where applicable.

    This document has been provided by Accessiway to comply with the obligations of the European Accessibility Act until the relevant National Authority provides the official template.
    Every complex paragraph is introduced by an explanation in a simpler language.

    Introduction

    We want everyone, including people with disabilities, to use our service easily. This statement explains the steps we take to make it accessible, following laws and standards like the European Accessibility Act and WCAG.

    S.I.T.L.A. S.R.L. is committed to accessibility and inclusivity. We want all our customers, including people with disabilities, to be able to use our service successfully.

    This document explains the accessibility features of https://mare.unionlido.com/, how we meet the requirements of the European Accessibility Act , EN301549 standard, WCAG 2.2, ADA and Sec. 508, and what we are doing to maintain and improve accessibility. This statement covers only https://mare.unionlido.com/.

    We regularly review this informations as we enhance https://mare.unionlido.com/.

    Overview

    Service description

    Informational website

    How to Use https://mare.unionlido.com/
    (Accessibility & Operation)

    We strive to make https://mare.unionlido.com/ simple to use for everyone. Here’s an overview of how to navigate and operate our service when using assistive technologies or special configurations:

    How to use https://mare.unionlido.com/ 

    Users can browse the website and make reservations

    Accessibility of https://mare.unionlido.com/

    Use the standard interaction methods with the operating system and assistive technologies.

    If you need more explanation on using any part of https://mare.unionlido.com/, please contact our support for personalized assistance. We aim to provide any additional description or explanation necessary for you to operate the service smoothly.


    Accessibility Compliance
    (How We Meet Requirements)

    We have assessed https://mare.unionlido.com/ against the European Accessibility Act’s requirements (if needed also to its local application), ADA, WCAG 2.2, Section 508 and ensured it meets them.

    We commit to ensuring that https://mare.unionlido.com/ is:

    Perceivable

    • Content is shown in a clear and logical order that assistive technologies can understand.
    • Instructions do not rely only on things like shape, color, size, position, or sound.
    • The content adapts correctly to the screen orientation, maintaining consistent display and functionality.
    • When present, the purpose of input fields is clearly communicated to assistive technologies.
    • Information is not given by color alone, or a clear text or symbol is also provided.
    • Information is shown as text, not as images of text, unless necessary.
    • Content reflows correctly when the screen size changes, if a two-dimensional layout is not needed.
    • Important components have enough color contrast with nearby elements, even in different states.
    • Changing text spacing does not hide or remove information.
    • If present, content shown on hover or focus does not disappear unexpectedly and can be easily dismissed.

    Operable

    • All features can be used with a keyboard or similar assistive technologies.
    • Users can move freely with the keyboard and are never stuck in a component.
    • If present, single-key shortcuts do not cause unexpected actions.
    • There are no time limits, or users can control or extend them when needed.
    • Moving content has controls to pause or manage playback.
    • There is no flashing or blinking content that could cause seizures.
    • Link text clearly shows where the link goes, on its own or with nearby text.
    • Content can be found in more than one way.
    • Headings and labels clearly describe the content and functions.
    • Elements that receive keyboard focus are always visible on the screen.
    • All features work without needing complex gestures.
    • Features do not start right away when touched, can be canceled, and do not require holding down.
    • The name read by assistive technologies matches the visible label text.
    • All features work without needing to move the device or the user.
    • All features work without needing to drag.
    • Interactive elements are large enough to be easy to use.

    Understandable

    • Each page has a defined language that is used consistently.
    • If present, changes in language within the text can be detected by assistive technologies.
    • Focusing on an element with the keyboard does not cause unexpected changes.
    • Activating an element does not cause unexpected changes.
    • Navigation options are always in the same place across the service.
    • Repeated interface elements are named and used consistently.
    • Help and support options are consistent across the service.
    • When an input error is found, the field is clearly identified and the error is explained in text.
    • Inputs have labels or instructions when needed.
    • When an input error occurs, suggestions to fix it are provided when possible.
    • We write content in clear, simple language.

    Robust

    • Standard technologies that assistive technologies can understand are used.
    • User interface components have clear names and roles, and their status is updated correctly when it changes.
    • Status messages can be read by assistive technologies without moving focus.

    We tested https://mare.unionlido.com/ with the most common assistive technologies in a wide variety 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 can be operated.
    • We also test with screen magnification and high contrast modes.

    We aim for compatibility with current versions of major assistive tools. Our code follows the 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 WCAG 2.2 AA (latest) and  EN 301 549 criteria to ensure accessibility. Meeting these standards creates a presumption of conformity with the EAA’s requirements, ADA  and other regulations based on the same technical standards.

    Ongoing Monitoring and Maintenance

    Accessibility is not a one-time effort for us – it’s an ongoing process. Here’s how we ensure https://mare.unionlido.com/ stays accessible over time:

    • With the support of AccessiWay, we carried out an external, expert-led manual audit on 25/08/2026 to verify our accessibility compliance. We maintain a cycle of continuous testing and improvement, with recurring support in place 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 quickly identify common accessibility issues (such as missing alt text or form labeling). Every code update goes through these checks.

    Feedback and Contact Information

    We welcome your feedback to make https://mare.unionlido.com/ better. If you face any issues or have suggestions, contact us by email, phone, or mail. Share details about the problem so we can help.

    We value the input of our users, especially if something isn’t working for you. If you have any difficulty accessing any part of https://mare.unionlido.com/, discover an accessibility issue, or have suggestions for improvement, please let us know.

    Email: webmaster@unionlido.com

    Phone: +39 041 257 5111

    Company address: Via Fausta, 258 30013 Cavallino-Treporti (Venezia)

    When you contact us, please provide as many details as possible about the issue (which page or feature, what happened, and which assistive technology you are using, if applicable). We will try to acknowledge your feedback within 15 business days and will do our best to resolve the issue promptly or inform you of our progress.

    Enforcement: In the event you feel we have not addressed your accessibility concerns adequately, you have the right to escalate your complaint. We sincerely hope to resolve any issue together with you before it reaches that stage, but this avenue is available.

    Document History: This document was last reviewed and updated on 25/08/2026. We plan to review it at least annually, or whenever significant changes to the service occur.

    EN301549 technical report

    Web accessibility

    Disability is defined as: any activity limitation or participation restriction in society, experienced by a person as a result of a substantial, lasting or definitive alteration of one or more physical, sensory, mental, cognitive, or psychic functions, a multiple disability, or a disabling 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 the user in such a way that they can perceive them. For example, providing textual equivalents for all non-textual content that can then be presented in other forms according to the user's needs: large characters, braille, speech synthesis, symbols or simplified language.

     Operable: User interface and navigation components must be operable. For example, making all functionality available via keyboard.

     Understandable: Information and the use of the user interface must be understandable. Textual content must be made readable and navigation must be consistent.

    Robust: Content must be sufficiently robust to be reliably interpreted by a wide variety 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 have not used Linux as it is currently very uncommon among users with disabilities.

    Browsers and user software

     In the latest versions available on the different operating systems:

    • Google Chrome
    • Windows Edge
    • Safari
    • Adobe Acrobat Reader / Preview on Mac (for PDFs only)

    Screen readers and assistive technologies

    In order to achieve the most standard evaluation we test everything with assistive technologies default configuration.

    In order to make the most realistic evaluation we also test:

    • Graphic adaptations present on the different systems (colors, contrasts, subtitles, etc.)
    • Mouse emulations, magnifiers and screen keyboards or keyboard improved settings  always of the different systems
    • Voiceover - Apple systems only
    • Talkback - Android only
    • NVDA (latest version) and Freedom scientific Jaws (second-to-latest version) - PC systems only

    Methodology

    Objective manual and semi-automatic verification methodology

    We analyze content with different automatic and semiautomatic systems and compare the results between tools to obtain the most complete and objective verification. The reference standard, unless specifically requested, that we use is always the latest (WCAG 2.2) so that we can ensure compliance in all countries from which the touchpoint (site, app, etc.) can be accessed.

    Our verification is therefore compliant with WCAG 2.2 level AA, and the requirements in UNI EN 301549 Guidelines or their declination in the French RGAAs. Each tool produces results that are then analyzed by our experts: it is, therefore, possible that not all tool results appear because they are judged to be false negatives.

    Automated tools for syntax checking

    • W3C Markup Validation Service : used with generated code, because it is the official tool for checking HTML, XHTML,MathHTML, etc.
    • W3C CSS Validation service : although the correctness of the CSS does not affect accessibility, it could affect some aspects that still have an impact on it if not correctly interpreted because it is incorrect. The verification is therefore appropriate and done with W3C CSS Validation Service
    • PAC PDF checker

    Automatic and semi-automatic tools for color verification

    • Color Contrast Analyser (CCA) : used punctually on dubious contrasts.
    • WCAG Color contrast checker : used as the first check to verify the contrasts of the colors used in the CSS of the pages.
    • Text on background image a11y check : used to check when text should overlap images.
    • Color contrast accessibility evaluator : used as an additional control for some online pages.

    Automatic and semi-automatic tools for checking accessibility

    Some online validators used as samples on the pages:

    • Accescan 
    • Wave

    And other local tools:

    • Web developer toolbar: Used to support manual verification. It allowed us to locate images without alt texts, fields without labels, etc.
    • AXE e Lighthouse for Chrome: they have provided us with precise indications on the defects of the accessibility of the HTML code but also on WAI ARIA attributes, fundamental in the case of web applications and interactive components.

    Terms

    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 with equivalent facilitation.

    Partially Supports: Some functionality of the product does not meet the criterion.

    Does Not Support: The majority of 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 in WCAG Level AAA criteria.