ACCESSIBILITY POLICY
Compliance status
Leasingfy – Specialised in Big Data for Business Intelligence, hereinafter also referred to as the “Website,” is partially compliant with Royal Decree 1112/2018 of 7 September, due to the non-compliance issues listed below.
Non-accessible content
The content listed below is not accessible for the following reasons:
a. Non-compliance with Royal Decree 1112/2018
Not applicable. It complies with 100% of the web accessibility criteria.
Criterion 5 — General requirements
Not applicable.
Compatible means may be required to activate certain accessibility features [requirement number 5.2 Activation of accessibility features, UNE-EN 301549:2022].
Criterion 6 — Two-way voice communication capability
Not applicable.
It may not be possible to guarantee a frequency range with an upper limit of at least 7000 Hz [requirement number 6.1 Voice bandwidth, UNE-EN 301549:2022].
It may not be possible to provide a two-way communication mode using RTT [requirement number 6.2.1.1 RTT communication, UNE-EN 301549:2022].
It may not be possible to provide a two-way voice and text communication mode simultaneously [requirement number 6.2.1.2 Simultaneous voice and text, UNE-EN 301549:2022].
It may not clearly distinguish sent text from received text in RTT communications [requirement number 6.2.2.1 Visually distinguishable display, UNE-EN 301549:2022].
It may not be possible to determine by software the sending and receiving direction of RTT [requirement number 6.2.2.2 Software-determinable sending and receiving direction, UNE-EN 301549:2022].
It may not be possible to provide speaker identification through RTT [requirement number 6.2.2.3 Speaker identification, UNE-EN 301549:2022].
There may be no on-screen visual indicator of real-time audio activity [requirement number 6.2.2.4 Visual audio indicator with real-time text, UNE-EN 301549:2022].
Compatibility with other systems with RTT functionality may not be guaranteed [requirement number 6.2.3 Interoperability, UNE-EN 301549:2022].
It may not be possible to guarantee that RTT input is transmitted to the network within 500 ms [requirement number 6.2.4 RTT responsiveness, UNE-EN 301549:2022].
An alternative to voice may not be provided for support or interactive response tasks [requirement number 6.4 Alternatives to voice-based services, UNE-EN 301549:2022].
A minimum QVGA resolution in video functionalities may not be guaranteed [requirement number 6.5.2 Resolution, UNE-EN 301549:2022].
A minimum video frame rate of 20 FPS during communications may not be guaranteed [requirement number 6.5.3 Frame rate, UNE-EN 301549:2022].
The maximum time of 100 ms between the presentation of voice and video to the user may not be met [requirement number 6.5.4 Audio and video synchronization, UNE-EN 301549:2022].
There may be no mode for speaker identification for real-time sign language users [requirement number 6.5.6 Speaker identification with video communication, UNE-EN 301549:2022].
Criterion 7 — Video capability
Not applicable.
There may be a video player that does not have an operating mode allowing existing subtitles to be displayed [requirement number 7.1.1 Subtitle playback, UNE-EN 301549:2022].
There may be a video player that does not have an operating mode allowing audio to be synchronized with subtitles [requirement number 7.1.2 Subtitle synchronization, UNE-EN 301549:2022].
There may be a video player that does not have a subtitle-saving system [requirement number 7.1.3 Preservation of subtitles, UNE-EN 301549:2022].
The user may not be able to adapt subtitle characteristics to their individual requirements [requirement number 7.1.4 Subtitle characteristics, UNE-EN 301549:2022].
In all cases, an operating mode that provides spoken output for available subtitles may not be provided [requirement number 7.1.5 Spoken subtitles, UNE-EN 301549:2022].
There may be a player that does not have a mode to select and play available audio descriptions [requirement number 7.2.1 Audio description playback, UNE-EN 301549:2022].
There may be a player that does not have a mode to synchronize available audio descriptions [requirement number 7.2.2 Audio description synchronization, UNE-EN 301549:2022].
There may be a player that does not have a mode to save available audio descriptions [requirement number 7.2.3 Preservation of audio description, UNE-EN 301549:2022].
Some pages include a video player that does not provide controls for subtitle and audio description playback at the same interaction level as the rest of the controls [requirement number 7.3 User controls for subtitles and audio description, UNE-EN 301549:2022].
Criterion 9 — Requirements applicable to web pages
Not applicable.
There is non-text content that lacks a text alternative, or that has an inadequate alternative [requirement number 9.1.1.1 Non-text content, UNE-EN 301549:2022].
Some recorded videos do not have text-based alternatives or audio alternatives [requirement number 9.1.2.1 Audio-only and video-only, UNE-EN 301549:2022].
Some recorded videos may not contain subtitles [requirement number 9.1.2.2 Subtitles, recorded, UNE-EN 301549:2022].
Some prerecorded videos on the website do not have audio description or alternative media [requirement number 9.1.2.3 Audio description or media alternative, UNE-EN 301549:2022].
Some prerecorded videos on the website do not have audio description or alternative media [requirement number 9.1.2.5 Audio description, recorded, UNE-EN 301549:2022].
On some pages, information, structure, and relationships are not software-determinable or do not have a text alternative [requirement number 9.1.3.1 Information and relationships, UNE-EN 301549:2022].
Some pages do not have at least one correct reading sequence programmatically defined [requirement number 9.1.3.2 Meaningful sequence, UNE-EN 301549:2022].
Elements are identified only by sensory characteristics such as shape, color, size, visual location, orientation, or sound [requirement number 9.1.3.3 Sensory characteristics, UNE-EN 301549:2022].
The content does not adapt when the screen orientation changes [requirement number 9.1.3.4 Orientation, UNE-EN 301549:2022].
There are form elements whose input purpose is not identified [requirement number 9.1.3.5 Identify input purpose, UNE-EN 301549:2022].
On some pages, color has been used as the only visual means to convey information, indicate an action, prompt a response, or distinguish a visual element [requirement number 9.1.4.1 Use of color, UNE-EN 301549:2022].
There are sound elements that play automatically and there is no mechanism to pause or stop them [requirement number 9.1.4.2 Audio control, UNE-EN 301549:2022].
On some pages, the contrast ratio in text may not be at least 4.5:1 [requirement number 9.1.4.3 Contrast, minimum, UNE-EN 301549:2022].
There are errors on some pages relating to text size and the possibility of customization when zooming [requirement number 9.1.4.4 Resize text, UNE-EN 301549:2022].
There are predefined images based only on text [requirement number 9.1.4.5 Images of text, UNE-EN 301549:2022].
There are errors when customizing font size, zoom level, or text spacing [requirement number 9.1.4.10 Reflow, UNE-EN 301549:2022].
There is insufficient contrast in interface components or graphic objects [requirement number 9.1.4.11 Non-text content contrast, UNE-EN 301549:2022].
There is text that is not displayed correctly when spacing and line heights are changed [requirement number 9.1.4.12 Text spacing, UNE-EN 301549:2022].
When an element receives pointer or keyboard focus, additional content is displayed that cannot be dismissed without moving the pointer or changing the mouse focus [requirement number 9.1.4.13 Content on hover or focus, UNE-EN 301549:2022].
There are pages where keyboard navigation is not optimal and errors appear [requirement number 9.2.1.1 Keyboard, UNE-EN 301549:2022].
There are components that, when receiving focus, prevent it from being moved to another component using only the tab key or arrow keys [requirement number 9.2.1.2 No keyboard trap, UNE-EN 301549:2022].
There are keyboard shortcuts that do not work [requirement number 9.2.1.4 Character key shortcuts, UNE-EN 301549:2022].
A time limit may be established that cannot be stopped, adjusted, or extended [requirement number 9.2.2.1 Adjustable timing, UNE-EN 301549:2022].
There may be automatically moving information without controls to pause, control, or hide it [requirement number 9.2.2.2 Pause, stop, hide, UNE-EN 301549:2022].
There may be elements that flash more than three times in one second or above the general threshold [requirement number 9.2.3.1 Three flashes or below threshold, UNE-EN 301549:2022].
On some pages, there is no mechanism to bypass blocks of content that are repeated across several pages [requirement number 9.2.4.1 Bypass blocks, UNE-EN 301549:2022].
Some web page titles are inadequately described [requirement number 9.2.4.2 Page titled, UNE-EN 301549:2022].
In some documents, sequential keyboard navigation may not follow a consistent order [requirement number 9.2.4.3 Focus order, UNE-EN 301549:2022].
The purpose of the portal’s links, headings, or labels may not always be sufficiently descriptive or consistent for all users [requirement number 9.2.4.4 Link purpose, in context, UNE-EN 301549:2022].
Links to related content pages or alternative navigation methods are not always provided [requirement number 9.2.4.5 Multiple ways, UNE-EN 301549:2022].
There are headings with repeated and/or insufficiently descriptive text [requirement number 9.2.4.6 Headings and labels, UNE-EN 301549:2022].
The focus location is not always visible when navigating with the keyboard [requirement number 9.2.4.7 Focus visible, UNE-EN 301549:2022].
There are elements using multipoint or path-based gestures that cannot be operated with a single pointer or without a path-based gesture [requirement number 9.2.5.1 Pointer gestures, UNE-EN 301549:2022].
There are pages where a mouse press event cannot be canceled [requirement number 9.2.5.2 Pointer cancellation, UNE-EN 301549:2022].
There are interface components that do not have visible labels [requirement number 9.2.5.3 Label in name, UNE-EN 301549:2022].
There is functionality that can only be operated through motion [requirement number 9.2.5.4 Motion actuation, UNE-EN 301549:2022].
On some pages, the default language used is not indicated [requirement number 9.3.1.1 Language of page, UNE-EN 301549:2022].
There may be occasional failures in editing and identifying the language in some parts of the web page [requirement number 9.3.1.2 Language of parts, UNE-EN 301549:2022].
There are components that, when receiving focus, initiate a change of context [requirement number 9.3.2.1 On focus, UNE-EN 301549:2022].
The user’s interaction with certain controls causes page changes without prior warning [requirement number 9.3.2.2 On input, UNE-EN 301549:2022].
There may be pages with inconsistent navigation due to different links with the same destination [requirement number 9.3.2.3 Consistent navigation, UNE-EN 301549:2022].
Certain interactive elements are not presented consistently in all cases, as they are displayed with different visual styles [requirement number 9.3.2.4 Consistent identification, UNE-EN 301549:2022].
There are error messages that are insufficiently descriptive, error messages that are not grouped into a single message, and a lack of suggestions in forms to help users complete fields correctly [requirement number 9.3.3.1 Error identification, UNE-EN 301549:2022].
There are forms with mandatory fields where the user is not informed of this, as well as fields lacking a textual example of the required format [requirement number 9.3.3.2 Labels or instructions, UNE-EN 301549:2022].
There may be an input error in a field/form where the user is not notified of a suggestion to resolve it [requirement number 9.3.3.3 Error suggestions, UNE-EN 301549:2022].
In data entry, errors are not detected and the user is not given an opportunity to correct them [requirement number 9.3.3.4 Error prevention, legal, financial, data, UNE-EN 301549:2022].
There may be errors in the use of HTML and WAI-ARIA 1.1 tags and attributes [requirement number 9.4.1.1 Parsing, UNE-EN 301549:2022].
On some pages, user interface components such as form elements, links, and script-generated components do not follow the structure recommended by accessibility guidelines [requirement number 9.4.1.2 Name, role, value, UNE-EN 301549:2022].
On some pages, status messages may not be programmatically determined through roles or properties [requirement number 9.4.1.3 Status messages, UNE-EN 301549:2022].
Some WCAG 2.1 requirements are not met [requirement number 9.6 WCAG conformance requirements, UNE-EN 301549:2022].
Criterion 10 — Requirements applicable to non-web documents
Not applicable.
There may be documents with images that do not have an adequate text alternative [requirement number 10.1.1.1 Non-text content, UNE-EN 301549:2022].
There may be no equivalent alternative for recorded audio-only or video-only content [requirement number 10.1.2.1 Audio-only and video-only, UNE-EN 301549:2022].
Videos may lack subtitles and audio descriptions [requirement number 10.1.2.2 Subtitles, recorded, UNE-EN 301549:2022].
There may be no alternative for time-based media or audio description for recorded video content in synchronized multimedia [requirement number 10.1.2.3 Audio description or media alternative, UNE-EN 301549:2022].
Audio description may not be provided for all recorded video content within synchronized multimedia content [requirement number 10.1.2.5 Audio description, recorded, UNE-EN 301549:2022].
In some documents, information, structure, and relationships are not software-determinable or do not have a text alternative [requirement number 10.1.3.1 Information and relationships, UNE-EN 301549:2022].
Some documents do not have at least one correct reading sequence programmatically defined [requirement number 10.1.3.2 Meaningful sequence, UNE-EN 301549:2022].
There may be documents for which there is no accessible alternative that allows the content to be operated and understood [requirement number 10.1.3.3 Sensory characteristics, UNE-EN 301549:2022].
There may be documents whose content does not adapt when the screen orientation changes [requirement number 10.1.3.4 Orientation, UNE-EN 301549:2022].
In some forms, the input field that collects information about the user does not have its purpose identified [requirement number 10.1.3.5 Identify input purpose, UNE-EN 301549:2022].
In some documents, color has been used as the only visual means to convey information, indicate an action, prompt a response, or distinguish a visual element [requirement number 10.1.4.1 Use of color, UNE-EN 301549:2022].
There are audio elements in some documents that play automatically and there is no mechanism to pause or stop them [requirement number 10.1.4.2 Audio control, UNE-EN 301549:2022].
In some documents, the contrast ratio in text may not be at least 4.5:1 [requirement number 10.1.4.3 Contrast, minimum, UNE-EN 301549:2022].
In some texts, the size cannot be increased up to 200 percent without loss of content or functionality, and in some documents content may lose functionality or information when enlarged [requirement number 10.1.4.4 Resize text, UNE-EN 301549:2022].
In some documents, images of text may have been used instead of text to convey information [requirement number 10.1.4.5 Images of text, UNE-EN 301549:2022].
In some documents, content may lose functionality or information when enlarged [requirement number 10.1.4.10 Reflow, UNE-EN 301549:2022].
In some documents, the contrast of user interface components and graphic objects may not reach 3:1 against adjacent colors [requirement number 10.1.4.11 Non-text content contrast, UNE-EN 301549:2022].
In some texts, it is not possible to override the specified text spacing [requirement number 10.1.4.12 Text spacing, UNE-EN 301549:2022].
The content of some documents does not receive keyboard focus with which any action can be performed [requirement number 10.1.4.13 Content on hover or focus, UNE-EN 301549:2022].
There are documents that cannot be fully operated using the keyboard [requirement number 10.2.1.1 Keyboard, UNE-EN 301549:2022].
In some documents, headings have not been defined and keyboard navigation is not possible [requirement number 10.2.1.2 No keyboard trap, UNE-EN 301549:2022].
In some documents, there are keyboard shortcuts that do not work [requirement number 10.2.1.4 Character key shortcuts, UNE-EN 301549:2022].
In some documents, a time limit is established that cannot be stopped, adjusted, or extended [requirement number 10.2.2.1 Adjustable timing, UNE-EN 301549:2022].
Some documents may contain automatically moving information that lacks controls to pause, control, or hide it [requirement number 10.2.2.2 Pause, stop, hide, UNE-EN 301549:2022].
Some documents may contain elements that flash more than three times in one second or above the general threshold [requirement number 10.2.3.1 Three flashes or below threshold, UNE-EN 301549:2022].
There may be documents that do not have a title [requirement number 10.2.4.2 Page titled, UNE-EN 301549:2022].
In some documents, headings have not been defined and keyboard navigation is not possible [requirement number 10.2.4.3 Focus order, UNE-EN 301549:2022].
Some documents may contain links whose specific purpose may not be textually defined [requirement number 10.2.4.4 Link purpose, in context, UNE-EN 301549:2022].
In some documents, there may be headings or control names that are not sufficiently descriptive of their purpose [requirement number 10.2.4.6 Headings and labels, UNE-EN 301549:2022].
The focus location is not always visible when navigating some documents with the keyboard [requirement number 10.2.4.7 Focus visible, UNE-EN 301549:2022].
In some documents, there may be elements using multipoint or path-based gestures that cannot be operated with a single pointer or without a path-based gesture [requirement number 10.2.5.1 Pointer gestures, UNE-EN 301549:2022].
There are documents where a mouse press event cannot be canceled [requirement number 10.2.5.2 Pointer cancellation, UNE-EN 301549:2022].
There are documents with labels accompanying controls that do not have the same name [requirement number 10.2.5.3 Label in name, UNE-EN 301549:2022].
There are documents whose functionality can only be operated through motion [requirement number 10.2.5.4 Motion actuation, UNE-EN 301549:2022].
There may be documents where the main language is not identified [requirement number 10.3.1.1 Language of page, UNE-EN 301549:2022].
There may be content or phrases within some documents whose language cannot be programmatically determined [requirement number 10.3.2.1 Language of parts, UNE-EN 301549:2022].
There may be components in some documents that, when receiving focus, initiate a change of context [requirement number 10.3.2.1 On focus, UNE-EN 301549:2022].
The user’s interaction with certain controls causes page changes without prior warning [requirement number 10.3.2.2 On input, UNE-EN 301549:2022].
There are data input fields with automatic error detection capability that do not identify where or how the error occurs [requirement number 10.3.3.1 Error identification, UNE-EN 301549:2022].
In some forms within some documents, an automatic change of context may occur without warning the user [requirement number 10.3.3.2 Labels or instructions, UNE-EN 301549:2022].
There may be an input error in a field/form in some documents where the user is not notified of a suggestion to resolve it [requirement number 10.3.3.3 Error suggestions, UNE-EN 301549:2022].
In some documents, there may be a form for collecting data or committing the user legally or financially that is not reversible, reviewable, or confirmed before submission [requirement number 10.3.3.4 Error prevention, legal, financial, data, UNE-EN 301549:2022].
In some documents, there may be duplicate attributes and IDs [requirement number 10.4.1.1 Parsing, UNE-EN 301549:2022].
In some documents, user interface components such as form elements, links, and script-generated components do not follow the structure recommended by accessibility guidelines [requirement number 10.4.1.2 Name, role, value, UNE-EN 301549:2022].
In some documents, status messages may not be programmatically determined through roles or properties [requirement number 10.4.1.3 Status messages, UNE-EN 301549:2022].
Criterion 11 — Requirements applicable to software
Not applicable.
The browser’s user visual preferences are not respected on the page [requirement number 11.7 User preferences, UNE-EN 301549:2022].
The information required for accessibility may not be compatible with the format used for the output of the authoring tool [requirement number 11.8.1 Content management technology, UNE-EN 301549:2022].
There may be no mechanism that allows content to be created in an accessible manner [requirement number 11.8.2 Creation of accessible content, UNE-EN 301549:2022].
There is no mechanism for preserving accessibility information during transformations [requirement number 11.8.3 Preservation of accessibility information during transformations, UNE-EN 301549:2022].
There may be no accessibility checker repair mechanism [requirement number 11.8.4 Repair service, UNE-EN 301549:2022].
No template may be available that is compatible with the creation of content compliant with the requirements of Chapters 9, Web, or 10, Non-web documents [requirement number 11.8.5 Templates, UNE-EN 301549:2022].
Criterion 12 — Requirements applicable to documentation and support services
Not applicable.
The product documentation does not list or explain all available accessibility features [requirement number 12.1.1 Accessibility and compatibility features, UNE-EN 301549:2022].
The product documentation may not be fully in accessible formats [requirement number 12.1.2 Accessible documentation, UNE-EN 301549:2022].
Support services do not provide all information regarding the accessibility features included in the product documentation [requirement number 12.2.2 Information on accessibility and compatibility features, UNE-EN 301549:2022].
Support services cannot always be adapted to the communication needs of users with disabilities [requirement number 12.2.3 Effective communication, UNE-EN 301549:2022].
Documentation supplied by support services may not be in an accessible format [requirement number 12.2.4 Accessible documentation, UNE-EN 301549:2022].
b. Disproportionate burden
Not applicable.
c. Content outside the scope of the applicable legislation
There may be office files in PDF and other formats published before 20 September 2018 that do not fully comply with all accessibility requirements. However, efforts have been made to ensure that most of them do comply.
There may be third-party content that has not been developed by this Unit or is not under its control, such as images, interactive maps, videos, documents, players, etc.
There may be prerecorded files published before 20 September 2018 that do not fully comply with all accessibility requirements.
Parts of the website, or the entire website, may have been created with a CMS, such as WordPress, Shopify, PrestaShop, etc. Therefore, due to an update or change in the systems, some generated or automatically generated content may not comply with all accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 03/06/2026.
The method used to prepare the statement was a self-assessment carried out by the company itself.
Last review of the statement: 03/06/2026.
Comments and contact details
You may submit communications regarding accessibility requirements, Article 10.2.a of Royal Decree 1112/2018 of 7 September, such as:
Reporting any possible non-compliance by this website.
Reporting other difficulties in accessing content.
Submitting any other query or suggestion for improvement regarding the accessibility of the website.
Through the following channels:
Email: info@leasingfy.info
Telephone: –
In accordance with Article 10.2.b of Royal Decree 1112/2018, you may also submit:
A complaint regarding compliance with the requirements of Royal Decree 1112/2018.
A request for accessible information relating to:
Content excluded from the scope of application of Royal Decree 1112/2018 pursuant to Article 3, section 4.
Content exempt from compliance with accessibility requirements because it imposes a disproportionate burden.
In the request for accessible information, the facts, reasons, and request must be stated clearly enough to verify that it is a reasonable and legitimate request.
Communications will be received and processed by the company’s management, as the unit responsible for the content of this website.
Optional content
The currently visible version of this website is dated 03/06/2026, and on that date the current accessibility level was reviewed.
From that date onward, partial daily reviews are carried out on new or modified web content, including templates, pages, and final published documents, in order to ensure compliance with the accessibility requirements of Standard UNE-EN 301549:2022, taking into account the exceptions under Royal Decree 1112/2018 of 7 September.
Among others, the following measures are adopted to facilitate accessibility:
Use of alternative text in images.
Links provide details about the function or destination of the hyperlink.
Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.
Compatibility
The website:
Has been designed in accordance with current accessibility standards and regulations, complying with priority 2, AA, checkpoints defined in the Web Content Accessibility Guidelines, WCAG 2.1.
Is optimized for the latest current versions of Chrome, Edge, Firefox, Safari, and Opera.
Is designed for proper display on any resolution and desktop, tablet, or mobile device, using responsive design.
Has been developed using HTML5 as the markup language and CSS 3 style sheets for its design.
In addition, continuous auditing and content review work is carried out to facilitate interpretation and improve navigation through the web portal.
