ES EN

Accessibility Statement

www.betancourtevents.com

Compliance status

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

Non-accessible content

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

a. Non-compliance with Royal Decree 1112/2018: Not applicable. It complies with 100% of the web accessibility criteria.

    • Criterion 5 – General requirements: Not applicable.
  • Incompatible means may be required to activate some accessibility feature [requirement number 5.2 Activation of accessibility features, UNE-EN 301549:2022].
    • Criterion 6 – Two-way voice communication capability: Not applicable.
  • It may not be possible to guarantee a frequency range with an upper limit of at least 7000Hz [requirement number 6.1 Voice bandwidth, UNE-EN 301549:2022].
  • It may not be possible to provide a two-way communication mode via RTT [requirement number 6.2.1.1 RTT communication, UNE-EN 301549:2022].
  • It may not be possible to provide a two-way simultaneous voice and text communication mode [requirement number 6.2.1.2 Simultaneous voice and text, UNE-EN 301549:2022].
  • It may not clearly distinguish on-screen the text sent from the text received in RTT communications [requirement number 6.2.2.1 Visually distinguishable on-screen presentation, UNE-EN 301549:2022].
  • It may not be possible for software to determine the direction of sending and receiving RTT [requirement number 6.2.2.2 Software-determinable send/receive direction, UNE-EN 301549:2022].
  • It may not be possible to provide speaker identification via RTT [requirement number 6.2.2.3 Speaker identification, UNE-EN 301549:2022].
  • There may not be an on-screen visual indicator of real-time audio activity [requirement number 6.2.2.4 Visual indicator of audio with real-time text, UNE-EN 301549:2022].
  • It may not be possible to guarantee interoperability with other systems with RTT functionalities [requirement number 6.2.3 Interoperability, UNE-EN 301549:2022].
  • It may not be possible to ensure that RTT input is transmitted to the network within 500ms [requirement number 6.2.4 RTT responsiveness, UNE-EN 301549:2022].
  • An alternative to voice may not be provided for assistance tasks or interactive response tasks [requirement number 6.4 Alternatives to voice-based services, UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum QVGA resolution for video functionalities [requirement number 6.5.2 Resolution, UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum video frame rate of 20 FPS during communications [requirement number 6.5.3 Frame rate, UNE-EN 301549:2022].
  • The maximum time of 100ms between voice and video presentation to the user may not be exceeded [requirement number 6.5.4 Audio and video synchronization, UNE-EN 301549:2022].
  • There may not be a mode for speaker identification for real-time sign language users [requirement number 6.5.6 Speaker identification with video communication, UNE-EN 301549:2022].
    • Criterion 7 – Video capability: Not applicable.
  • Some video players may not have an operation mode that allows existing captions to be displayed [requirement number 7.1.1 Caption playback, UNE-EN 301549:2022].
  • Some video players may not have an operation mode that allows audio to be synchronized with captions [requirement number 7.1.2 Caption synchronization, UNE-EN 301549:2022].
  • Some video players may not provide a system for saving captions [requirement number 7.1.3 Caption preservation, UNE-EN 301549:2022].
  • Users may not be able to adapt caption characteristics to their individual requirements [requirement number 7.1.4 Caption characteristics, UNE-EN 301549:2022].
  • In all cases, an operation mode that facilitates spoken output of available captions may not be provided [requirement number 7.1.5 Spoken captions, 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, UNE-EN 301549:2022].
  • Some players may not have a mode to synchronize available audio descriptions [requirement number 7.2.2 Audio description synchronization, UNE-EN 301549:2022].
  • Some players may not have a mode to save available audio descriptions [requirement number 7.2.3 Audio description preservation, UNE-EN 301549:2022].
  • Some pages include a video player that does not provide controls for captions and audio description at the same interaction level as other controls [requirement number 7.3 User controls for captions and audio description, UNE-EN 301549:2022].
    • Criterion 9 – Requirements applicable to web pages: Not applicable.
  • There is non-text content that lacks a text alternative, or has an alternative that is not suitable [requirement number 9.1.1.1 Non-text content, UNE-EN 301549:2022].
  • Some recorded videos do not have text-based alternatives or audio alternatives [requirement number 9.1.2.1 Audio-only and video-only (pre-recorded), UNE-EN 301549:2022].
  • Some recorded videos may not include captions [requirement number 9.1.2.2 Captions (pre-recorded), UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative media [requirement number 9.1.2.3 Audio description or alternative media, UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative media [requirement number 9.1.2.5 Audio description (pre-recorded), UNE-EN 301549:2022].
  • On some pages, information, structure and relationships are not programmatically determined or do not have a text alternative [requirement number 9.1.3.1 Info and relationships, UNE-EN 301549:2022].
  • Some pages do not have at least one correct reading sequence defined programmatically [requirement number 9.1.3.2 Meaningful sequence, UNE-EN 301549:2022].
  • Identification of elements relies only on sensory characteristics such as shape, color, size, visual location, orientation or sound [requirement number 9.1.3.3 Sensory characteristics, UNE-EN 301549:2022].
  • Content does not adapt when changing screen orientation [requirement number 9.1.3.4 Orientation, UNE-EN 301549:2022].
  • There are form elements where the purpose of the input is not identified [requirement number 9.1.3.5 Identify input purpose, UNE-EN 301549:2022].
  • On some pages, color has been used as the only visual means to convey information, indicate an action, trigger a response, or distinguish a visual element [requirement number 9.1.4.1 Use of color, UNE-EN 301549:2022].
  • There are audio elements that play automatically and there is no mechanism to pause or stop them [requirement number 9.1.4.2 Audio control, UNE-EN 301549:2022].
  • On some pages, the contrast ratio for text may not be at least 4.5:1 [requirement number 9.1.4.3 Contrast (minimum), UNE-EN 301549:2022].
  • There are errors on some pages related to text size and its ability to be customized when zooming [requirement number 9.1.4.4 Resize text, UNE-EN 301549:2022].
  • There are pre-designed images based solely on text [requirement number 9.1.4.5 Images of text, UNE-EN 301549:2022].
  • There are errors when customizing font size, zoom level, or text spacing [requirement number 9.1.4.10 Reflow, UNE-EN 301549:2022].
  • Insufficient contrast in interface components or graphical objects [requirement number 9.1.4.11 Non-text contrast, UNE-EN 301549:2022].
  • There is text that does not display correctly when changing spacing and line heights [requirement number 9.1.4.12 Text spacing, 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 focus [requirement number 9.1.4.13 Content on hover or focus, UNE-EN 301549:2022].
  • There are pages where keyboard navigation is not optimal and errors appear [requirement number 9.2.1.1 Keyboard, UNE-EN 301549:2022].
  • There are components that, when receiving focus, prevent moving to another element using only the Tab key or arrow keys [requirement number 9.2.1.2 No keyboard trap, UNE-EN 301549:2022].
  • There are keyboard shortcuts that do not work [requirement number 9.2.1.4 Character key shortcuts, UNE-EN 301549:2022].
  • A time limit may be set that cannot be stopped, adjusted, or extended [requirement number 9.2.2.1 Timing adjustable, UNE-EN 301549:2022].
  • There may be automatically moving information that does not provide controls to pause, stop, or hide it [requirement number 9.2.2.2 Pause, stop, hide, UNE-EN 301549:2022].
  • There may be elements that flash more than three times in one second or above the general threshold [requirement number 9.2.3.1 Three flashes or below threshold, UNE-EN 301549:2022].
  • On some pages, there is no mechanism to skip blocks of content repeated across multiple pages [requirement number 9.2.4.1 Bypass blocks, UNE-EN 301549:2022].
  • Inadequate description of some web page titles [requirement number 9.2.4.2 Page titled, UNE-EN 301549:2022].
  • In some documents, sequential keyboard navigation 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].
  • Related content links or alternative navigation methods are not always offered [requirement number 9.2.4.5 Multiple ways, UNE-EN 301549:2022].
  • There are headings with repeated and/or poorly descriptive text [requirement number 9.2.4.6 Headings and labels, UNE-EN 301549:2022].
  • Focus location is not always visible when navigating by keyboard [requirement number 9.2.4.7 Focus visible, 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, UNE-EN 301549:2022].
  • There are pages where a mouse event cannot be canceled once triggered [requirement number 9.2.5.2 Pointer cancellation, UNE-EN 301549:2022].
  • There are interface components that do not have visible labels [requirement number 9.2.5.3 Label in name, UNE-EN 301549:2022].
  • There is functionality operable only by motion [requirement number 9.2.5.4 Motion actuation, UNE-EN 301549:2022].
  • On some pages, the default language used is not indicated [requirement number 9.3.1.1 Language of page, UNE-EN 301549:2022].
  • There may be occasional editing and language identification issues in some parts of the web page [requirement number 9.3.1.2 Language of parts, UNE-EN 301549:2022].
  • There are components that, when receiving focus, initiate a change of context [requirement number 9.3.2.1 On focus, UNE-EN 301549:2022].
  • User interaction with some controls may cause page changes without prior warning [requirement number 9.3.2.2 On input, UNE-EN 301549:2022].
  • There may be pages with inconsistent navigation due to different links pointing to the same destination [requirement number 9.3.2.3 Consistent navigation, UNE-EN 301549:2022].
  • Certain interactive elements may not be presented consistently in all cases, as they may appear with different visual styles [requirement number 9.3.2.4 Consistent identification, UNE-EN 301549:2022].
  • There are poorly descriptive error messages, or error messages not grouped into a single message, as well as missing suggestions in forms to fill fields correctly [requirement number 9.3.3.1 Error identification, UNE-EN 301549:2022].
  • There are forms with required fields where the user is not informed, as well as fields lacking a textual example of the required format [requirement number 9.3.3.2 Labels or instructions, UNE-EN 301549:2022].
  • There may be input errors in some fields/forms where the user is not notified with suggestions to fix them [requirement number 9.3.3.3 Error suggestion, UNE-EN 301549:2022].
  • Input errors are not detected and the user is not given an opportunity to correct them [requirement number 9.3.3.4 Error prevention (legal, financial, data), UNE-EN 301549:2022].
  • There may be errors in the use of HTML tags and attributes and WAI-ARIA 1.1 [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 according to accessibility guidelines [requirement number 9.4.1.2 Name, role, value, UNE-EN 301549:2022].
  • On some pages, status messages may not be programmatically determined through functions or properties [requirement number 9.4.1.3 Status messages, UNE-EN 301549:2022].
  • Some WCAG 2.1 requirements are not met [requirement number 9.6 WCAG conformance requirements, UNE-EN 301549:2022].
    • Criterion 10 – Requirements applicable to non-web documents: Not applicable.
  • There may be documents with images that do not have an adequate text alternative [requirement number 10.1.1.1 Non-text content, UNE-EN 301549:2022].
  • There may be no equivalent alternative for audio-only or video-only recorded content [requirement number 10.1.2.1 Audio-only and video-only (pre-recorded), UNE-EN 301549:2022].
  • Videos may lack captions and audio descriptions [requirement number 10.1.2.2 Captions (pre-recorded), UNE-EN 301549:2022].
  • There may be no alternative for time-based media or audio description for recorded video content in synchronized multimedia [requirement number 10.1.2.3 Audio description or alternative media, UNE-EN 301549:2022].
  • Audio description may not be provided for all recorded video content within synchronized multimedia content [requirement number 10.1.2.5 Audio description (pre-recorded), 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, UNE-EN 301549:2022].
  • Some documents do not have at least one correct reading sequence defined programmatically [requirement number 10.1.3.2 Meaningful sequence, UNE-EN 301549:2022].
  • There may be documents for which there is no other accessible alternative to operate and understand the content [requirement number 10.1.3.3 Sensory characteristics, UNE-EN 301549:2022].
  • There may be documents whose content does not adapt when changing screen orientation [requirement number 10.1.3.4 Orientation, UNE-EN 301549:2022].
  • In some forms, the input field that collects user information does not have the purpose identified [requirement number 10.1.3.5 Identify input purpose, UNE-EN 301549:2022].
  • In some documents, color has been used as the only visual means to convey information, indicate an action, trigger a response, or distinguish a visual element [requirement number 10.1.4.1 Use of color, UNE-EN 301549:2022].
  • There are audio elements in some documents that play automatically and there is no mechanism to pause or stop them [requirement number 10.1.4.2 Audio control, UNE-EN 301549:2022].
  • In some documents, the contrast ratio for text may not be at least 4.5:1 [requirement number 10.1.4.3 Contrast (minimum), UNE-EN 301549:2022].
  • In some texts, the size cannot be changed up to 200 percent without loss of content or functionality, and in some documents content may lose functionality or information when zoomed [requirement number 10.1.4.4 Resize text, UNE-EN 301549:2022].
  • In some documents, text images may have been used instead of text to convey information [requirement number 10.1.4.5 Images of text, UNE-EN 301549:2022].
  • In some documents, content may lose functionality or information when zoomed [requirement number 10.1.4.10 Reflow, 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, UNE-EN 301549:2022].
  • In some texts, it is not possible to override specified text spacing [requirement number 10.1.4.12 Text spacing, UNE-EN 301549:2022].
  • Content in some documents does not receive keyboard focus to perform any action [requirement number 10.1.4.13 Content on hover or focus, UNE-EN 301549:2022].
  • There are documents that cannot be fully operated via keyboard [requirement number 10.2.1.1 Keyboard, UNE-EN 301549:2022].
  • In some documents, headings are not defined and keyboard navigation is not possible [requirement number 10.2.1.2 No keyboard trap, UNE-EN 301549:2022].
  • In some documents, keyboard shortcuts do not work [requirement number 10.2.1.4 Character key shortcuts, UNE-EN 301549:2022].
  • In some documents, a time limit may be set that cannot be stopped, adjusted, or extended [requirement number 10.2.2.1 Timing adjustable, UNE-EN 301549:2022].
  • Some documents may contain automatically moving information that does not provide controls to pause, stop, or hide it [requirement number 10.2.2.2 Pause, stop, hide, UNE-EN 301549:2022].
  • Some documents may contain elements that flash more than three times in one second or above the general threshold [requirement number 10.2.3.1 Three flashes or below threshold, UNE-EN 301549:2022].
  • There may be documents that do not have a title [requirement number 10.2.4.2 Page titled, UNE-EN 301549:2022].
  • In some documents, headings are not defined and keyboard navigation is not possible [requirement number 10.2.4.3 Focus order, UNE-EN 301549:2022].
  • Some documents may contain links that may not have the specific purpose textually defined [requirement number 10.2.4.4 Link purpose (in context), UNE-EN 301549:2022].
  • Some documents may contain headings or control names that are not sufficiently descriptive of their purpose [requirement number 10.2.4.6 Headings and labels, UNE-EN 301549:2022].
  • Focus location is not always visible when navigating by keyboard through some documents [requirement number 10.2.4.7 Focus visible, UNE-EN 301549:2022].
  • Some documents may have 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, UNE-EN 301549:2022].
  • There are documents where a mouse event cannot be canceled once triggered [requirement number 10.2.5.2 Pointer cancellation, UNE-EN 301549:2022].
  • There are documents where some labels accompanying controls do not match their names [requirement number 10.2.5.3 Label in name, UNE-EN 301549:2022].
  • There are documents whose functionality is operable only by motion [requirement number 10.2.5.4 Motion actuation, UNE-EN 301549:2022].
  • There may be documents where the main language is not identified [requirement number 10.3.1.1 Language of page, UNE-EN 301549:2022].
  • There may be content or phrases within some documents whose language cannot be programmatically determined [requirement number 10.3.2.1 Language of parts, UNE-EN 301549:2022].
  • There may be components in some documents that, when receiving focus, initiate a change of context [requirement number 10.3.2.1 On focus, UNE-EN 301549:2022].
  • User interaction with some controls may cause page changes without prior warning [requirement number 10.3.2.2 On input, UNE-EN 301549:2022].
  • There are data input fields with automatic error detection that do not identify where or how the error occurs [requirement number 10.3.3.1 Error identification, UNE-EN 301549:2022].
  • In some forms in some documents, an automatic context change may occur without warning the user [requirement number 10.3.3.2 Labels or instructions, UNE-EN 301549:2022].
  • There may be input errors in some fields/forms where the user is not notified with suggestions to fix them [requirement number 10.3.3.3 Error suggestion, UNE-EN 301549:2022].
  • There may be forms in some documents collecting data or that have legal or financial implications that are not reversible, reviewable, or confirmed before submission [requirement number 10.3.3.4 Error prevention (legal, financial, data), UNE-EN 301549:2022].
  • Some documents may contain duplicate attributes and IDs [requirement number 10.4.1.1 Parsing, UNE-EN 301549:2022].
  • In some documents, user interface components such as form elements, links and script-generated components do not follow the recommended structure according to accessibility guidelines [requirement number 10.4.1.2 Name, role, value, UNE-EN 301549:2022].
  • In some documents, status messages may not be programmatically determined through functions or properties [requirement number 10.4.1.3 Status messages, UNE-EN 301549:2022].
    • Criterion 11 – Requirements applicable to software: Not applicable.
  • The browser’s user visual preferences are not respected on the page [requirement number 11.7 User preferences, UNE-EN 301549:2022].
  • Information necessary for accessibility may not be compatible with the format used for the authoring tool output [requirement number 11.8.1 Content management technology, UNE-EN 301549:2022].
  • There may be no mechanism that allows content to be created in an accessible way [requirement number 11.8.2 Accessible content creation, 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, UNE-EN 301549:2022].
  • There may be no repair mechanism for the accessibility checker [requirement number 11.8.4 Repair service, UNE-EN 301549:2022].
  • There may be no template available that supports creating content compliant with the requirements of chapters 9 (Web) or 10 (Non-web documents) [requirement number 11.8.5 Templates, UNE-EN 301549:2022].
    • Criterion 12 – Requirements applicable to documentation and support services: Not applicable.
  • Product documentation does not list or explain all available accessibility features [requirement number 12.1.1 Accessibility and compatibility features, UNE-EN 301549:2022].
  • Product documentation may not be fully available in accessible formats [requirement number 12.1.2 Accessible documentation, UNE-EN 301549:2022].
  • Support services do not provide all information about the accessibility features included in the product documentation [requirement number 12.2.2 Information on accessibility and compatibility features, UNE-EN 301549:2022].
  • Support services may not always be adaptable to the communication needs of users with disabilities [requirement number 12.2.3 Effective communication, UNE-EN 301549:2022].
  • Documentation provided by support services may not be available in an accessible format [requirement number 12.2.4 Accessible documentation, UNE-EN 301549:2022].

b. Disproportionate burden: Not applicable.

c. Content outside the scope of applicable legislation:

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

Preparation of this accessibility statement

This statement was prepared on 21/01/2026

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

Last review of the statement: 21/01/2026

Comments and contact information

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

  • Report any possible non-compliance by this website.
  • Report other difficulties accessing the content.
  • Submit any other query or suggestion for improvement related to the accessibility of the website.

Through the following channels:

  • Email: hola@betancourtevents.com
  • Phone: +34 658 669 969

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 regarding:
    • Content excluded from the scope of application of Royal Decree 1112/2018 as established in article 3, section 4.
    • Content exempt from compliance with accessibility requirements due to disproportionate burden.

In the request for accessible information, the facts, reasons and request must be clearly specified to verify 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 contents of this website.

Optional content

The currently visible version of this website is dated 21/01/2026, and on that date the accessibility level in force at that time was reviewed.

From that date onwards, partial daily reviews are carried out of new or modified web content, including templates, pages and final published documents, in order to ensure compliance with the accessibility requirements of Standard UNE-EN 301549:2022, considering the exceptions of Royal Decree 1112/2018 of 7 September.

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

  • Use of alternative text for 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 in accordance with current accessibility standards and regulations, meeting the priority 2 (AA) checkpoints defined in the Web Content Accessibility Guidelines (WCAG 2.1)
  • is optimized for the latest current versions of Chrome, Edge, Firefox, Safari and Opera
  • is designed to display correctly at any resolution and on any desktop, tablet or mobile device (responsive design)
  • has been developed using HTML5 as the markup language and CSS 3 style sheets for its design.

In addition, continuous auditing and content review work is carried out to facilitate interpretation and improve navigation on the website.

This Accessibility Statement document was created using the generator of a free online web accessibility statement template on 21/01/2026.