Clikalia Accessibility

Clikalia is committed to making its website accessible in accordance with the Royal Decree 1112/2018, of 7 September, on the accessibility of public sector websites and mobile applications, which transposes Directive (EU) 2016/2102 of the European Parliament and of the Council.

This accessibility statement applies to the website: https://clikalia.es/

Compliance Status

Based on a self-assessment, this website is partially compliant with the UNE-EN 301 549:2022 standard (equivalent to WCAG 2.1 Level AA guidelines), due to the exceptions and instances of non-compliance listed below.

Inaccessible Content

The content listed below is not accessible for the following reasons:

a) Violation of Royal Decree 1112/2018

Lack of a mechanism to skip blocks of repetitive content (Criterion 2.4.1, WCAG 2.1 AA)

The pages do not include a “Skip to Main Content” link, which forces users navigating with a keyboard to cycle through all navigation elements each time a page loads.

Lack of complete focus management in modal windows (Criteria 2.1.2 and 2.4.3 of WCAG 2.1 AA)

Modal dialog components do not fully confine the keyboard focus (focus trap) within the active element, nor do they restore focus to the element that triggered the dialog when it is closed. This can cause the focus to escape to the underlying document or be lost for keyboard users and assistive technologies.

Lack of actively announced state regions (Criterion 4.1.3, WCAG 2.1 AA)

Dynamically generated status messages—including, but not limited to, action confirmations, filter results, or asynchronous error notifications—are not presented using `aria-live` regions; therefore, they are not automatically announced by screen readers unless the user moves focus to them.

Failure to respect the reduced motion preference (Criterion 2.3 of WCAG 2.1 and Technical Recommendation UNE-EN 301 549:2022 §11)

Interface transitions and animations—including the opening of modals, drop-down menus, side panels, and carousels—play unconditionally, without checking the user’s operating system preference (prefers-reduced-motion). This may pose a risk to users with photosensitive epilepsy, vestibular disorders, or other related conditions.

b) Non-compliance with Royal Decree 1112/2018

Some content on the website may not fully comply with certain accessibility requirements:

Images without adequate text alternatives: Some photographs of properties or visual elements may lack sufficiently descriptive 
alternative attributes (`alt`) to ensure they can be properly interpreted by assistive technologies.

Interactive location maps: Certain maps showing the location of properties may present difficulties when navigating via keyboard or with screen readers.

Insufficient contrast in forms: Some fields or elements of the contact form may have color contrast levels below the recommended standards, which could make them difficult to read for people with low vision.  

Possible isolated issues with the keyboard navigation order or the programmatic identification of certain interactive elements.

c) Disproportionate burden

Not applicable.

d) The content does not fall within the scope of applicable legislation

There may be office documents or third-party content published before September 20, 2018, that do not fully comply with accessibility requirements.

Preparation of this accessibility statement

The method used to prepare the statement was a technical self-assessment conducted by the development team, involving a static review of the source code, an analysis of the user interface component structure, and a comparison with the conformance criteria of the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, incorporated as a reference standard by UNE-EN 301 549:2022.

The evaluation covered the architecture of reusable components, the user flows of active web applications, and the configuration of the project’s development and quality control tools.

Aspects verified positively during the evaluation:

Presence of correctly implemented ARIA attributes in form components, buttons, drop-down menus, progress indicators, and alert components, in accordance with success criterion 4.1.2 (Name, Function, and Value).

Explicit association between labels and form controls using the for/htmlFor and aria-describedby attributes, in accordance with criterion 1.3.1 (Information and Relationships).

Declaration of the lang attribute with the value corresponding to the active language in the document’s root element, in accordance with criterion 3.1.1 (Language Page ).

Use of semantic HTML section and region elements (<main>, <nav>, <header>, <footer>) that enable navigation via landmarks using assistive technologies, in accordance with success criterion 1.3.1.

A distinct visible focus indicator for keyboard interaction, in accordance with sucess criterion 2.4.7 (Visible Focus).

Alternative text is required for all image components at the system architecture level.

Keyboard navigation support (Escape, Enter, Space, and arrow keys) in the interactive components of the user interface library.

Areas identified as needing improvement or requiring correction:

Implementation of a “Skip to Main Content” link in all applications.

Implementation of focus confinement and restoration in modal dialog components.

Incorporation of `aria-live` regions for displaying dynamic status messages.

Adapting animations and transitions to the operating system's preference for reduced motion.

Instrumental validation of compliance with the color contrast ratios established in  Success Criterion 1.4.3 (Minimum Contrast) using automated tools.

Comments and Contact Information

You may submit reports regarding accessibility requirements (Article 10.2.a of Royal Decree 1112/2018), such as:

• Report any potential non-compliance by this website.

• Report other difficulties accessing the content.

• Submit any other questions or suggestions for improvement regarding the website’s accessibility.

You may submit these communications via:

• The contact form available on the website https://clikalia.es/contacta-con-nosotros

• Customer service email: hola@clikalia.com

Requests for accessible information and complaints (Article 12 of Royal Decree 1112/2018) must include:

• Facts, reasons, and a request that demonstrate the request is reasonable and legitimate.

• The requester’s contact information for receiving the response.

Procedure for Filing a Request

If, after submitting a request for accessible information or a complaint, the request has been denied, you disagree with the decision made, or the response does not meet the requirements set forth in Article 12.5 of Royal Decree 1112/2018, the interested party may file a complaint.

Likewise, a complaint may be filed if twenty business days have elapsed without a response having been received.

The complaint may be filed through the mechanisms provided for in current legislation regarding the accessibility of public sector websites and mobile applications.

Optional Content

The website is reviewed periodically with the aim of progressively improving the accessibility of its content and features, ensuring an inclusive digital experience for all users.

Continuous improvement efforts include:

• Progressive review of text alternatives for images of properties.

• Optimization of keyboard navigation on maps and interactive elements.

• Improving color contrast and the readability of forms and controls.

• Periodic accessibility evaluations in accordance with WCAG 2.1 Level AA.