ACCESSIBILITY STATEMENT
www.fueltenerife.com

Compliance Status
Fuel Tenerife (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 not accessible for the following reasons:

  1. Non-compliance with RD 1112/2018: Not applicable. The website complies with 100% of web accessibility criteria.

Criterion 5 – General Requirements: Not applicable.
Certain non-compatible means 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.

  • It may not be possible to guarantee a frequency range with an upper limit of at least 7000Hz [requirement number 6.1 Bandwidth for voice, of UNE-EN 301549:2022].
  • A two-way communication mode via RTT may not be provided [requirement number 6.2.1.1 Communication via RTT, of UNE-EN 301549:2022].
  • A two-way communication mode for simultaneous voice and text may not be provided [requirement number 6.2.1.2 Simultaneous voice and text, of UNE-EN 301549:2022].
  • The text sent and the text received in RTT communications may not be visually distinguishable [requirement number 6.2.2.1 Visually differentiable on-screen presentation, of UNE-EN 301549:2022].
  • The direction of RTT sending and receiving may not be determinable by software [requirement number 6.2.2.2 Direction of sending and receiving determinable by software, 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].
  • A visual on-screen indicator of real-time audio activity may not be present [requirement number 6.2.2.4 Visual audio indicator with real-time text, of UNE-EN 301549:2022].
  • Compatibility with other systems with 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 Responsiveness of RTT, of 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, of 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, of 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, of UNE-EN 301549:2022].
  • It may not be ensured that the maximum time of 100ms between the presentation of voice and video to the user is exceeded [requirement number 6.5.4 Synchronization of audio and video, of UNE-EN 301549:2022].
  • There may not be a mode for speaker identification for users of sign language in real-time communication [requirement number 6.5.6 Speaker identification with video communication, of UNE-EN 301549:2022].

Criterion 7 – Video capability: Not applicable.

  • Some video players may not provide an operational mode that allows displaying existing subtitles [requirement number 7.1.1 Subtitle playback, of UNE-EN 301549:2022].
  • Some video players may not provide an operational mode that allows synchronizing audio with subtitles [requirement number 7.1.2 Subtitle synchronization, of UNE-EN 301549:2022].
  • Some video players may not have a system to save subtitles [requirement number 7.1.3 Subtitle preservation, of UNE-EN 301549:2022].
  • Users may not be able to adapt the characteristics of subtitles to their individual requirements [requirement number 7.1.4 Subtitle characteristics, of UNE-EN 301549:2022].
  • It may not always be possible to provide an operational mode that facilitates a spoken output of the available subtitles [requirement number 7.1.5 Spoken subtitles, of UNE-EN 301549:2022].
  • Some players may not have a mode to select and play available audio descriptions [requirement number 7.2.1 Audio description playback, of UNE-EN 301549:2022].
  • Some players may not have a mode to synchronize available audio descriptions [requirement number 7.2.2 Audio description synchronization, of UNE-EN 301549:2022].
  • Some players may not have a mode to save available audio descriptions [requirement number 7.2.3 Audio description preservation, of UNE-EN 301549:2022].
  • Some pages incorporate video players that do not provide controls for the playback of 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, of UNE-EN 301549:2022].

Criterion 9 – Requirements applicable to web pages: Not applicable.

  • Non-text content exists that lacks a textual alternative, or has an alternative that is not adequate [requirement number 9.1.1.1 Non-text content, of UNE-EN 301549:2022].
  • Some recorded videos lack text-based 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 do not have audio descriptions 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 do not have audio descriptions or alternative media [requirement number 9.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].
  • On some pages, information, structure, and relationships are not determined by software or do not have an alternative as text [requirement number 9.1.3.1 Information and relationships, of UNE-EN 301549:2022].
  • At least one correct reading sequence may not be programmatically determined on some pages [requirement number 9.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
  • Identification of elements relies solely on 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 is changed [requirement number 9.1.3.4 Orientation, of 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, of UNE-EN 301549:2022].
  • On some pages, color is 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 audio elements that play automatically, and no mechanism exists to pause or stop them [requirement number 9.1.4.2 Audio control, of 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), of UNE-EN 301549:2022].
  • There are errors on some pages related to text size and its customization when zooming [requirement number 9.1.4.4 Resize text, of UNE-EN 301549:2022].
  • There are decorative images based solely on text [requirement number 9.1.4.5 Images of text, of UNE-EN 301549:2022].
  • There are errors when customizing font size, zoom level, or text spacing [requirement number 9.1.4.10 Text spacing, of UNE-EN 301549:2022].
  • 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, when line spacing and heights are adjusted, does not display correctly [requirement number 9.1.4.12 Text Spacing, UNE-EN 301549:2022].
  • When an element receives the 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].
  • Some pages do not offer optimal keyboard navigation and errors occur [requirement number 9.2.1.1 Keyboard, UNE-EN 301549:2022].
  • There are components that, when focused, prevent navigation to another element using only the tab or arrow keys [requirement number 9.2.1.2 No Keyboard Trap, UNE-EN 301549:2022].
  • Some keyboard shortcuts do not work [requirement number 9.2.1.4 Character Key Shortcuts, UNE-EN 301549:2022].
  • There are time limitations in place that cannot be paused, adjusted, or extended [requirement number 9.2.2.1 Timing Adjustable, UNE-EN 301549:2022].
  • There may be automatically moving content that does not have controls to pause, stop, or hide it [requirement number 9.2.2.2 Pause, Stop, and Hide, UNE-EN 301549:2022].
  • Some elements may flash more than three times per second or exceed the general threshold [requirement number 9.2.3.1 Three Flashes or Below Threshold, UNE-EN 301549:2022].
  • Some pages lack mechanisms to skip blocks of content that repeat across multiple pages [requirement number 9.2.4.1 Bypass Blocks, UNE-EN 301549:2022].
  • Certain web page titles are inadequately descriptive [requirement number 9.2.4.2 Page Titled, UNE-EN 301549:2022].
  • In some documents, sequential navigation using the keyboard may not have a consistent order [requirement number 9.2.4.3 Focus Order, 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), UNE-EN 301549:2022].
  • Links to related content 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 that use multipoint gestures or path-based actions 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].
  • Some pages do not allow canceling an event triggered by a mouse click [requirement number 9.2.5.2 Pointer Cancellation, UNE-EN 301549:2022].
  • Some interface components lack visible labels [requirement number 9.2.5.3 Label in Name, UNE-EN 301549:2022].
  • Functionality is operable only through motion [requirement number 9.2.5.4 Motion Actuation, UNE-EN 301549:2022].
  • Some pages do not indicate the default language being used [requirement number 9.3.1.1 Language of Page, UNE-EN 301549:2022].
  • There may be occasional errors in editing and identifying the language of some parts of the webpage [requirement number 9.3.1.2 Language of Parts, UNE-EN 301549:2022].
  • Some components, when focused, initiate a context change [requirement number 9.3.2.1 On Focus, UNE-EN 301549:2022].
  • User interaction with a control may trigger a page change without prior warning [requirement number 9.3.2.2 On Input, UNE-EN 301549:2022].
  • Some pages may have inconsistent navigation due to different links pointing to the same destination [requirement number 9.3.2.3 Consistent Navigation, UNE-EN 301549:2022].
  • Certain interactive elements are not presented consistently across all cases, as they are displayed with different visual styles [requirement number 9.3.2.4 Consistent Identification, UNE-EN 301549:2022].
  • Error messages are insufficiently descriptive, or errors are not grouped into a single message, and there is a lack of suggestions for filling out fields correctly [requirement number 9.3.3.1 Error Identification, UNE-EN 301549:2022].
  • Some forms with mandatory fields do not inform users about this requirement, and some fields lack textual examples of the expected format [requirement number 9.3.3.2 Labels or Instructions, UNE-EN 301549:2022].
  • There may be input errors in fields or forms where no suggestion is provided to the user for resolution [requirement number 9.3.3.3 Error Suggestions, UNE-EN 301549:2022].
  • Data input does not detect errors, nor is the user 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 recommended structure in accessibility guidelines [requirement number 9.4.1.2 Name, Role, Value, UNE-EN 301549:2022].
  • On certain pages, status messages may not be programmatically determined through functions or properties [requirement number 9.4.1.3 Status Messages, UNE-EN 301549:2022].
  • Some requirements of WCAG 2.1 are not met [requirement number 9.6 Conformance requirements of the WCAG guidelines, of 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, of 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, 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 not be an alternative for time-based media or an audio description for video content recorded in synchronized multimedia content [requirement number 10.1.2.3 Audio description or alternative media, of UNE-EN 301549:2022].
  • There may be no audio description provided for all recorded video content within synchronized multimedia content [requirement number 10.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].
  • In some documents, information, structure, and relationships are not determined by software or do not have a text alternative [requirement number 10.1.3.1 Information and relationships, of UNE-EN 301549:2022].
  • Some documents may not have a programmatically defined correct reading sequence [requirement number 10.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
  • There may be documents where 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 changing the screen orientation [requirement number 10.1.3.4 Orientation, of UNE-EN 301549:2022].
  • In some forms, the input field collecting user information is not identified for its purpose [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 to convey information, indicate an action, prompt a response, or distinguish 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 losing content or functionality, and in some documents, content may lose functionality or information when the content is enlarged [requirement number 10.1.4.4 Resize text, of UNE-EN 301549:2022].
  • In some documents, text images 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 the content is enlarged [requirement number 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 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].
  • Some document content does not receive keyboard focus with which any action can be performed [requirement number 10.1.4.13 Content on hover or focus, of UNE-EN 301549:2022].
  • There are documents that cannot be fully operated using the keyboard [requirement number 10.2.1.1 Keyboard, of UNE-EN 301549:2022].
  • In some documents, headers have not been defined, and navigation via keyboard is not possible [requirement number 10.2.1.2 No keyboard trap, of UNE-EN 301549:2022].
  • Some documents contain 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 without controls to pause, control, or hide it [requirement number 10.2.2.2 Pause, stop, and hide, of UNE-EN 301549:2022].
  • Some documents may contain elements that flash more than three times per second or exceed the general threshold [requirement number 10.2.3.1 Three flashes or below threshold, of UNE-EN 301549:2022].
  • There may be documents without titles [requirement number 10.2.4.2 Page titled, of UNE-EN 301549:2022].
  • In some documents, headers have not been defined, and navigation via keyboard is not possible [requirement number 10.2.4.3 Focus order, of UNE-EN 301549:2022].
  • Some documents may contain links that do not have a specifically defined textual purpose [requirement number 10.2.4.4 Link purpose (in context), of UNE-EN 301549:2022].
  • In some documents, a header or control name may not be sufficiently descriptive of its purpose [requirement number 10.2.4.6 Headings and labels, of UNE-EN 301549:2022].
  • The focus location is not always visible when navigating with the 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 gesture based on [requirement number 10.2.5.1 Pointer Gestures, of UNE-EN 301549:2022]:
  • There are documents where an event cannot be canceled by clicking the mouse [requirement number 10.2.5.2 Pointer Cancellation, of UNE-EN 301549:2022].
  • There are documents where some labels accompanying controls do not share the same name [requirement number 10.2.5.3 Label in Name, of UNE-EN 301549:2022].
  • There are documents whose functionality is operable only 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.2.1 Language of Parts, of UNE-EN 301549:2022].
  • Some documents may include components that initiate a context change upon receiving focus [requirement number 10.3.2.1 On Focus, of UNE-EN 301549:2022].
    User interaction with a control may cause page changes without prior warning [requirement number 10.3.2.2 On Input, of UNE-EN 301549:2022].
  • There are data input 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 document forms, an automatic context change may occur without notifying the user [requirement number 10.3.3.2 Labels or Instructions, of UNE-EN 301549:2022].
  • In some documents, there may be an input field/form error that does not notify the user of a suggestion to resolve it [requirement number 10.3.3.3 Suggestions for Errors, of UNE-EN 301549:2022].
  • In some documents, there may be forms for data collection or legally/financially binding actions that are not reversible, reviewable, or confirmed before submission [requirement number 10.3.3.4 Error Prevention (Legal, Financial, Data), of UNE-EN 301549:2022].
  • Some documents may contain 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 recommended structure by accessibility guidelines [requirement number 10.4.1.2 Name, Role, Value, of UNE-EN 301549:2022].
  • In some documents, status messages may not be programmatically determined through functions or properties [requirement number 10.4.1.3 Status Messages, of UNE-EN 301549:2022].

Criterion 11 – Requirements applicable to software: Not applicable.

  • The user’s visual preferences set in the browser are not respected on the page [requirement number 11.7 User Preferences, of UNE-EN 301549:2022].
  • The accessibility-required information may not be compatible with the format used for the authoring tool’s output [requirement number 11.8.1 Content Management Technology, of UNE-EN 301549:2022].
  • There may not be a mechanism to create content in an accessible manner [requirement number 11.8.2 Creation of Accessible Content, 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].
  • There may not be a repair mechanism for the accessibility checker [requirement number 11.8.4 Repair Service, of UNE-EN 301549:2022].
  • No templates compatible with creating content according to the requirements of Chapters 9 (Web) or 10 (Non-Web Documents) may be available [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 Features and Compatibility, of UNE-EN 301549:2022].
  • The product documentation may not be entirely in accessible formats [requirement number 12.1.2 Accessible Documentation, of UNE-EN 301549:2022].
  • Support services do not provide complete information about accessibility features included in the product documentation [requirement number 12.2.2 Information on Accessibility Features and Compatibility, of UNE-EN 301549:2022].
  • Support services are not always adaptable 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].
  1. 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 meet all accessibility requirements, although efforts have been made to ensure most of them do comply.
    There may be third-party content not developed by 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 meet all accessibility requirements.
    Parts or the entirety of the website may be created with a CMS (WordPress, Shopify, PrestaShop, etc.), and due to 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 January 9, 2025.
The method used to prepare this statement was a self-assessment conducted by the company itself.
Last review of the statement: January 9, 2025.

Observations and contact information
You may make communications regarding accessibility requirements (Article 10.2.a of Royal Decree 1112/2018, dated September 7), such as:

  • Reporting any potential non-compliance by this website.
  • Communicating other difficulties in accessing content.
  • Making any other inquiries or suggestions for improving the accessibility of the website.

Through the following means:

  • Email: macaronesiayachtservice@gmail.com
  • Phone: +34 610 64 25 17

In accordance with 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 regarding:
    • Content excluded from the scope of RD 1112/2018 as established in Article 3, Section 4.
    • Content exempt from compliance with accessibility requirements due to imposing a disproportionate burden.

In the request for accessible information, you must clearly specify the facts, reasons, and request to confirm that it is a reasonable and legitimate request.
Communications will be received and handled by the company management, as the unit responsible for the contents of this website.

Optional content
The version currently visible on this website is from January 9, 2025, and on that date, the accessibility level was reviewed in accordance with the standards in force at the time.
From that date onwards, partial daily reviews are conducted on new or modified web content, including templates, pages, and final published documents, to ensure compliance with the accessibility requirements of UNE-EN 301549:2022, considering the exceptions of Royal Decree 1112/2018, dated September 7.

Among other measures, the following have been adopted to facilitate accessibility:

  • Use of alternative text for images.
  • Links provide details about the hyperlink’s function or destination.
  • Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.

Compatibility
The website:

  • Has been designed to adhere to current standards and regulations regarding accessibility, meeting Priority 2 (AA) verification points defined in the Web Content Accessibility Guidelines (WCAG 2.1).
  • Is optimized for the latest versions of Chrome, Edge, Firefox, Safari, and Opera.
  • Is designed for proper display on any resolution and device, including desktops, tablets, or mobile devices (responsive design).
  • Has been developed using HTML5 as the markup language and CSS 3 for design.

Additionally, continuous auditing and content review are carried out to facilitate interpretation and improve navigation on the website.

This Accessibility Statement document was created using the free online web accessibility statement generator on January 9, 2025.