Accessibility

ACCESSIBILITY STATEMENT

www.misterimpex.com

Compliance Status

Mister Impex (hereinafter, also Website) is partially compliant with Royal Decree 1112/2018, of September 7, due to the non-conformity of the aspects indicated below.

Non-Accessible Content

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

a. Lack of compliance with RD 1112/2018: Not applicable. Meets 100% of web accessibility criteria.

  • Criterion 5 – General Requirements: Not applicable.
    • Non-compatible means may be required to activate some accessibility features [requirement number 5.2 Activation of accessibility features, from 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 number 6.1 Bandwidth for speech, from 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, from UNE-EN 301549:2022].
    • It may not be possible to provide a mode for simultaneous voice and text two-way communication [requirement number 6.2.1.2 Concurrent voice and text, from UNE-EN 301549:2022].
    • It may not clearly differentiate between sent text and received text in RTT communications [requirement number 6.2.2.1 Visually distinguishable display, from UNE-EN 301549:2022].
    • It may not be possible to programmatically determine the send and receive direction of RTT [requirement number 6.2.2.2 Programmatically determinable send and receive direction, from UNE-EN 301549:2022].
    • It may not be possible to provide speaker identification for RTT [requirement number 6.2.2.3 Speaker identification, from UNE-EN 301549:2022].
    • There may not be a visual indicator on screen of real-time audio activity [requirement number 6.2.2.4 Visual indicator of audio with real-time text, from UNE-EN 301549:2022].
    • It may not be possible to guarantee compatibility with other systems with RTT functionalities [requirement number 6.2.3 Interoperability, from UNE-EN 301549:2022].
    • It may not be possible to guarantee that RTT input is transmitted to the network within 500ms [requirement number 6.2.4 RTT responsiveness, from UNE-EN 301549:2022].
    • An alternative to voice may not be provided for performing assistance or interactive response tasks [requirement number 6.4 Alternatives to voice-based services, from UNE-EN 301549:2022].
    • It may not be possible to guarantee a minimum resolution of QVGA in video functionalities [requirement number 6.5.2 Resolution, from UNE-EN 301549:2022].
    • It may not be possible to guarantee a minimum video frequency of 20 FPS during communications [requirement number 6.5.3 Frame rate, from UNE-EN 301549:2022].
    • The maximum time of 100ms between the presentation of voice and video to the user may not be exceeded [requirement number 6.5.4 Audio and video synchronization, from UNE-EN 301549:2022].
    • There may not be a mode for speaker identification for sign language users in real-time [requirement number 6.5.6 Speaker identification with video communication, from UNE-EN 301549:2022].
  • Criterion 7 – Video Capability: Not applicable.
    • There may be some video players that do not have an operation mode to display existing subtitles [requirement number 7.1.1 Captioning playback, from UNE-EN 301549:2022].
    • There may be some video players that do not have an operation mode to synchronize audio with subtitles [requirement number 7.1.2 Captioning synchronization, from UNE-EN 301549:2022].
    • There may be some video players that do not have a subtitle saving system [requirement number 7.1.3 Preservation of captioning, from UNE-EN 301549:2022].
    • The user may not be able to adapt the characteristics of the subtitles to their individual requirements [requirement number 7.1.4 Captions characteristics, from UNE-EN 301549:2022].
    • An operation mode that provides spoken output of available subtitles may not be provided in all cases [requirement number 7.1.5 Spoken subtitles, from UNE-EN 301549:2022].
    • There may be some players that do not have a mode to select and play available audio descriptions [requirement number 7.2.1 Audio description playback, from UNE-EN 301549:2022].
    • There may be some players that do not have a mode to synchronize available audio descriptions [requirement number 7.2.2 Synchronization of audio description, from UNE-EN 301549:2022].
    • There may be some players that do not have a mode to save available audio descriptions [requirement number 7.2.3 Preservation of audio description, from UNE-EN 301549:2022].
    • Some pages incorporate a video player that does not provide controls for playing subtitles and audio description at the same level of interaction as the rest of the controls [requirement number 7.3 User controls for subtitles and audio description, from UNE-EN 301549:2022].
  • Criterion 9 – Requirements applicable to web pages: Not applicable.
    • There are non-text contents that lack a text alternative, or have an alternative that is not adequate [requirement number 9.1.1.1 Non-text content, from 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 (prerecorded), from UNE-EN 301549:2022].
    • Some recorded videos may not contain subtitles [requirement number 9.1.2.2 Captions (prerecorded), from 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, from 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 (prerecorded), from UNE-EN 301549:2022].
    • On some pages, the information, structure, and relationships are not determined by software or do not have a text alternative [requirement number 9.1.3.1 Info and relationships, from UNE-EN 301549:2022].
    • Some pages do not have at least one correct reading sequence defined by program [requirement number 9.1.3.2 Meaningful sequence, from UNE-EN 301549:2022].
    • Identification of elements only by sensory characteristics such as shape, color, size, visual location, orientation, or sound [requirement number 9.1.3.3 Sensory characteristics, from UNE-EN 301549:2022].
    • The content does not adapt when changing the screen orientation [requirement number 9.1.3.4 Orientation, from UNE-EN 301549:2022].
    • There are form elements in which the purpose of the input is not identified [requirement number 9.1.3.5 Identify input purpose, from 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, from 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, from 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), from UNE-EN 301549:2022].
    • There are errors on some pages related to text size and its ability to be customized when zooming [requirement number 9.1.4.4 Resize text, from UNE-EN 301549:2022].
    • There are pre-designed images based only on text [requirement number 9.1.4.5 Images of text, from UNE-EN 301549:2022].
    • There are errors when customizing font size, zoom level, or text spacing [requirement number 9.1.4.10 Reflow, from UNE-EN 301549:2022].
    • Insufficient contrast in interface components or graphical objects [requirement number 9.1.4.11 Non-text contrast, from UNE-EN 301549:2022].
    • There is text that is not displayed correctly when changing spacing and line heights [requirement number 9.1.4.12 Text spacing, from 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, from UNE-EN 301549:2022].
    • There are pages where keyboard navigation is not optimal and errors appear [requirement number 9.2.1.1 Keyboard, from UNE-EN 301549:2022].
    • There are components that, when receiving focus, prevent passing it to another using only the tab key or arrow keys [requirement number 9.2.1.2 No keyboard trap, from UNE-EN 301549:2022].
    • There are keyboard shortcuts that do not work [requirement number 9.2.1.4 Character key shortcuts, from UNE-EN 301549:2022].
    • There is a time limit set that cannot be stopped, adjusted, or extended [requirement number 9.2.2.1 Timing adjustable, from UNE-EN 301549:2022].
    • There may be some automatically moving information that lacks controls to pause, control, or hide [requirement number 9.2.2.2 Pause, Stop, Hide, from UNE-EN 301549:2022].
    • There may be elements that flash more than three times per second or above the general threshold [requirement number 9.2.3.1 Three Flashes or Below Threshold, from UNE-EN 301549:2022].
    • Some pages lack a mechanism to bypass blocks of content that are repeated across multiple pages [requirement number 9.2.4.1 Bypass Blocks, from UNE-EN 301549:2022].
    • Inadequate description of some web page titles [requirement number 9.2.4.2 Page Titled, from UNE-EN 301549:2022].
    • In some documents, sequential keyboard navigation might not have a consistent order [requirement number 9.2.4.3 Focus Order, from 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), from 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, from UNE-EN 301549:2022].
    • There are headings with repetitive and/or poorly descriptive text [requirement number 9.2.4.6 Headings and Labels, from UNE-EN 301549:2022].
    • The focus location is not always visible when navigating with the keyboard [requirement number 9.2.4.7 Focus Visible, from UNE-EN 301549:2022].
    • There are elements that use multipoint or path-based gestures that cannot be operated with just a pointer or without a path-based gesture [requirement number 9.2.5.1 Pointer Gestures, from UNE-EN 301549:2022].
    • There are pages where a mouse click event cannot be canceled [requirement number 9.2.5.2 Pointer Cancellation, from UNE-EN 301549:2022].
    • There are interface components that do not have visible labels [requirement number 9.2.5.3 Label in Name, from UNE-EN 301549:2022].
    • There is functionality that is only operable through movement [requirement number 9.2.5.4 Motion Actuation, from UNE-EN 301549:2022].
    • On some pages, the default language used is not indicated [requirement number 9.3.1.1 Language of Page, from UNE-EN 301549:2022].
    • There might be occasional editing and language identification errors in some parts of the web page [requirement number 9.3.1.2 Language of Parts, from UNE-EN 301549:2022].
    • There are components that initiate a change of context when they receive focus [requirement number 9.3.2.1 On Focus, from UNE-EN 301549:2022].
    • User interaction with some controls causes page changes without prior warning [requirement number 9.3.2.2 On Input, from 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, from UNE-EN 301549:2022].
    • Certain interactive elements are not consistently presented in all cases, as they are displayed with different visual styles [requirement number 9.3.2.4 Consistent Identification, from 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 suggestions in forms to fill in fields correctly [requirement number 9.3.3.1 Error Identification, from 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 field format [requirement number 9.3.3.2 Labels or Instructions, from UNE-EN 301549:2022].
    • There might be some input errors in fields/forms where the user is not notified of the suggestion to solve it [requirement number 9.3.3.3 Error Suggestion, from UNE-EN 301549:2022].
    • In data entry, errors are not detected and the user is not provided with an opportunity to correct them [requirement number 9.3.3.4 Error Prevention (Legal, Financial, Data), from UNE-EN 301549:2022].
    • There may be errors in the use of HTML tags and attributes and WAI-ARIA 1.1 [requirement number 9.4.1.1 Parsing, from 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, from 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, from UNE-EN 301549:2022].
    • Some of the WCAG 2.1 requirements are not met [requirement number 9.6 WCAG Conformance Requirements, from 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, from UNE-EN 301549:2022].
    • There may be no equivalent alternative for audio-only or video-only recorded content [requirement number 10.1.2.1 Audio-only and Video-only, from UNE-EN 301549:2022].
    • Videos may lack subtitles and audio descriptions [requirement number 10.1.2.2 Captions (Prerecorded), from UNE-EN 301549:2022].
    • There may be no alternative for time-based media or audio description for prerecorded video content in synchronized multimedia [requirement number 10.1.2.3 Audio Description or Media Alternative, from UNE-EN 301549:2022].
    • An audio description may not be provided for all prerecorded video content within synchronized multimedia [requirement number 10.1.2.5 Audio Description (Prerecorded), from UNE-EN 301549:2022].
    • In some documents, information, structure, and relationships are not programmatically determined or do not have a text alternative [requirement number 10.1.3.1 Info and Relationships, from UNE-EN 301549:2022].
    • Some documents do not have at least one programmatically determined correct reading sequence [requirement number 10.1.3.2 Meaningful Sequence, from 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, from UNE-EN 301549:2022].
    • There may be documents whose content does not adapt when changing the screen orientation [requirement number 10.1.3.4 Orientation, from UNE-EN 301549:2022].
    • In some forms, the input field that collects user information does not have an identified purpose [requirement number 10.1.3.5 Identify Input Purpose, from 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, from 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, from 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), from 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, the content may lose functionality or information when zooming in [requirement number 10.1.4.4 Resize Text, from 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, from UNE-EN 301549:2022].
    • In some documents, content may lose functionality or information when zooming in [requirement number 10.1.4.10 Reflow, from UNE-EN 301549:2022].
    • In some documents, the contrast of user interface components and graphical objects may not reach 3:1 with adjacent colors [requirement number 10.1.4.11 Non-text Contrast, from 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, from UNE-EN 301549:2022].
    • The content of some documents does not receive keyboard focus with which to perform any action [requirement number 10.1.4.13 Content on Hover or Focus, from UNE-EN 301549:2022].
    • There are documents that cannot be fully operated through the keyboard [requirement number 10.2.1.1 Keyboard, from 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, from UNE-EN 301549:2022].
    • In some documents, there are keyboard shortcuts that do not work [requirement number 10.2.1.4 Character Key Shortcuts, from UNE-EN 301549:2022].
    • In some documents, there is a time limit set that cannot be stopped, adjusted, or extended [requirement number 10.2.2.1 Timing Adjustable, from UNE-EN 301549:2022].
    • Some documents may contain automatically moving information that does not have controls to pause, control, or hide [requirement number 10.2.2.2 Pause, Stop, Hide, from UNE-EN 301549:2022].
    • Some documents may contain elements that flash more than three times per second or above the general threshold [requirement number 10.2.3.1 Three Flashes or Below Threshold, from UNE-EN 301549:2022].
    • There may be documents that do not have a title [requirement number 10.2.4.2 Page Titled, from UNE-EN 301549:2022].
    • In some documents, headers have not been defined and navigation by keyboard is not possible [requirement number 10.2.4.3 Focus Order, from UNE-EN 301549:2022].
    • Some documents may contain links that might not have a textually defined specific purpose [requirement number 10.2.4.4 Link Purpose (in context), from UNE-EN 301549:2022].
    • In some documents, there may be headers or control names that are not sufficiently descriptive of their purpose [requirement number 10.2.4.6 Headings and Labels, from UNE-EN 301549:2022].
    • The focus location is not always visible when navigating by keyboard through some documents [requirement number 10.2.4.7 Focus Visible, from UNE-EN 301549:2022].
    • In some documents, there may be elements that use multipoint or path-based gestures that cannot be operated with just one pointer or without a path-based gesture [requirement number 10.2.5.1 Pointer Gestures, from UNE-EN 301549:2022].
    • There are documents where an event cannot be canceled when clicking the mouse [requirement number 10.2.5.2 Pointer Cancellation, from UNE-EN 301549:2022].
    • There are documents that have some labels accompanying controls that do not have the same name [requirement number 10.2.5.3 Label in Name, from UNE-EN 301549:2022].
    • There are documents whose functionality is only operable through movement [requirement number 10.2.5.4 Motion Actuation, from UNE-EN 301549:2022].
    • There may be documents in which the main language is not identified [requirement number 10.3.1.1 Language of Page, from 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, from 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, from UNE-EN 301549:2022].
    • User interaction with some controls causes page changes without prior warning [requirement number 10.3.2.2 On Input, from 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, from UNE-EN 301549:2022].
    • In some forms within documents, an automatic context change could occur without warning the user [requirement number 10.3.3.2 Labels or Instructions, from UNE-EN 301549:2022].
    • In some documents, there might be an input error in a field/form that does not notify the user of a suggestion to solve it [requirement number 10.3.3.3 Error Suggestion, from UNE-EN 301549:2022].
    • In some documents, there may be forms for data collection or that involve legal or financial commitments that are not reversible, reviewable, or have confirmation before submitting [requirement number 10.3.3.4 Error Prevention (Legal, Financial, Data), from UNE-EN 301549:2022].
    • In some documents, there may be duplicate attributes and IDs [requirement number 10.4.1.1 Parsing, from 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, from UNE-EN 301549:2022].
    • In some documents, status messages might not be programmatically determined through functions or properties [requirement number 10.4.1.3 Status Messages, from UNE-EN 301549:2022].
  • Criterion 11 – Requirements applicable to software: Not applicable.
    • User’s visual preferences in the browser are not respected on the page [requirement number 11.7 User Preferences, from UNE-EN 301549:2022].
    • The information necessary for accessibility may not be compatible with the format used for the output of the authoring tool [requirement number 11.8.1 Content Technology, from UNE-EN 301549:2022].
    • There may not be a mechanism that allows for the creation of content in an accessible manner [requirement number 11.8.2 Accessible Content Creation, from UNE-EN 301549:2022].
    • There is no mechanism for preserving accessibility information during transformations [requirement number 11.8.3 Preservation of Accessibility Information in Transformations, from UNE-EN 301549:2022].
    • There may not be a repair mechanism for the accessibility checker [requirement number 11.8.4 Repair Service, from UNE-EN 301549:2022].
    • No template may be available that is compatible with content creation according 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.
    • The 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].
    • The product documentation may not be completely in accessible formats [requirement number 12.1.2 Accessible documentation, of UNE-EN 301549:2022].
    • Support services do not provide all information on accessibility features included in the 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].
    • There may be documentation provided by support services that is not in an accessible format [requirement number 12.2.4 Accessible documentation, of UNE-EN 301549:2022].

b. Disproportionate burden: Not applicable.

c. Content not within the scope of applicable legislation:

  • There may be office files in PDF and other formats published before September 20, 2018, that do not fully comply with all accessibility requirements. Although efforts have been made to ensure that most of them do comply.
  • There may be third-party content that is not developed in this Unit or 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 comply with all accessibility requirements.
  • Parts or the entire website may be created with a CMS (WordPress, Shopify, PrestaShop, etc.), so due to some updates or changes in the systems, not all generated or auto-generated content may comply with all accessibility regulations.

Preparation of this accessibility statement

This statement was prepared on 01/14/2025

The method used to prepare the statement was a self-assessment carried out by the company itself.

Last review of the statement: 01/14/2025

Observations and contact information

You can make communications about accessibility requirements (Article 10.2.a of Royal Decree 1112/2018, of September 7) such as:

  • Report any possible non-compliance by this website.
  • Communicate other difficulties in accessing the content.
  • Make any other query or suggestion for improvement regarding the accessibility of the website.

Through the following channels:

  • Email: info@misterimpex.com
  • Phone: +34 667 27 36 45

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

  • A complaint regarding compliance with the requirements of RD 1112/2018.
  • A request for accessible information regarding:
    • Content that is excluded from the scope of application of RD 1112/2018 as established by Article 3, paragraph 4.
    • Content that is exempt from compliance with accessibility requirements due to imposing a disproportionate burden.

In the Request for accessible information, the facts, reasons, and petition must be specified with all clarity, allowing 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 contents of this website.

Optional content

The currently visible version of this website is from 01/14/2025, and on that date, the review of the current accessibility level was carried out.

From that date, daily partial reviews of new or modified web content are carried out, both of the templates and the final published pages and documents, in order 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 in images.
  • Links provide details of 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 adapting 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 proper display in any resolution and device including desktop, tablets, or mobile (responsive design)
  • has been created using HTML5 as the markup language and CSS 3 style sheets for its design.

Additionally, continuous auditing and content review work is carried out to facilitate interpretation and improve navigation through the web portal.

This Accessibility Declaration document has been created using the free online web accessibility declaration template generator on 14/01/2025.

Phone

(+34) 667 273 645

Email

info@misterimpex.com

Designed by Okawa
Copyright © 2025