luzvacacional.com
Compliance status
Horizonte Luz, S.L. (hereinafter also referred to as the Website) is partially compliant with Royal Decree 1112/2018 of 7 September, due to the instances of non-compliance set out below.
Non-accessible content
The content listed below is not accessible for the following reasons:
<strong>a. Non-compliance with Royal Decree 1112/2018:</strong> Not applicable. It complies with 100% of web accessibility criteria.
- Criterion 5 – General requirements: Not applicable.
- Some accessibility features may require unsupported means in order to be activated [requirement 5.2 Activation of accessibility features, of 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 7000Hz [requirement 6.1 Bandwidth for speech, of UNE-EN 301549:2022].
- It may not be possible to provide a two-way communication mode using RTT [requirement 6.2.1.1 Communication by RTT, of UNE-EN 301549:2022].
- It may not be possible to provide a two-way communication mode using voice and text simultaneously [requirement 6.2.1.2 Simultaneous voice and text, of UNE-EN 301549:2022].
- It may not display sent text and received text in a clearly distinguishable way in RTT communications [requirement 6.2.2.1 Visually distinguishable on-screen presentation, of UNE-EN 301549:2022].
- It may not be possible for software to determine the direction of RTT sending and receiving [requirement 6.2.2.2 Direction of sending and receiving determinable by software, of UNE-EN 301549:2022].
- It may not be possible to provide speaker identification for RTT [requirement 6.2.2.3 Speaker identification, of UNE-EN 301549:2022].
- There may not be an on-screen visual indicator of real-time audio activity [requirement 6.2.2.4 Visual indicator of audio with real-time text, of UNE-EN 301549:2022].
- It may not be possible to guarantee compatibility with other systems featuring RTT functionality [requirement 6.2.3 Interoperability, of UNE-EN 301549:2022].
- It may not be possible to guarantee that RTT input is transmitted to the network within 500ms [requirement 6.2.4 RTT responsiveness, of UNE-EN 301549:2022].
- A voice alternative for carrying out assistance or interactive response tasks may not be provided [requirement 6.4 Alternatives to voice-based services, of UNE-EN 301549:2022].
- It may not be possible to guarantee a minimum QVGA resolution in video functionalities [requirement 6.5.2 Resolution, of UNE-EN 301549:2022].
- It may not be possible to guarantee a minimum video frame rate of 20 FPS during communications [requirement 6.5.3 Frame rate, of UNE-EN 301549:2022].
- The maximum time of 100ms between the presentation of voice and video to the user may not be met [requirement 6.5.4 Audio and video synchronisation, of UNE-EN 301549:2022].
- There may not be a mode for speaker identification for real-time sign language users [requirement 6.5.6 Speaker identification with video communication, of UNE-EN 301549:2022].
- Criterion 7 – Video capability: Not applicable.
- There may be a video player that does not provide an operating mode allowing existing subtitles to be displayed [requirement 7.1.1 Subtitle playback, of UNE-EN 301549:2022].
- There may be a video player that does not provide an operating mode allowing audio to be synchronised with subtitles [requirement 7.1.2 Subtitle synchronisation, of UNE-EN 301549:2022].
- There may be a video player that does not include a system for preserving subtitles [requirement 7.1.3 Preservation of captioning, of UNE-EN 301549:2022].
- It may not be possible for the user to adapt subtitle features to their individual requirements [requirement 7.1.4 Subtitle characteristics, of UNE-EN 301549:2022].
- An operating mode that enables spoken output of available subtitles may not be provided in all cases [requirement 7.1.5 Spoken subtitles, of UNE-EN 301549:2022].
- There may be a player that does not provide a mode for selecting and playing available audio descriptions [requirement 7.2.1 Audio description playback, of UNE-EN 301549:2022].
- There may be a player that does not provide a mode for synchronising available audio descriptions [requirement 7.2.2 Audio description synchronisation, of UNE-EN 301549:2022].
- There may be a player that does not provide a mode for saving available audio descriptions [requirement 7.2.3 Preservation of audio description, of UNE-EN 301549:2022].
- Some pages include a video player that does not provide controls for subtitle and audio description playback at the same level of interaction as the other controls [requirement 7.3 User controls for subtitles and audio description, of UNE-EN 301549:2022].
- Criterion 9 – Requirements applicable to web pages: Not applicable.
- There is non-text content that lacks a text alternative, or has an alternative that is not appropriate [requirement 9.1.1.1 Non-text content, of UNE-EN 301549:2022].
- Some recorded videos do not provide text-based alternatives or an audio alternative [requirement 9.1.2.1 Audio-only and video-only, of UNE-EN 301549:2022].
- Some recorded videos may not include subtitles [requirement 9.1.2.2 Captions (pre-recorded), of UNE-EN 301549:2022].
- Some pre-recorded videos on the website do not provide audio description or alternative media [requirement 9.1.2.3 Audio description or media alternative, of UNE-EN 301549:2022].
- Some pre-recorded videos on the website do not provide audio description or alternative media [requirement 9.1.2.5 Audio description (pre-recorded), of UNE-EN 301549:2022].
- On some pages, information, structure and relationships are not programmatically determined or do not have a text alternative [requirement 9.1.3.1 Information and relationships, of UNE-EN 301549:2022].
- At least one correct reading sequence is not programmatically defined on some page [requirement 9.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
- Some elements are identified only through sensory characteristics such as shape, colour, size, visual location, orientation or sound [requirement 9.1.3.3 Sensory characteristics, of UNE-EN 301549:2022].
- The content does not adapt when the screen orientation is changed [requirement 9.1.3.4 Orientation, of UNE-EN 301549:2022].
- There are form elements for which the purpose of the input is not identified [requirement 9.1.3.5 Identify input purpose, of UNE-EN 301549:2022].
- On some pages, colour has been used as the only visual means of conveying information, indicating an action, prompting a response or distinguishing a visual element [requirement 9.1.4.1 Use of colour, of UNE-EN 301549:2022].
- There are audio elements that play automatically and there is no mechanism to pause or stop them [requirement 9.1.4.2 Audio control, of UNE-EN 301549:2022].
- On some pages, the contrast ratio for text may not be at least 4.5:1 [requirement 9.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].
- There are errors on some pages relating to text size and its ability to be customised when zooming [requirement 9.1.4.4 Resize text, of UNE-EN 301549:2022].
- There are pre-designed images based solely on text [requirement 9.1.4.5 Images of text, of UNE-EN 301549:2022].
- There are errors when customising font size, zoom level or text spacing [requirement 9.1.4.10 Reflow, of UNE-EN 301549:2022].
- There is insufficient contrast in interface components or graphical objects [requirement 9.1.4.11 Non-text contrast, of UNE-EN 301549:2022].
- Some text is not displayed correctly when spacing and line height are changed [requirement 9.1.4.12 Text spacing, of UNE-EN 301549:2022].
- When an element receives pointer hover or keyboard focus, additional content is shown that cannot be dismissed without moving the pointer or changing mouse focus [requirement 9.1.4.13 Content on hover or focus, of UNE-EN 301549:2022].
- There are pages where keyboard navigation is not optimal and errors occur [requirement 9.2.1.1 Keyboard, of UNE-EN 301549:2022].
- There are components which, when they receive focus, prevent it from being moved elsewhere using only the Tab key or arrow keys [requirement 9.2.1.2 No keyboard trap, of UNE-EN 301549:2022].
- There are keyboard shortcuts that do not work [requirement 9.2.1.4 Character key shortcuts, of UNE-EN 301549:2022].
- There is a time limit in place that cannot be stopped, adjusted or extended [requirement 9.2.2.1 Timing adjustable, of UNE-EN 301549:2022].
- There may be automatically moving content that does not provide controls to pause, stop or hide it [requirement 9.2.2.2 Pause, stop, hide, of UNE-EN 301549:2022].
- There may be elements that flash more than three times in one second or above the general flash threshold [requirement 9.2.3.1 Three flashes or below threshold, of UNE-EN 301549:2022].
- On some pages, there is no mechanism for skipping blocks of content repeated across multiple pages [requirement 9.2.4.1 Bypass blocks, of UNE-EN 301549:2022].
- Some web page titles are described inadequately [requirement 9.2.4.2 Page titled, of UNE-EN 301549:2022].
- In some documents, sequential keyboard navigation may not follow a consistent order [requirement 9.2.4.3 Focus order, of UNE-EN 301549:2022].
- The purpose of links, headings or labels on the site may not always be sufficiently descriptive or consistent for all users [requirement 9.2.4.4 Link purpose (in context), of UNE-EN 301549:2022].
- Links to related content pages or alternative navigation methods are not always provided [requirement 9.2.4.5 Multiple ways, of UNE-EN 301549:2022].
- Some headings contain repeated and/or insufficiently descriptive text [requirement 9.2.4.6 Headings and labels, of UNE-EN 301549:2022].
- The focus indicator is not always visible when navigating by keyboard [requirement 9.2.4.7 Focus visible, of UNE-EN 301549:2022].
- There are elements that use multipoint or path-based gestures which cannot be operated with a single pointer or without a path-based gesture [requirement 9.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
- There are pages where an event cannot be cancelled when clicking with the mouse [requirement 9.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].
- There are interface components that do not have visible labels [requirement 9.2.5.3 Label in name, of UNE-EN 301549:2022].
- There is functionality that can only be operated by motion [requirement 9.2.5.4 Motion actuation, of UNE-EN 301549:2022].
- On some pages, the default language used is not indicated [requirement 9.3.1.1 Language of page, of UNE-EN 301549:2022].
- There may be occasional editing and language identification errors in parts of the website [requirement 9.3.1.2 Language of parts, of UNE-EN 301549:2022].
- There are components that, when they receive focus, trigger a change of context [requirement 9.3.2.1 On focus, of UNE-EN 301549:2022].
- User interaction with certain controls causes page changes without prior warning [requirement 9.3.2.2 On input, of UNE-EN 301549:2022].
- There may be pages with inconsistent navigation due to different links leading to the same destination [requirement 9.3.2.3 Consistent navigation, of UNE-EN 301549:2022].
- There may be pages with inconsistent navigation due to different links leading to the same destination [requirement 9.3.2.3 Consistent navigation, of UNE-EN 301549:2022].
- There are error messages that are not sufficiently descriptive, or error messages that are not grouped into a single message, as well as a lack of suggestions in forms for completing fields correctly [requirement 9.3.3.1 Error identification, of UNE-EN 301549:2022].
- There are forms with required fields where the user is not informed of this, as well as fields where a textual example of the required format is missing [requirement 9.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
- There may be an input error in a field or form for which the user is not notified of a suggestion to correct it [requirement 9.3.3.3 Error suggestion 333, of UNE-EN 301549:2022].
- In data entry, errors are not detected and the user is not given an opportunity to correct them [requirement 9.3.3.4 Error prevention (legal, financial, data), of UNE-EN 301549:2022].
- There may be errors in the use of HTML and WAI-ARIA 1.1 tags and attributes [requirement 9.4.1.1 Parsing, of 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 the accessibility guidelines [requirement 9.4.1.2 Name, role, value, of UNE-EN 301549:2022].
- On some pages, status messages may not be programmatically determined through roles or properties [requirement 9.4.1.3 Status messages, of UNE-EN 301549:2022].
- Some WCAG 2.1 requirements are not met [requirement 9.6 WCAG conformance requirements, of UNE-EN 301549:2022].
- Criterion 10 – Requirements applicable to non-web documents: Not applicable.
- There may be documents containing images that do not have an appropriate text alternative [requirement 10.1.1.1 Non-text content, of UNE-EN 301549:2022].
- There may be no equivalent alternative for audio-only or pre-recorded video-only content [requirement 10.1.2.1 Audio-only and video-only, of UNE-EN 301549:2022].
- Videos may lack captions and audio descriptions [requirement 10.1.2.2 Captions (pre-recorded), of UNE-EN 301549:2022].
- There may be no alternative for time-based media or audio description for pre-recorded video content in synchronised media [requirement 10.1.2.3 Audio description or media alternative, of UNE-EN 301549:2022].
- Audio description may not be provided for all pre-recorded video content within synchronised media [requirement 10.1.2.5 Audio description (pre-recorded), of UNE-EN 301549:2022].
- In some documents, information, structure and relationships are not programmatically determined or do not have a text alternative [requirement 10.1.3.1 Information and relationships, of UNE-EN 301549:2022].
- Some documents do not have at least one correct reading sequence programmatically defined [requirement 10.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
- There may be documents for which no other accessible alternative exists to operate and understand the content [requirement 10.1.3.3 Sensory characteristics, of UNE-EN 301549:2022].
- There may be documents whose content does not adapt when the screen orientation is changed [requirement 10.1.3.4 Orientation, of UNE-EN 301549:2022].
- In some forms, the input field collecting user information does not have its purpose identified [requirement 10.1.3.5 Identify input purpose, of UNE-EN 301549:2022].
- In some documents, colour has been used as the only visual means of conveying information, indicating an action, prompting a response or distinguishing a visual element [requirement 10.1.4.1 Use of colour, of 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 10.1.4.2 Audio control, of UNE-EN 301549:2022].
- In some documents, the contrast ratio for text may not be at least 4.5:1 [requirement 10.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].
- In some texts, size cannot be increased up to 200 per cent without loss of content or functionality, and in some documents content may lose functionality or information when enlarged [requirement 10.1.4.4 Resize text, of UNE-EN 301549:2022].
- In some documents, images of text may have been used instead of text to convey information [requirement 10.1.4.5 Images of text, of UNE-EN 301549:2022].
- In some documents, content may lose functionality or information when enlarged [requirement 10.1.4.10 Reflow, of UNE-EN 301549:2022].
- In some documents, the contrast of user interface components and graphical objects may not reach 3:1 against adjacent colours [requirement 10.1.4.11 Non-text contrast, of UNE-EN 301549:2022].
- In some texts, it is not possible to override the specified text spacing [requirement 10.1.4.12 Text spacing, of UNE-EN 301549:2022].
- The content of some documents does not receive keyboard focus that would allow any action to be carried out [requirement 10.1.4.13 Content on hover or focus, of UNE-EN 301549:2022].
- There are documents that cannot be fully operated through the keyboard [requirement 10.2.1.1 Keyboard, of UNE-EN 301549:2022].
- In some documents, headings have not been defined and keyboard navigation is not possible [requirement 10.2.1.2 No keyboard trap, of UNE-EN 301549:2022].
- Some documents contain keyboard shortcuts that do not work [requirement 10.2.1.4 Character key shortcuts, of UNE-EN 301549:2022].
- In some documents, there is a time limit in place that cannot be stopped, adjusted or extended [requirement 10.2.2.1 Timing adjustable, of UNE-EN 301549:2022].
- Some documents may contain automatically moving content without controls to pause, stop or hide it [requirement 10.2.2.2 Pause, stop, hide, of UNE-EN 301549:2022].
- Some documents may contain elements that flash more than three times in one second or above the general flash threshold [requirement 10.2.3.1 Three flashes or below threshold, of UNE-EN 301549:2022].
- There may be documents without a title [requirement 10.2.4.2 Page titled, of UNE-EN 301549:2022].
- In some documents, headings have not been defined and keyboard navigation is not possible [requirement 10.2.4.3 Focus order, of UNE-EN 301549:2022].
- Some documents may contain links whose specific purpose is not textually defined [requirement 10.2.4.4 Link purpose (in context), of UNE-EN 301549:2022].
- In some documents, there may be a heading or control name that is not sufficiently descriptive of its purpose [requirement 10.2.4.6 Headings and labels, of UNE-EN 301549:2022].
- The focus indicator is not always visible when navigating by keyboard through some documents [requirement 10.2.4.7 Focus visible, of UNE-EN 301549:2022].
- Some documents may contain elements that use multipoint or path-based gestures which cannot be operated with a single pointer or without a path-based gesture [requirement 10.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
- There are documents where an event cannot be cancelled when clicking with the mouse [requirement 10.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].
- There are documents in which some labels accompanying controls do not have the same name [requirement 10.2.5.3 Label in name, of UNE-EN 301549:2022].
- There are documents whose functionality can only be operated by motion [requirement 10.2.5.4 Motion actuation, of UNE-EN 301549:2022].
- There may be documents in which the main language is not identified [requirement 10.3.1.1 Language of page, of UNE-EN 301549:2022].
- There may be content or phrases within some documents whose language cannot be programmatically determined [requirement 10.3.2.1 Language of parts, of UNE-EN 301549:2022].
- There may be components in some documents that, when they receive focus, trigger a change of context [requirement 10.3.2.1 On focus, of UNE-EN 301549:2022].
- User interaction with certain controls causes page changes without prior warning [requirement 10.3.2.2 On input, of UNE-EN 301549:2022].
- There are data entry fields with automatic error detection that do not identify where or how the error occurs [requirement 10.3.3.1 Error identification, of UNE-EN 301549:2022].
- In some forms within certain documents, an automatic change of context may occur without warning the user [requirement 10.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
- In some documents, there may be an input error in a field or form for which the user is not given a suggestion on how to correct it [requirement 10.3.3.3 Error suggestion, of UNE-EN 301549:2022].
- In some documents, there may be forms for data collection or forms with legal or financial implications that are not reversible, reviewable or confirmed before submission [requirement 10.3.3.4 Error prevention (legal, financial, data), of UNE-EN 301549:2022].
- In some documents, there may be duplicate attributes and IDs [requirement 10.4.1.1 Parsing, of 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 the accessibility guidelines [requirement 10.4.1.2 Name, role, value, of UNE-EN 301549:2022].
- In some documents, status messages may not be programmatically determined through roles or properties [requirement 10.4.1.3 Status messages, of UNE-EN 301549:2022].
- Criterion 11 – Requirements applicable to software: Not applicable.
- The browser’s visual user preferences are not respected on the page [requirement 11.7 User preferences, of UNE-EN 301549:2022].
- The information necessary for accessibility may not be compatible with the format used for the authoring tool’s output [requirement 11.8.1 Content management technology, of UNE-EN 301549:2022].
- There may be no mechanism allowing content to be created in an accessible way [requirement 11.8.2 Accessible content creation, of UNE-EN 301549:2022].
- There is no mechanism for preserving accessibility information during transformations [requirement 11.8.3 Preservation of accessibility information in transformations, of UNE-EN 301549:2022].
- There may be no repair feature in the accessibility checker [requirement 11.8.4 Repair service, of UNE-EN 301549:2022].
- There may be no template available that supports the creation of content compliant with the requirements of Chapters 9 (Web) or 10 (Non-web documents) [requirement 11.8.5 Templates, of 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 12.1.1 Accessibility and compatibility features, of UNE-EN 301549:2022].
- The product documentation may not be entirely available in accessible formats [requirement 12.1.2 Accessible documentation, of UNE-EN 301549:2022].
- Support services do not provide all the information on accessibility features included in the product documentation [requirement 12.2.2 Information on accessibility and compatibility features, of UNE-EN 301549:2022].
- Support services cannot always be adapted to the communication needs of users with disabilities [requirement 12.2.3 Effective communication, of UNE-EN 301549:2022].
- There may be documentation supplied by support services that is not in an accessible format [requirement 12.2.4 Accessible documentation, of 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 meet all accessibility requirements, although efforts have been made to ensure that most of them do.
- There may be third-party content not developed by or under the control of this organisation, such as images, interactive maps, videos, documents, players, and similar elements.
- There may be pre-recorded files published before 20 September 2018 that do not fully meet all accessibility requirements.
- Parts of, or the entirety of, the website may be created using a CMS (WordPress, Shopify, PrestaShop, etc.); therefore, due to updates or changes in these systems, not all generated or auto-generated content may fully comply with all accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 21/05/2026
The method used to prepare the statement was a self-assessment carried out by the company itself.
Last review of the statement: 21/05/2026
Comments and contact details
You may submit communications regarding accessibility requirements (Article 10.2.a of Royal Decree 1112/2018 of 7 September), for example:
- Reporting any possible non-compliance by this website.
- Notifying us of any other difficulties in accessing the content.
- Making any other enquiry or suggestion for improvement relating to the accessibility of the website.
Through the following channels:
- Email: info@luzvacacional.com
- Telephone: +34 638 46 25 22
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 Royal Decree 1112/2018, as established by 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 clearly specified in order to demonstrate that it is a reasonable and legitimate request.
Communications will be received and handled by the company’s management, as the unit responsible for the content of this website.
Optional content
The version of this website currently visible is dated 21/05/2026, and on that date a review of the accessibility level in force at that time was carried out.
From that date onwards, daily partial reviews are carried out on new or modified web content, including templates, pages and published final documents, in order to ensure compliance with the accessibility requirements of UNE-EN 301549:2022, taking into account the exceptions set out in Royal Decree 1112/2018 of 7 September.
Among other measures, the following have been adopted to improve accessibility:
- Use of alternative text for 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 specification (WCAG 2.1)
- is optimised for the latest current versions of Chrome, Edge, Firefox, Safari and Opera
- is designed for correct display on any resolution and on desktop, tablet and mobile devices (responsive design)
- has been developed using HTML5 as the markup language and CSS 3 style sheets for its design.
In addition, ongoing auditing and content review work is carried out to facilitate interpretation and improve navigation throughout the website.