3 Line Strategy

Contact Us

Accessibility statement

www.3linestrategy.com

Compliance Status

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

Inaccessible Content

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

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

    • Criterion 5 – General Requirements: Not applicable.
  • Non-compatible media may be required to activate some accessibility features [requirement number 5.2 Activation of accessibility features, of UNE-EN 301549:2022].
    • Criterion 6 – Two-way voice communication capability: Not applicable.
  • A frequency range with an upper limit of at least 7000 Hz may not be guaranteed [requirement 6.1 Voice bandwidth, of UNE-EN 301549:2022].
  • Two-way communication via RTT may not be provided [requirement 6.2.1.1 Communication via RTT, of UNE-EN 301549:2022].
  • Two-way communication with simultaneous voice and text may not be provided [requirement 6.2.1.2 Simultaneous voice and text, of UNE-EN 301549:2022].
  • Text sent and text received may not be clearly displayed in RTT communications [requirement 6.2.2.1 Visually distinguishable display, of UNE-EN 301549:2022].
  • The RTT send and receive address may not be software-determinable [requirement 6.2.2.2 Software-determinable send and receive address, of UNE-EN 301549:2022].
  • RTT speaker identification may not be provided [requirement 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 6.2.2.4 Real-time audio visual indicator with text, of UNE-EN 301549:2022].
  • Compatibility with other systems with RTT capabilities may not be guaranteed [requirement 6.2.3 Interoperability, of UNE-EN 301549:2022].
  • It may not be possible to guarantee that the RTT input will be transmitted to the network within 500 ms [requirement 6.2.4 RTT Responsiveness, of UNE-EN 301549:2022].
  • An alternative to voice may not be provided for interactive assistance or response tasks [requirement 6.4 Alternatives to Voice-Based Services, of UNE-EN 301549:2022].
  • A minimum resolution of QVGA may not be guaranteed for video functionalities [requirement 6.5.2 Resolution, of UNE-EN 301549:2022].
  • A minimum video frame rate of 20 FPS may not be guaranteed during communications [requirement 6.5.3 Frame Rate, of UNE-EN 301549:2022].
  • The maximum delay of 100 ms between the presentation of voice and video to the user may not be exceeded [requirement 6.5.4 Audio and video synchronization, of UNE-EN 301549:2022].
  • There may not be a mode for real-time speaker identification for sign language users [requirement 6.5.6 Speaker identification with video communication, of UNE-EN 301549:2022].
    • Criterion 7 – Video Capability: Not applicable.
  • There may be some video players that do not have an operating mode that allows the display of existing subtitles [requirement 7.1.1 Subtitle Playback, of UNE-EN 301549:2022].
  • There may be some video players that do not have an operating mode that allows the synchronization of audio with subtitles [requirement 7.1.2 Subtitle Synchronization, of UNE-EN 301549:2022].
  • There may be some video players that do not have a subtitle saving system [requirement 7.1.3 Subtitle Preservation, of UNE-EN 301549:2022].
  • The user may not be able to adapt the subtitle characteristics to their individual requirements [requirement 7.1.4 Subtitle characteristics, of UNE-EN 301549:2022].
  • An operating mode that facilitates spoken output of the available subtitles may not be provided in all cases [requirement 7.1.5 Spoken subtitles, of UNE-EN 301549:2022].
  • Some players may not have a mode for selecting and playing available audio descriptions [requirement 7.2.1 Audio description playback, of UNE-EN 301549:2022].
  • Some players may not have a mode for synchronizing available audio descriptions [requirement 7.2.2 Audio description synchronization, of UNE-EN 301549:2022].
  • Some players may not have a way to save audio descriptions [requirement 7.2.3 Preservation of audio description, of UNE-EN 301549:2022].
  • Some pages include a video player that does not provide controls for playing subtitles and audio descriptions at the same level of interaction as the other controls [requirement 7.3 User controls for subtitles and audio description, of UNE-EN 301549:2022].
    • Criterion 9 – Requirements applicable to web pages: Not applicable.
  • There is non-textual content that lacks a text alternative, or that has an alternative that is not suitable [requirement 9.1.1.1 Non-textual content, of UNE-EN 301549:2022].
  • Some recorded videos do not have text-based alternatives or audio alternatives [requirement 9.1.2.1 Audio only and video only, of UNE-EN 301549:2022].
  • Some recorded videos may not contain subtitles [requirement 9.1.2.2 Subtitles (recorded), of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative means [requirement 9.1.2.3 Audio description or alternative means, of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative means [requirement 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 do not have a text alternative [requirement 9.1.3.1 Information and relationships, of UNE-EN 301549:2022].
  • Some pages do not have at least one correct reading sequence defined by software [requirement 9.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
  • Identification of elements with only sensory characteristics such as shape, color, size, visual location, orientation, or sound [requirement 9.1.3.3 Sensory characteristics, of UNE-EN 301549:2022].
  • The content does not adapt when changing the screen orientation [requirement 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 9.1.3.5 Identify the purpose of input, of UNE-EN 301549:2022].
  • On some pages, color has been used as the sole visual means to convey information, indicate an action, elicit a response, or distinguish a visual element [requirement 9.1.4.1 Use of color, of UNE-EN 301549:2022].
  • There are audio elements that play automatically, and there is no mechanism to pause or stop them [requirement 9.1.4.2 Audio control, of UNE-EN 301549:2022].
  • On some pages, the text contrast ratio may not be at least 4.5:1 [requirement 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 9.1.4.4 Text resizing, of UNE-EN 301549:2022].
  • There are text-only clip art images [requirement 9.1.4.5 Text images, of UNE-EN 301549:2022].
  • There are errors when customizing font size, zoom level, or text spacing [requirement 9.1.4.10 Text resizing, of UNE-EN 301549:2022].
  • Insufficient contrast in interface components or graphic objects [requirement 9.1.4.11 Contrast of non-text content, of UNE-EN 301549:2022].
  • Some text does not display correctly when changing spacing and line height [requirement 9.1.4.12 Text spacing, of UNE-EN 301549:2022].
  • When an element receives the mouse pointer or keyboard focus, additional content is displayed that cannot be dismissed without moving the pointer or changing the mouse focus [requirement 9.1.4.13 Content with hover or focus, of UNE-EN 301549:2022].
  • Some pages have suboptimal keyboard navigation, resulting in errors [requirement 9.2.1.1 Keyboard, of UNE-EN 301549:2022].
  • There are components that, when receiving focus, prevent switching to another focus using only the tab or arrow keys [requirement 9.2.1.2 No focus traps, of UNE-EN 301549:2022].
  • There are keyboard shortcuts that do not work [requirement 9.2.1.4 Shortcuts with character keys, of UNE-EN 301549:2022].
  • A time limit has been set that cannot be stopped, adjusted, or extended [requirement 9.2.2.1 Adjustable time, of UNE-EN 301549:2022].
  • There may be some automatically scrolling information that does not have controls to pause, control, or hide [requirement 9.2.2.2 Pause, stop, and hide, of UNE-EN 301549:2022].
  • There may be elements that flash more than three times in one second or above the general threshold [requirement 9.2.3.1 Threshold of three flashes or less, of UNE-EN 301549:2022].
  • Some pages lack a mechanism to skip content blocks that are repeated on multiple pages [requirement 9.2.4.1 Avoid blocks, of UNE-EN 301549:2022].
  • Some web page titles are inadequately described [requirement 9.2.4.2 Page titles, of UNE-EN 301549:2022].
  • In some documents, sequential keyboard navigation may not follow a consistent order [requirement 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 9.2.4.4 Purpose of links (in context), of UNE-EN 301549:2022].
  • Links to related content pages or alternative navigation methods are not always provided [requirement 9.2.4.5 Multiple paths, of UNE-EN 301549:2022].
  • There are headings with repetitive and/or non-descriptive text [requirement 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 9.2.4.7 Visible focus, of 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 9.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
  • There are pages where an event cannot be canceled by mouse click [requirement 9.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].
  • There are interface components that do not have visible labels [requirement 9.2.5.3 Name label, of UNE-EN 301549:2022].
  • There is functionality that can only be operated by movement [requirement 9.2.5.4 Movement activation, of UNE-EN 301549:2022].
  • Some pages do not specify the default language used [requirement 9.3.1.1 Page language, of UNE-EN 301549:2022].
  • There may be occasional editing and language identification errors in some parts of the web page [requirement 9.3.1.2 Language of parts, of UNE-EN 301549:2022].
  • Some components initiate a context change when they receive focus [requirement 9.3.2.1 When receiving focus, of UNE-EN 301549:2022].
  • User interaction with some controls causes page changes without prior warning [requirement 9.3.2.2 When receiving input, of UNE-EN 301549:2022].
  • There may be pages with inconsistent navigation due to different links to the same destination [requirement 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 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 into a single message, as well as a lack of form suggestions for correctly filling out fields [requirement 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 field format is missing [requirement number 9.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • There may be an input error in a field/form for which the user is not notified of a suggestion for resolving it [requirement 9.3.3.3 Suggestions for errors 333, of UNE-EN 301549:2022].
  • Errors are not detected during data entry, nor is the user provided with an opportunity to correct them [requirement 9.3.3.4 Prevention of errors (legal, financial, data), of UNE-EN 301549:2022].
  • Errors may exist in the use of HTML and WAI-ARIA 1.1 tags and attributes [requirement 9.4.1.1 Processing, of UNE-EN 301549:2022].
  • On some pages, user interface components such as form elements, links, and scripted components do not follow the structure recommended by accessibility guidelines [requirement 9.4.1.2 Name, Function, Value, of UNE-EN 301549:2022].
  • On some pages, status messages may not be programmatically determined through functions or properties [requirement 9.4.1.3 Status Messages, of UNE-EN 301549:2022].
  • Some WCAG 2.1 requirements are not met [requirement 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 10.1.1.1 Non-text content, of UNE-EN 301549:2022].
  • There may be no equivalent alternative for audio-only or recorded video content [requirement 10.1.2.1 Audio only and video only, of UNE-EN 301549:2022].
  • Videos may lack subtitles and audio descriptions [requirement 10.1.2.2 (Recorded) subtitles, of UNE-EN 301549:2022].
  • There may be no alternative for time-based media or audio description for recorded video content in synchronized multimedia [requirement 10.1.2.3 Audio description or alternative means, of UNE-EN 301549:2022].
  • Audio description may not be provided for all recorded video content within synchronized multimedia content [requirement 10.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].
  • In some documents, the information, structure, and relationships are not determined by software or have no alternative as text [requirement 10.1.3.1 Information and relationships, of UNE-EN 301549:2022].
  • Some documents do not have at least one correct reading sequence defined by software [requirement 10.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
  • There may be documents for which there is no accessible alternative to operate and understand the content [requirement 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 10.1.3.4 Orientation, of UNE-EN 301549:2022].
  • In some forms, the input field that collects user information does not have an identified purpose [requirement 10.1.3.5 Identifying the 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, elicit a response, or distinguish a visual element [requirement 10.1.4.1 Use of color, of 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 10.1.4.2 Audio control, of UNE-EN 301549:2022].
  • In some documents, the contrast ratio in text may not be at least 4.5:1 [requirement 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 losing content or functionality, and in some documents, content may lose functionality or information when enlarged [requirement 10.1.4.4 Text resizing, of UNE-EN 301549:2022].
  • In some documents, images of text may be used instead of text to convey information [requirement 10.1.4.5 Text images, of UNE-EN 301549:2022].
  • In some documents, content may lose functionality or information when zoomed in [requirement 10.1.4.10 Text reflow, from UNE-EN 301549:2022].
  • In some documents, the contrast between user interface components and graphic objects may not reach 3:1 with adjacent colors [requirement 10.1.4.11 Contrast of non-text content, from UNE-EN 301549:2022].
  • In some texts, it is not possible to override the specified text spacing [requirement 10.1.4.12 Text spacing, from UNE-EN 301549:2022].
  • The content of some documents does not receive keyboard focus that allows any actions to be performed [requirement 10.1.4.13 Content with hover or focus, from UNE-EN 301549:2022].
  • There are documents that cannot be fully operated via the keyboard [requirement 10.2.1.1 Keyboard, of UNE-EN 301549:2022].
  • In some documents, headings have not been defined and keyboard navigation is not possible [requirement 10.2.1.2 No focus traps, of UNE-EN 301549:2022].
  • In some documents, keyboard shortcuts do not work [requirement 10.2.1.4 Shortcuts with character keys, of UNE-EN 301549:2022].
  • In some documents, a time limit is set that cannot be stopped, adjusted, or extended [requirement 10.2.2.1 Adjustable time, of UNE-EN 301549:2022].
  • Some documents may contain automatically scrolling information that lacks controls for pausing, controlling, or hiding [requirement 10.2.2.2 Pause, stop, and hide, of UNE-EN 301549:2022].
  • Some documents may contain elements that flash more than three times in one second or above the general threshold [requirement 10.2.3.1 Threshold of three flashes or less, of UNE-EN 301549:2022].
  • Some documents may not have titles [requirement 10.2.4.2 Page headings, of UNE-EN 301549:2022].
  • In some documents, headings have not been defined, and keyboard navigation is not possible [requirement 10.2.4.3 Focus order, of UNE-EN 301549:2022].
  • Some documents may contain links whose specific purpose may not be clearly defined [requirement 10.2.4.4 Purpose of links (in context), of UNE-EN 301549:2022].
  • Some documents may contain headings or control names that are not sufficiently descriptive of their purpose [requirement 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 10.2.4.7 Visible focus, of UNE-EN 301549:2022].
  • Some documents may contain elements that use multipoint or path-based controls that cannot be operated with a single pointer or without a path-based gesture [requirement 10.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
  • Some documents cannot cancel an event by clicking the mouse [requirement 10.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].
  • Some documents have labels accompanying controls that do not have the same name [requirement 10.2.5.3 Name label, of UNE-EN 301549:2022].
  • Some documents have functionality that is only operable by movement [requirement 10.2.5.4 Activation by movement, of UNE-EN 301549:2022].
  • Some documents may not identify the primary language [requirement 10.3.1.1 Page language, of UNE-EN 301549:2022].
  • There may be content or phrases within some documents whose language cannot be determined by the program [requirement 10.3.2.1 Language of parts, of UNE-EN 301549:2022].
  • There may be components in some documents that, when they receive focus, initiate a context switch [requirement 10.3.2.1 On receiving focus, of UNE-EN 301549:2022].
  • User interaction with a control causes page changes without prior warning [requirement 10.3.2.2 On receiving input, of UNE-EN 301549:2022].
  • There are data entry fields with automatic error detection capabilities that do not identify where or how the error occurred [requirement 10.3.3.1 Error identification, of UNE-EN 301549:2022].
  • In some forms of a document, an automatic context switch may occur without warning the user [requirement 10.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • In some documents, there may be an input error in a field/form for which the user is not notified of a suggestion for resolving it [requirement 10.3.3.3 Suggestions for errors, of UNE-EN 301549:2022].
  • In some documents, there may be forms for data collection or for legally or financially binding forms that are not reversible, revisable, or require confirmation before submission [requirement 10.3.3.4 Prevention of errors (legal, financial, data), of UNE-EN 301549:2022].
  • Some documents may contain duplicate attributes and IDs [requirement 10.4.1.1 Processing, of UNE-EN 301549:2022].
  • Some documents may contain user interface components such as form elements, links, and script-generated components that do not follow the structure recommended by accessibility guidelines [requirement 10.4.1.2 Name, Function, Value, of UNE-EN 301549:2022].
  • Some documents may not have status messages programmatically defined via functions or properties [requirement 10.4.1.3 Status Messages, of UNE-EN 301549:2022].
    • Criterion 11 – Requirements applicable to software: Not applicable.
  • The browser’s visual user preferences are not respected on the page [requirement 11.7 User Preferences, of UNE-EN 301549:2022].
  • The information required for accessibility may not be compatible with the format used for the authoring tool’s output [requirement 11.8.1 Content management technology, of UNE-EN 301549:2022].
  • There may be no mechanism for creating content in an accessible form [requirement 11.8.2 Creating accessible content, of UNE-EN 301549:2022].
  • There may be no mechanism for preserving accessibility information during transformations [requirement 11.8.3 Preservation of accessibility information during transformations, of UNE-EN 301549:2022].
  • There may be no mechanism for repairing the accessibility checker [requirement 11.8.4 Repair service, of UNE-EN 301549:2022].
  • No template may be available that supports creating content that meets the requirements of Chapters 9 (Web) or 10 (Non-web documents) [requirement 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 12.1.1 Accessibility features and support, of UNE-EN 301549:2022].
  • The product documentation may not be fully available in accessible formats [requirement 12.1.2 Accessible documentation, of UNE-EN 301549:2022].
  • Support services do not provide all the information on accessibility features included in the product documentation [requirement 12.2.2 Information on accessibility features and compatibility, of UNE-EN 301549:2022].
  • Support services cannot always adapt to the communication needs of users with disabilities [requirement 12.2.3 Effective communication, of UNE-EN 301549:2022].
  • Some documentation provided by support services may not be in an accessible format [requirement 12.2.4 Accessible documentation, of UNE-EN 301549:2022].

b. Disproportionate burden: Not applicable.

c. Content does not fall within the scope of applicable legislation:

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

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

Last revised statement: 03/26/2025

Comments and contact information

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

  • Report any potential non-compliance with this website.
  • Report any other difficulties accessing the content.
  • Make any other queries or suggestions for improvements related to the website’s accessibility.

Through the following channels:

  • Email: hola@3linestrategy.com
  • Phone: 661 74 18 26

In accordance with Article 10.2.b of Royal Decree 1112/2018, you can also submit:

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

The Request for Accessible Information must clearly specify the facts, reasons, and request that demonstrate that it is a reasonable and legitimate request.

Submissions will be received and processed by company management, as the unit responsible for the content of this website.

Optional Content

The currently visible version of this website is from 03/26/2025, and the accessibility level in force at that time was reviewed on that date.

Starting on that date, daily partial reviews of new or modified web content, including templates and final published pages and documents, are being conducted to ensure compliance with the accessibility requirements of Standard UNE-EN 301549:2022, taking into account the exceptions provided by Royal Decree 1112/2018, of September 7.

Among others, the following measures are being 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 to adapt to current accessibility standards and regulations, complying with the priority 2 (AA) checkpoints defined in the Web Content Accessibility Guidelines (WCAG 2.1) specification.
  • It is optimized for the latest versions of Chrome, Edge, Firefox, Safari, and Opera.
  • It is designed to be displayed correctly at any resolution and device: desktop, tablet, or mobile (responsive design).
  • It has been created using HTML5 as the markup language and CSS 3 style sheets for its design.

In addition, content is continuously audited and reviewed to facilitate interpretation and improve navigation throughout the website.