Open Gateway
es pt

Accessibility Statement

Compliance Status

https://opengateway.telefonica.com  (hereinafter also referred to as Website) is partially compliant with Royal Decree 1112/2018, of 7 September, due to non-compliance with the aspects listed below.

Content is not accessible

The content below is not accessible for the following reasons:

a. Non-compliance with RD 1112/2018

  • Criterion no. 5 - General Requirements:
    • Non-compliant means may be needed in order to activate an accessibility feature [requirement number 5.2, Activation of accessibility features, of UNE-EN 301549:2022].
  • Criterion no. 6 - Two-way voice communication capability:
    • There is a possibility that a frequency range with an upper limit of at least 7000Hz may not be guaranteed [requirement number 6.1, Voice bandwidth of UNE-EN 301549:2022].
    • It may not be possible to provide a two-way communication mode via RTT [requirement number 6.2.1.1, Communication via RTT, of UNE-EN 301549:2022].
    • It may not be possible to provide a two-way communication mode with simultaneous voice and text [requirement number 6.2.1.2, Simultaneous voice and text, of UNE-EN 301549:2022].
    • It may not show sent text and received text in RTT communications in a clearly differentiated manner [requirement number 6.2.2.1, Visually differentiable screen presentation, of UNE-EN 301549:2022].
    • The RTT sending and receiving address may not be determinable by the software [requirement number 6.2.2.2, Sending and receiving address determinable by software, of UNE-EN 301549:2022].
    • It may not be possible to provide speaker identification by RTT [requirement number 6.2.2.3, Speaker identification, of UNE-EN 301549:2022].
    • There may not be an on-screen visual indicator of real-time audio activity [requirement number 6.2.2.4, Visual audio indicator with real-time text, of UNE-EN 301549:2022].
    • It may not be able to guarantee compatibility with other systems with RTT functionalities [requirement number 6.2.3, Interoperability, of UNE-EN 301549:2022].
    • It may not be able to guarantee that the 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 when carrying out interactive response or assistance tasks [requirement number 6.4, Alternatives to voice-based services, of UNE-EN 301549:2022].
    • It may not be possible to guarantee a minimum QVGA resolution for video functionalities [requirement number 6.5.2, Resolution, of UNE-EN 301549:2022].
    • It may not be possible to guarantee a minimum video frame rate of 20 FPS during communications [requirement number 6.5.3, Frame rate, of 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 synchronisation, of UNE-EN 301549:2022].
    • There may not be a speaker identification function for sign language users in real time [requirement number 6.5.6, Speaker identification with video communication, of UNE-EN 301549:2022].
  • Criterion no. 7 - Video capacity:
    • It is possible that there is a video player that does not have an operation mode that allows for displaying existing subtitles [requirement number 7.1.1, Subtitle playback, of UNE-EN 301549:2022].
    • It is possible that there is a video player that does not have an operation mode that allows the audio to be synchronised with the subtitles [requirement number 7.1.2, Subtitle synchronisation, of UNE-EN 301549:2022].
    • There may be a video player that does not have a subtitle saving system [requirement number 7.1.3, Preservation of subtitling, of 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, Subtitle characteristics, of UNE-EN 301549:2022].
    • A mode of operation enabling spoken output of the subtitles available 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 does not include a mode for selecting and playing available audio description [requirement number 7.2.1, Playback of audio description, of UNE-EN 301549:2022].
    • It is possible that there is a player that does not have a feature to synchronise available audio description [requirement number 7.2.2, Synchronisation of audio description, of UNE-EN 301549:2022].
    • It is possible that there is a player that has no way to save available audio descriptions [requirement number 7.2.3, Preservation of audio description, of UNE-EN 301549:2022].
    • Some pages include a video player that provides controls for audio description and subtitle playback which are not as interactive as the rest of the controls [requirement number 7.3, User controls for subtitles and audio description, of UNE-EN 301549:2022].
  • Criterion no. 9 - Requirements for websites:
    • There are non-textual contents that lack a text-based alternative, or have an alternative that is inadequate [requirement number 9.1.1.1, Non-textual content, of UNE-EN 301549:2022].
    • Some recorded videos do not have 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 of the website's pre-recorded videos do not have audio description or alternative means [requirement number 9.1.2.3, Audio description or alternative means, of UNE-EN 301549:2022].
    • Some of the website's pre-recorded videos do not have audio description or alternative means [requirement number 9.1.2.5, Audio description (recorded), of UNE-EN 301549:2022].
    • On some pages, the information, structure and relationships are not determined by software or have no text-based alternative [requirement number 9.1.3.1, Information and relationships, of UNE-EN 301549:2022].
    • A page contains at least one incorrect reading sequence, which is not programmatically defined [requirement number 9.1.3.2, Meaningful sequence, of UNE-EN 301549:2022].
    • Identification of elements with sensory characteristics only, such as shape, colour, size, visual location, orientation or sound [requirement number 9.1.3.3, Sensory characteristics, of UNE-EN 301549:2022].
    • The content does not adapt when changing the screen orientation [requirement number 9.1.3.4, Orientation, of UNE-EN 301549:2022].
    • There are elements of forms where the input purpose is not identified [requirement number 9.1.3.5, Identify input purpose, of UNE-EN 301549:2022].
    • On some pages colour has been used as the sole visual means to convey information, indicate an action, elicit a response or distinguish a visual element [requirement number 9.1.4.1, Use of colour, of UNE-EN 301549:2022].
    • There are sound elements that play automatically and there is no mechanism to pause or stop it [requirement number 9.1.4.2 Audio control, of UNE-EN 301549:2022].
    • On some pages, the text contrast ratio may be below the 4.5:1 threshold [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 customisability when zooming in [requirement number 9.1.4.4, Text resizing, of UNE-EN 301549:2022].
    • Text-based clipart is available [requirement number 9.1.4.5, Text images, from UNE-EN 301549:2022].
    • There are errors when customising the font size, zoom or text spacing [requirement number 9.1.4.10, Reflow, of UNE-EN 301549:2022].
    • Insufficient contrast in interface components or graphical objects [requirement number 9.1.4.11, Non-text contrast, of UNE-EN 301549:2022].
    • There is text that is not correctly displayed when line heights and spacing is changed [requirement number 9.1.4.12, Text spacing, of UNE-EN 301549:2022].
    • When an element is focused by the pointer or keyboard, 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 not optimal and errors appear [requirement number 9.2.1.1, Keyboard, of UNE-EN 301549:2022].
    • There are components which, when focused, prevent switching the focus to another element by using the tab or arrow keys only [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].
    • There is a time limitation in place that cannot be stopped, adjusted or extended [requirement number 9.2.2.1, Adjustable time, of UNE-EN 301549:2022].
    • There may be some information set to automatic movement that does not offer pause, setting or hide controls [requirement number 9.2.2.2, Pause, stop, hide, of UNE-EN 301549:2022].
    • There may be elements flashing 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 for omitting blocks of content that are repeated on several pages [requirement number 9.2.4.1, Bypassing blocks, of UNE-EN 301549:2022].
    • Inadequate description of some of the web page titles[requirement number 9.2.4.2, Page titles, of UNE-EN 301549:2022].
    • In some documents the sequential keyboard navigation may not have a consistent order [requirement number 9.2.4.3, Focus order, of UNE-EN 301549:2022].
    • The purpose of the portal's links, headings or labels 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 ways of navigation are not always provided [requirement number 9.2.4.5, Multiple pathways, of UNE-EN 301549:2022].
    • There are headings with repeated and/or non-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 with a keyboard [requirement number 9.2.4.7, Visible focus, of UNE-EN 301549:2022].
    • There are elements using multipoint or path-based that cannot be operated with only a 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 cancelled by clicking the mouse [requirement number 9.2.5.2, Pointer cancellation, of UNE-EN 301549:2022].
    • There are interface components that do not have visible labels [requirement number 9.2.5.3, Label in name, of UNE-EN 301549:2022].
    • There is functionality that is only operable by 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 may be occasional errors in editing and language identification in some parts of the website [requirement number 9.3.1.2, Language of parts, of UNE-EN 301549:2022].
    • There are components that, when in focus, initiate a context switch [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 with 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 in different visual styles [requirement number 9.3.2.4, Consistent identification, of UNE-EN 301549:2022].
    • There are error messages that are not very descriptive, or error messages that are not grouped in a single message as well as lack of suggestions in the form to help fill in the fields correctly [requirement number 9.3.3.1, Error identification, of UNE-EN 301549:2022].
    • There are forms with mandatory fields where the user is not informed of this, as well as fields where a textual example of the format of the field is missing [requirement number 9.3.3.2, Labels or instructions, of UNE-EN 301549:2022].
    • There could be an input error in a field/form whereby the user is not notified with any suggestion to solve it [requirement number 9.3.3.3, Error suggestion 333, of UNE-EN 301549:2022].
    • The data entry does not detect errors and does not provide the user with an opportunity to correct them [requirement number 9.3.3.4, Prevention of errors (legal, financial, data), of UNE-EN 301549:2022].
    • Errors may occur 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 the accessibility guidelines [requirement number 9.4.1.2, Name, role, value, of UNE-EN 301549:2022].
    • On some pages, status messages may not be determined programmatically through functions or properties [requirement number 9.4.1.3, Status messages, of UNE-EN 301549:2022].
    • Some of the WCAG 2.1 requirements are not met [requirement number 9.6, Conformance requirements of the WCAG guidelines, of UNE-EN 301549:2022].
  • Criterion no. 10 - Requirements for non-web documents:
    • There may be documents with images that do not have an adequate textual 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 pre-recorded 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 (pre-recorded), of UNE-EN 301549:2022].
    • There may not be an alternative for time-dependent media or an audio description for video content recorded in synchronised multimedia [requirement number 10.1.2.3, Audio description or media alternative, of UNE-EN 301549:2022].
    • Audio description may not be provided for all recorded video content within synchronised multimedia content [requirement number 10.1.2.5, Audio description (pre-recorded), of UNE-EN 301549:2022].
    • In some documents, the information, structure and relationships are not determined by software or have no text-based alternative [requirement number 10.1.3.1, Information and relationships, of UNE-EN 301549:2022].
    • Some documents do not have at least one correct programmatically defined reading sequence [requirement number 10.1.3.2, Meaningful sequence, of UNE-EN 301549:2022].
    • There may be documents for which there is no accessible alternative with which 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 is changed [requirement number 10.1.3.4, Orientation, of UNE-EN 301549:2022].
    • In some forms the input field that collects information about the user does identify the purpose [requirement number 10.1.3.5, Identify input purpose, of UNE-EN 301549:2022].
    • Colour has been used as the sole visual means to convey information, indicate an action, elicit a response or distinguish a visual element in a document [requirement number 10.1.4.1, Use of colour, of UNE-EN 301549:2022].
    • There are audio elements in a document that play automatically and there is no mechanism to pause or stop it [requirement number 10.1.4.2, Audio control, of UNE-EN 301549:2022].
    • The text contrast ratio may be below 4.5:1 in a document [requirement number 10.1.4.3, Contrast (minimum), of UNE-EN 301549:2022].
    • In some texts the size cannot be changed by up to 200 percent without loss of content or functionality, and in some documents the content may lose functionality or information when the content is enlarged [requirement number 10.1.4.4, Text resizing, from 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, of UNE-EN 301549:2022].
    • In some documents the content may lose functionality or information when the content is expanded [requirement number 10.1.4.10, Reflow, of UNE-EN 301549:2022].
    • In some documents the contrast ratio of user interface components and graphical objects may be below 3:1 against adjacent colours [requirement number 10.1.4.11, Non-text contrast, of UNE-EN 301549:2022].
    • For 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 do not receive a keyboard focus with which to perform any action [requirement number 10.1.4.13, Content on hover or focus, of UNE-EN 301549:2022].
    • There are documents where it is not possible to operate entirely via the keyboard [requirement number 10.2.1.1. Keyboard, of UNE-EN 301549:2022].
    • In some documents, the headings are not 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, there is a time limitation in place that cannot be stopped, adjusted or extended [requirement number 10.2.2.1, Adjustable time, of UNE-EN 301549:2022].
    • Some documents could include information set to automatic movement that does not offer pause, setting or hide controls [requirement number 10.2.2.2, Pause, stop, hide, of UNE-EN 301549:2022].
    • Some documents could include elements flashing 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 do not have a title [requirement number 10.2.4.2, Page titling, of UNE-EN 301549:2022].
    • In some documents the headings are not defined and keyboard navigation is not possible [requirement number 10.2.4.3, Focus order, of UNE-EN 301549:2022].
    • Some documents may contain a link whose specific purpose is not textually defined [requirement number 10.2.4.4, Link purpose (in context), of UNE-EN 301549:2022].
    • In some documents there may be a heading or a control name that is not sufficiently descriptive regarding its purpose [requirement number 10.2.4.6, Headings and labels, of UNE-EN 301549:2022].
    • The focus location is not always visible when browsing through a document using a keyboard [requirement number 10.2.4.7, Visible focus, of UNE-EN 301549:2022].
    • There may be document elements using multipoint or path-based that cannot be operated with only a 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 cancelled by clicking the mouse [requirement number 10.2.5.2, Pointer cancellation, of UNE-EN 301549:2022].
    • There are documents that have some labels accompanying the controls whose name does not match [requirement number 10.2.5.3, Label in name, of UNE-EN 301549:2022].
    • There are documents whose functionality is only operable by motion [requirement number 10.2.5.4, Motion actuation, of UNE-EN 301549:2022].
    • There may be documents where the main 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].
    • There may be components in a document that, when in focus, initiate a context switch [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 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, of UNE-EN 301549:2022].
    • In some document forms, an automatic context switch may occur without warning to 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 whereby the user is not notified with any suggestion to solve it [requirement number 10.3.3.3, Error suggestion, of UNE-EN 301549:2022].
    • In some documents, there may be a form for data collection or legal or financial commitments that are not reversible, reviewable or which cannot be confirmed before submission [requirement number 10.3.3.4, Error prevention (legal, financial, data), of UNE-EN 301549:2022].
    • Duplicate attributes and IDs may be present in some documents [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 the accessibility guidelines [requirement number 10.4.1.2, Name, role, value, of UNE-EN 301549:2022].
    • In some documents, status messages may not be determined programmatically through functions or properties [requirement number 10.4.1.3, Status messages, of UNE-EN 301549:2022].
  • Criterion no. 11 - Software requirements:
    • The visual user preferences of the browser are not respected on the page [requirement number 11.7, User preferences, of UNE-EN 301549:2022].
    • The information needed for accessibility may not be compatible with the format used for the output of the authoring tool [requirement number 11.8.1, Content management technology, of UNE-EN 301549:2022].
    • There may not be a mechanism for creating content that is accessible [requirement number 11.8.2, Accessible content creation, of UNE-EN 301549:2022].
    • There is no mechanism for preservation of accessibility information during transformations [requirement number 11.8.3, Preservation of accessibility information in transformations, of UNE-EN 301549:2022].
    • There may be no repair mechanism for the accessibility verifier [requirement number 11.8.4, Repair assistance, of UNE-EN 301549:2022].
    • A template that supports content creation according to the requirements of chapter 9 (Web) or 10 (Non-web documents) may not be available [requirement number 11.8.5, Templates, of UNE-EN 301549:2022].
  • Criterion no. 12 - Requirements for documentation and support services:
    • 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].
    • Product documentation may not be available in full in accessible formats [requirement number 12.1.2, Accessible documentation, of UNE-EN 301549:2022].
    • Support services do not provide all the information on accessibility features that is 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 be adapted 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. The content does not fall within the scope of the applicable legislation:

  • There may be PDF and other office automation files published before 20 September 2018 that do not fully comply with all accessibility requirements. However, efforts have been made to ensure that most of them do comply.
  • There may be third party content that is not developed by or under the control of this Unit, such as images, interactive maps, videos, documents, players, etc.
  • There may be pre-recorded files published before 20 September 2018 that do not fully meet all accessibility requirements.
  • Parts or all of the website may be created with a CMS (WordPress, Shopify, PrestaShop, etc.), so as a result of updates or changes in the systems, not all the generated or self-generated content may comply with all accessibility regulations.

Elaboration of this accessibility statement

This statement was elaborated on 10/07/2025

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

Last statement revision: 07/10/2025

Comments and contact details

You can send messages regarding accessibility requirements (article 10.2.a of Royal Decree 1112/2018, of 7 September) such as, for example:

  • Reporting any possible non-compliance by this website.
  • Conveying other difficulties in accessing content.
  • Making any other query or suggestion for improvement regarding the website's accessibility.

Through the following channels:

  • E-mail: opengateway@telefonica.com

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 relating to:
    • 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 accessibility requirements because it implies a disproportionate burden.

In the Request for Accessible Information, the facts, reasons and request must be clearly stated in order to establish that the request is reasonable and legitimate.

Messages will be received and processed by the company's management, as the unit responsible for the contents of this website.

Compatibility

The website:

  • It has been designed in accordance with current standards and regulations in relation to accessibility, complying with the priority 2 (AA) checkpoints defined in the Web Content Accessibility Guidelines (WCAG 2.1) specification
  • It is optimised for the latest current versions of Chrome, Edge, Firefox, Safari and Opera
  • It is designed to be displayed correctly in any resolution and on any desktop, tablet or mobile device (responsive design)
  • It has been made using HTML5 as markup language and CSS 3 style sheets for its design.

In addition, ongoing auditing and revision of content is carried out to allow for its interpretation and improve navigation on the web portal.