Compliance Status

MAYTE LUENGO (hereinafter also referred to as the Website) is partially compliant with Royal Decree 1112/2018 of September 7, due to the non-compliance of the aspects indicated below.

Non-Accessible Content

The content listed below is non-accessible for the following reasons: a. Non-compliance with RD 1112/2018: Not applicable. It complies with 100% of the web accessibility criteria.

Criterion 5 – General Requirements: Not applicable. Non-compatible media may be required to activate some accessibility features [Requirement number 5.2 Activation of accessibility features, of UNE-EN 301549:2022].

Criterion 6 – Two-way voice communication capability: Not applicable.

• A frequency range whose upper limit is at least 7000Hz may not be guaranteed [Requirement number 6.1 Audio bandwidth for voice, of UNE-EN 301549:2022].

• A two-way communication mode using RTT may not be provided [Requirement number 6.2.1.1 RTT communication, of UNE-EN 301549:2022].

• A simultaneous two-way voice and text communication mode may not be provided [Requirement number 6.2.1.2 Simultaneous voice and text, of UNE-EN 301549:2022].

• Sent text may not be displayed in a clearly differentiated manner from received text in RTT communications [Requirement number 6.2.2.1 Visually distinguishable display, of UNE-EN 301549:2022].

• The direction of sending and receiving RTT may not be software-determinable [Requirement number 6.2.2.2 Programmatically determinable send and receive direction, of UNE-EN 301549:2022].

• Speaker identification via RTT may not be provided [Requirement number 6.2.2.3 Speaker identification, of UNE-EN 301549:2022].

• There may not be a visual indicator on the screen for real-time audio activity [Requirement number 6.2.2.4 Real-time text audio indicator, of UNE-EN 301549:2022].

• Interoperability with other systems featuring RTT functionalities may not be guaranteed [Requirement number 6.2.3 Interoperability, of UNE-EN 301549:2022].

• It may not be guaranteed that RTT input is transmitted to the network within 500ms [Requirement number 6.2.4 RTT responsiveness, of UNE-EN 301549:2022].

• An alternative to voice may not be provided for interactive assistance or response tasks [Requirement number 6.4 Alternatives to voice-based services, of UNE-EN 301549:2022].

• A minimum resolution of QVGA in video functionalities may not be guaranteed [Requirement number 6.5.2 Resolution, of 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, of UNE-EN 301549:2022].

• The maximum time of 100ms between the presentation of audio and video to the user may be exceeded [Requirement number 6.5.4 Audio to video synchronization, of UNE-EN 301549:2022].

• There may not be a real-time speaker identification mode for sign language users [Requirement number 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 lacks an operating mode allowing the display of available subtitles [Requirement number 7.1.1 Captioning playback, of UNE-EN 301549:2022].

• There may be a video player that lacks an operating mode allowing audio synchronization with subtitles [Requirement number 7.1.2 Captioning synchronization, of UNE-EN 301549:2022].

• There may be a video player that lacks a system to preserve captions [Requirement number 7.1.3 Captioning preservation, of UNE-EN 301549:2022].

• The user may not be able to adapt subtitle characteristics to their individual requirements [Requirement number 7.1.4 Captions characteristics, of UNE-EN 301549:2022].

• An operating mode providing a spoken output of available subtitles may not be provided in all cases [Requirement number 7.1.5 Spoken subtitles, of UNE-EN 301549:2022].

• There may be a player that lacks a mode to select and play available audio descriptions [Requirement number 7.2.1 Audio description playback, of UNE-EN 301549:2022].

• There may be a player that lacks a mode to synchronize available audio descriptions [Requirement number 7.2.2 Audio description synchronization, of UNE-EN 301549:2022].

• There may be a player that lacks a mode to save available audio descriptions [Requirement number 7.2.3 Audio description preservation, of UNE-EN 301549:2022].

• Some pages embed a video player that does not provide user controls for subtitles and audio description at the same level of interaction as other controls [Requirement number 7.3 User controls for captions and audio description, of UNE-EN 301549:2022].

Criterion 9 – Web-applicable Requirements: Not applicable.

• There is non-text content that lacks a text alternative, or has an inadequate alternative [Requirement number 9.1.1.1 Non-text content, of UNE-EN 301549:2022].

• Some recorded videos lack text-based alternatives or audio alternatives [Requirement number 9.1.2.1 Audio-only and video-only, of UNE-EN 301549:2022].

• Some recorded videos may not contain subtitles [Requirement number 9.1.2.2 Subtitles (recorded), of UNE-EN 301549:2022].

• Some pre-recorded videos on the website lack audio description or alternative media [Requirement number 9.1.2.3 Audio description or alternative media, of UNE-EN 301549:2022].

• Some pre-recorded videos on the website lack audio description [Requirement number 9.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].

• On some pages, information, structure, and relationships are not programmatically determined or lack a text alternative [Requirement number 9.1.3.1 Information and relationships, of 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, of UNE-EN 301549:2022].

• Elements are identified solely by sensory characteristics such as shape, color, size, visual location, orientation, or sound [Requirement number 9.1.3.3 Sensory characteristics, of UNE-EN 301549:2022].

• Content does not adapt when the screen orientation changes [Requirement number 9.1.3.4 Orientation, of UNE-EN 301549:2022].

• There are form elements in which the input purpose is not identified [Requirement number 9.1.3.5 Identify input purpose, of UNE-EN 301549:2022].

• On some pages, color has been used as the sole visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element [Requirement number 9.1.4.1 Use of color, of UNE-EN 301549:2022].

• There are sound elements that play automatically and lack a mechanism to pause or stop them [Requirement number 9.1.4.2 Audio control, of UNE-EN 301549:2022].

• On some pages, the text contrast ratio might not be at least 4.5:1 [Requirement number 9.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].

• There are errors on some pages related to text size and its customization capabilities when zooming [Requirement number 9.1.4.4 Resize text, of UNE-EN 301549:2022].

• There are pre-designed images based solely on text [Requirement number 9.1.4.5 Images of text, of UNE-EN 301549:2022].

• There are errors when customizing the font size, zoom level, or text spacing [Requirement number 9.1.4.10 Text reflow, of UNE-EN 301549:2022].

• Insufficient contrast in user interface components or graphical objects [Requirement number 9.1.4.11 Non-text contrast, of UNE-EN 301549:2022].

• There is text that does not display correctly when changing line heights and spaces [Requirement number 9.1.4.12 Text spacing, of UNE-EN 301549:2022].

• When an element receives pointer hover 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, of UNE-EN 301549:2022].

• There are pages where keyboard navigation is suboptimal and errors appear [Requirement number 9.2.1.1 Keyboard, of UNE-EN 301549:2022].

• There are components that, upon receiving focus, prevent moving it to another element using only the Tab key or arrow keys [Requirement number 9.2.1.2 No keyboard trap, of UNE-EN 301549:2022].

• There are keyboard shortcuts that do not work [Requirement number 9.2.1.4 Character key shortcuts, of UNE-EN 301549:2022].

• A time limit is set that cannot be stopped, adjusted, or extended [Requirement number 9.2.2.1 Timing adjustable, of UNE-EN 301549:2022].

• There may be automatically moving information that lacks controls to pause, stop, or hide [Requirement number 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 threshold [Requirement number 9.2.3.1 Three flashes or below threshold, of UNE-EN 301549:2022].

• On some pages, there is no mechanism to skip blocks of content that are repeated across multiple pages [Requirement number 9.2.4.1 Bypass blocks, of UNE-EN 301549:2022].

• Inadequate description of some web page titles [Requirement number 9.2.4.2 Page titled, of UNE-EN 301549:2022].

• In some documents, sequential keyboard navigation might not follow a consistent order [Requirement number 9.2.4.3 Focus order, of UNE-EN 301549:2022].

• The purpose of links, headings, or labels on the portal may not always be sufficiently descriptive or consistent for all users [Requirement number 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 offered [Requirement number 9.2.4.5 Multiple ways, of UNE-EN 301549:2022].

• There are headings with repeated and/or poorly descriptive text [Requirement number 9.2.4.6 Headings and labels, of UNE-EN 301549:2022].

• The focus location is not always visible when navigating via keyboard [Requirement number 9.2.4.7 Focus visible, of UNE-EN 301549:2022].

• There are elements that use 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, of UNE-EN 301549:2022].

• There are pages where an event cannot be canceled upon clicking the mouse [Requirement number 9.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].

• There are interface components that lack visible labels [Requirement number 9.2.5.3 Label in name, of UNE-EN 301549:2022].

• There is functionality that is only operable through motion [Requirement number 9.2.5.4 Motion actuation, of UNE-EN 301549:2022].

• On some pages, the default language used is not indicated [Requirement number 9.3.1.1 Language of page, of UNE-EN 301549:2022].

• There could be occasional editing and language identification flaws in some parts of the web page [Requirement number 9.3.1.2 Language of parts, of UNE-EN 301549:2022].

• There are components that, when receiving focus, trigger a change of context [Requirement number 9.3.2.1 On focus, of UNE-EN 301549:2022].

• User interaction with a control causes page changes without prior warning [Requirement number 9.3.2.2 On input, of UNE-EN 301549:2022].

• There may be pages with inconsistent navigation due to different links pointing to the same destination [Requirement number 9.3.2.3 Consistent navigation, of 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, of UNE-EN 301549:2022].

   

• There are poorly descriptive error messages, or error messages that are not grouped into a single message, as well as a lack of form suggestions to fill out fields correctly [Requirement number 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 lacking a textual example of the required format [Requirement number 9.3.3.2 Labels or instructions, of UNE-EN 301549:2022].

• There could be an input error in a field/form where the user is not notified of the suggestion to fix it [Requirement number 9.3.3.3 Error suggestion, of UNE-EN 301549:2022].

• Data entry does not detect errors, nor is the user provided with an opportunity to correct them [Requirement number 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 number 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 accessibility guidelines [Requirement number 9.4.1.2 Name, role, value, of UNE-EN 301549:2022].

• On some pages, status messages might not be programmatically determined through roles or properties [Requirement number 9.4.1.3 Status messages, of UNE-EN 301549:2022].

• Some WCAG 2.1 requirements are breached [Requirement number 9.6 WCAG conformance requirements, of UNE-EN 301549:2022].

Criterion 10 – Requirements applicable to non-web documents: Not applicable.

• There may be documents with images that lack an adequate text alternative [Requirement number 10.1.1.1 Non-text content, of 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, of UNE-EN 301549:2022].

• Videos may lack subtitles and audio descriptions [Requirement number 10.1.2.2 Subtitles (recorded), of UNE-EN 301549:2022].

• There may be no alternative for time-dependent media or an audio description for recorded video content in synchronized media [Requirement number 10.1.2.3 Audio description or alternative media, of UNE-EN 301549:2022].

• An audio description may not be provided for all recorded video content within synchronized multimedia [Requirement number 10.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].

• In some documents, information, structure, and relationships are not programmatically determined or lack a text alternative [Requirement number 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 number 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 number 10.1.3.3 Sensory characteristics, of 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, of UNE-EN 301549:2022].

• In some forms, the input field that collects user information does not have its purpose identified [Requirement number 10.1.3.5 Identify input purpose, of UNE-EN 301549:2022].

• In some documents, color has been used as the sole visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element [Requirement number 10.1.4.1 Use of color, of UNE-EN 301549:2022].

• There are audio elements in some documents that play automatically and lack a mechanism to pause or stop them [Requirement number 10.1.4.2 Audio control, of UNE-EN 301549:2022].

• In some documents, the text contrast ratio might not be at least 4.5:1 [Requirement number 10.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].

• In some texts, the size cannot be changed 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, of 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, of UNE-EN 301549:2022].

• In some documents, content may lose functionality or information when enlarged [Requirement number 10.1.4.10 Text reflow, of UNE-EN 301549:2022].

• In some documents, the contrast of user interface components and graphical objects might not reach 3:1 with adjacent colors [Requirement number 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 number 10.1.4.12 Text spacing, of UNE-EN 301549:2022].

• The content of some documents does not receive keyboard focus to perform any action [Requirement number 10.1.4.13 Content on hover or focus, of UNE-EN 301549:2022].

• There are documents that cannot be fully operated via keyboard [Requirement number 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 number 10.2.1.2 No keyboard trap, of UNE-EN 301549:2022].

• In some documents, there are keyboard shortcuts that do not work [Requirement number 10.2.1.4 Character key shortcuts, of UNE-EN 301549:2022].

• In some documents, a time limit is set that cannot be stopped, adjusted, or extended [Requirement number 10.2.2.1 Timing adjustable, of UNE-EN 301549:2022].

• Some documents may contain automatically moving information that lacks controls to pause, stop, or hide [Requirement number 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 threshold [Requirement number 10.2.3.1 Three flashes or below threshold, of UNE-EN 301549:2022].

• There may be documents that lack a title [Requirement number 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 number 10.2.4.3 Focus order, of UNE-EN 301549:2022].

• Some documents may contain links that might not have a specifically defined purpose in text [Requirement number 10.2.4.4 Link purpose (in context), of 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, of UNE-EN 301549:2022].

• The focus location is not always visible when navigating via keyboard through some documents [Requirement number 10.2.4.7 Focus visible, of UNE-EN 301549:2022].

• In some documents, there may be elements that use 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, of UNE-EN 301549:2022].

• There are documents where an event cannot be canceled upon clicking the mouse [Requirement number 10.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].

• There are documents that have labels accompanying controls that do not match the same name [Requirement number 10.2.5.3 Label in name, of UNE-EN 301549:2022].

• There are documents whose functionality is only operable through motion [Requirement number 10.2.5.4 Motion actuation, of UNE-EN 301549:2022].

• There may be documents in which the primary language is not identified [Requirement number 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 number 10.3.1.2 Language of parts, of UNE-EN 301549:2022].

• There may be components in some documents that, when receiving focus, trigger a change of context [Requirement number 10.3.2.1 On focus, of UNE-EN 301549:2022].

• User interaction with a control causes page changes without prior warning [Requirement number 10.3.2.2 On input, of UNE-EN 301549:2022].

• There are data entry fields with automatic error detection capabilities that do not identify where or how the error occurs [Requirement number 10.3.3.1 Error identification, of UNE-EN 301549:2022].

• In some forms within a document, an automatic context change could occur without warning the user [Requirement number 10.3.3.2 Labels or instructions, of UNE-EN 301549:2022].

• In some documents, there could be an input error in a field/form where the user is not notified of the suggestion to fix it [Requirement number 10.3.3.3 Error suggestion, of UNE-EN 301549:2022].

• In some documents, there may be forms for data collection or legal/financial commitments that are not reversible, reviewable, or do not require confirmation before submission [Requirement number 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 number 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 accessibility guidelines [Requirement number 10.4.1.2 Name, role, value, of UNE-EN 301549:2022].

• In some documents, status messages might not be programmatically determined through roles or properties [Requirement number 10.4.1.3 Status messages, of UNE-EN 301549:2022].

Criterion 11 – Requirements applicable to software: Not applicable.

• User visual preferences in the browser are not respected on the page [Requirement number 11.7 User preferences, of UNE-EN 301549:2022].

• Information required for accessibility may not be compatible with the format used for the authoring tool output [Requirement number 11.8.1 Content management technology, of UNE-EN 301549:2022].

• A mechanism allowing the creation of content in an accessible manner may not exist [Requirement number 11.8.2 Accessible content creation, of UNE-EN 301549:2022].

• There is no mechanism to preserve accessibility information during transformations [Requirement number 11.8.3 Preservation of accessibility information during transformations, of UNE-EN 301549:2022].

• An accessibility checker repair service may not be available [Requirement number 11.8.4 Repair service, of UNE-EN 301549:2022].

• No template may be available that supports content creation conforming to the requirements of Chapters 9 (Web) or 10 (Non-web documents) [Requirement number 11.8.5 Templates, of UNE-EN 301549:2022].

Criterion 12 – Requirements applicable to documentation and support services: Not applicable.

• Product documentation does not list or explain all available accessibility features [Requirement number 12.1.1 Accessibility and compatibility features, of UNE-EN 301549:2022].

• Product documentation may not be fully available in accessible formats [Requirement number 12.1.2 Accessible documentation, of UNE-EN 301549:2022].

• Support services do not provide all the information regarding accessibility features included in product documentation [Requirement number 12.2.2 Information on accessibility and compatibility features, of UNE-EN 301549:2022].

• Support services cannot always adapt to the communication needs of users with disabilities [Requirement number 12.2.3 Effective communication, of UNE-EN 301549:2022].

• Documentation provided by support services may not be in an accessible format [Requirement number 12.2.4 Accessible documentation, of UNE-EN 301549:2022].

b. Disproportionate burden: Not applicable. c. Content outside the scope of applicable legislation:

• There may be office automation files in PDF and other formats published before September 20, 2018, that do not fully meet all accessibility requirements, although efforts have been made to ensure most of them comply.

   

• There may be third-party content not developed by this Unit nor under its control, such as images, interactive maps, videos, documents, players, etc.

   

• There may be pre-recorded files published before September 20, 2018, that do not fully meet all accessibility requirements.

   

• Parts or the entirety of the website may be built using a CMS (WordPress, Shopify, PrestaShop, etc.); therefore, due to system updates or changes, not all generated or auto-generated content may fully comply with all accessibility regulations.

   

Preparation of This Accessibility Statement

This statement was prepared on 05/19/2026. The method used to prepare the statement was a self-assessment carried out by the company itself. Last review of the statement: 05/19/2026.

Comments and Contact Information

You may submit communications regarding accessibility requirements (Article 10.2.a of Royal Decree 1112/2018 of September 7) to, for example:

• Report any possible non-compliance by this website.

• Convey other content access difficulties.

• Make any other queries or suggestions for improvement regarding website accessibility.

Through the following channels:

• Email: Contact@mayteluengo.com

• Phone: According to Article 10.2.b of RD 1112/2018, you may also submit:

• A complaint regarding compliance with the requirements of RD 1112/2018.

• A request for accessible information relating to:

  • Content excluded from the scope of application of RD 1112/2018 as established by Article 3, paragraph 4.

  • Content exempt from compliance with accessibility requirements due to a disproportionate burden.

In the Request for Accessible Information, the facts, reasons, and request must be clearly specified to confirm that it is a reasonable and legitimate request. Communications will be received and processed by the company management, as the unit responsible for the content of this website.

Optional Content

The currently visible version of this website dates from 05/19/2026, and the review of the accessibility level active at that time was conducted on that date. From that date onward, partial daily reviews of new or modified web content are carried out—covering templates, pages, and final published documents—to ensure compliance with the accessibility requirements of the UNE-EN 301549:2022 Standard, considering the exceptions of Royal Decree 1112/2018 of September 7.

Among others, the following measures are adopted to facilitate accessibility:

• Use of alternative text for images.

• Links offer details regarding 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 to adapt to current standards and regulations regarding accessibility, complying with Priority 2 (AA) verification points defined in the Web Content Accessibility Guidelines (WCAG 2.1) specification.

• Is optimized for the latest current versions of Chrome, Edge, Firefox, Safari, and Opera.

• Is designed for correct display on any resolution and desktop, tablet, or mobile device (responsive design).

• Has been built using HTML5 as the markup language and CSS 3 style sheets for its design.

Additionally, ongoing auditing and content review work is performed to facilitate interpretation and improve navigation across the web portal.

This Accessibility Statement document was created using the online free web accessibility statement template generator on 05/19/2026.