https://dongsaninternacional.com/

Compliance Status

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

Inaccessible content

The content listed below is inaccessible for the following reasons:

a. Non-compliance with RD 1112/2018: Not applicable. It complies 100% with web accessibility criteria.

  • Criterion 5 - General requirements: Not applicable.
  • Non-compatible means may be required to activate some accessibility features [requirement number 5.2 Activation of accessibility features, of UNE-EN 301549:2022].

  • Criterion 6 - Two-way voice communication capability: Not applicable.
  • A frequency range whose upper limit is at least 7000Hz may not be guaranteed [requirement number 6.1 Voice bandwidth, of UNE-EN 301549:2022].

  • A two-way communication mode using RTT may not be provided [requirement number 6.2.1.1 Communication using RTT, of UNE-EN 301549:2022].

  • A two-way voice and text communication mode may not be provided simultaneously [requirement number 6.2.1.2 Simultaneous voice and text, of UNE-EN 301549:2022].

  • Sent text may not be clearly differentiated from received text in RTT communications [requirement number 6.2.2.1 Visually differentiable screen presentation, of UNE-EN 301549:2022].

  • The sending and receiving direction of RTT may not be determinable by software [requirement number 6.2.2.2 Software-determinable sending and receiving direction, of UNE-EN 301549:2022].

  • Speaker identification by RTT may not be provided [requirement number 6.2.2.3 Speaker identification, of UNE-EN 301549:2022].

  • There may not be a visual on-screen indicator of real-time audio activity [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 RTT responsiveness, of UNE-EN 301549:2022].

  • An alternative to voice for performing interactive assistance or response tasks may not be provided [requirement number 6.4 Alternatives to voice-based services, of UNE-EN 301549:2022].

  • A minimum QVGA resolution may not be guaranteed in video functionalities [requirement number 6.5.2 Resolution, of UNE-EN 301549:2022].

  • A minimum video frame rate of 20 FPS during communications may not be guaranteed [requirement number 6.5.3 Frame rate, of UNE-EN 301549:2022].

  • The maximum time of 100ms between the presentation of voice and video to the user may not be exceeded [requirement number 6.5.4 Audio and video synchronization, of UNE-EN 301549:2022].

  • There may be no mode for speaker identification for sign language users in real time [requirement number 6.5.6 Speaker identification with video communication, of UNE-EN 301549:2022].

  • Criterion 7 - Video capability: Not applicable.
  • There may be a video player that does not have an operating mode that allows existing subtitles to be displayed [requirement number 7.1.1 Subtitle playback, of UNE-EN 301549:2022].

  • There may be a video player that does not have an operating mode that allows audio to be synchronized with subtitles [requirement number 7.1.2 Subtitle synchronization, of UNE-EN 301549:2022].

  • There may be a video player that does not have a subtitle saving system [requirement number 7.1.3 Subtitle preservation, 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].

  • An operating mode that facilitates a spoken output of available subtitles 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 have a mode to select and play available audio descriptions [requirement number 7.2.1 Audio description playback, of UNE-EN 301549:2022].

  • There may be a player that does not have a mode to synchronize available audio descriptions [requirement number 7.2.2 Audio description synchronization, of UNE-EN 301549:2022].

  • There may be a player that does 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 a video player that does not provide controls for subtitle and audio description playback at the same level of interaction as other 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 text alternative, or has an inadequate alternative [requirement number 9.1.1.1 Non-text content, of UNE-EN 301549:2022].

  • Some recorded videos may not have text-based alternatives 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 Captions (Prerecorded), of UNE-EN 301549:2022].

  • Some prerecorded videos on the website may not have audio descriptions or alternative means [requirement number 9.1.2.3 Audio Description or Media Alternative, of UNE-EN 301549:2022].

  • Some prerecorded videos on the website may not have audio descriptions or alternative means [requirement number 9.1.2.5 Audio Description (Prerecorded), of UNE-EN 301549:2022].

  • On some pages, information, structure, and relationships are not determined by software or do not have a text alternative [requirement number 9.1.3.1 Info and Relationships, of UNE-EN 301549:2022].

  • Some pages do not have at least one correct reading sequence defined by the program [requirement number 9.1.3.2 Meaningful Sequence, of UNE-EN 301550:2022].

  • Identification of elements based 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 for which the input purpose is not identified [requirement number 9.1.3.5 Identify Input Purpose, of UNE-EN 301549:2022].

  • On some pages, color has been used as the only visual means to convey information, indicate an action, elicit a response, or distinguish a visual element [requirement number 9.1.4.1 Use of Color, of UNE-EN 301549:2022].

  • There are sound elements that play automatically and there is no mechanism to pause or stop them [requirement number 9.1.4.2 Audio Control, of UNE-EN 301549:2022].

  • On some pages, the text contrast ratio 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 ability to be customized when zooming [requirement number 9.1.4.4 Resize text, of UNE-EN 301549:2022].

  • There are text-only images [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 Reflow, of UNE-EN 301549:2022].

  • Insufficient contrast in interface components or graphic objects [requirement number 9.1.4.11 Non-text Contrast, of UNE-EN 301549:2022].

  • There is text that does not display correctly when spaces and line heights are changed [requirement number 9.1.4.12 Text Spacing, of 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, 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 that, upon receiving focus, prevent it from being passed to another only with the tab key or arrow keys [requirement number 9.2.1.2 No Keyboard Trap, of UNE-EN 301549:2022].

  • Keyboard shortcuts do not work [requirement number 9.2.1.4 Character Key Shortcuts, of UNE-EN 301549:2022].

  • There is a time limit set that cannot be paused, adjusted, or extended [requirement number 9.2.2.1 Timing Adjustable, of UNE-EN 301549:2022].

  • There may be some automatically moving information that does not have controls to pause, control, or hide [requirement number 9.2.2.2 Pause, Stop, Hide, of UNE-EN 301549:2022].

  • There may be elements that flash more than three times in a 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 to bypass blocks of content that are repeated on several pages [requirement number 9.2.4.1 Bypass Blocks, of UNE-EN 301549:2022].

  • Inadequate description of some of the web page titles [requirement number 9.2.4.2 Page Titled, of 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, of 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), of UNE-EN 301549:2022].

  • Links to related content pages or alternative navigation methods are not always offered [requirement number 9.2.4.5 Multiple Ways, of UNE-EN 301549:2022].

  • There are headings with repeated and/or uninformative 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 the keyboard [requirement number 9.2.4.7 Focus Visible, of UNE-EN 301549:2022].

  • There are elements that use multipoint or path-based input that cannot be operated with only one 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 canceled when pressing 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 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 editing and language identification errors in some parts of the web page [requirement number 9.3.1.2 Language of Parts, of UNE-EN 301549:2022].

  • There are components that, when receiving focus, initiate a change of context [requirement number 9.3.2.1 On Focus, of UNE-EN 301549:2022].

  • User interaction with some controls 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 with different visual styles [requirement number 9.3.2.4 Consistent Identification, of UNE-EN 301549:2022].

  • There are uninformative error messages, or error messages that are not grouped into a single message, as well as a lack of suggestions in forms to correctly fill in the fields [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 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 some field/form that the user is not notified of with a suggestion to solve it [requirement number 9.3.3.3 Error Suggestion 333, of UNE-EN 301549:2022].

  • In data 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), of 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, 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 accessibility guidelines [requirement number 9.4.1.2 Name, Role, Value, of 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, of UNE-EN 301549:2022].

  • Some of the WCAG 2.1 requirements are not met [requirement number 9.6 WCAG conformance requirements, of UNE-EN 301549:2022].

  • Criterion 10 - Requirements applicable to non-web documents: Not applicable.
  • Documents may exist 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 not be an 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 Captions (Prerecorded), of UNE-EN 301549:2022].

  • There may not be an alternative for time-based media or an audio description for recorded video content in synchronized multimedia [requirement number 10.1.2.3 Audio Description or Media Alternative, of UNE-EN 301549:2022].

  • An audio description may not be provided for all recorded video content within synchronized multimedia content [requirement number 10.1.2.5 Audio Description (Prerecorded), 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 Info and Relationships, of UNE-EN 301549:2022].

  • Some documents do not have at least one correct reading sequence defined by the program [requirement number 10.1.3.2 Meaningful Sequence, of UNE-EN 301549:2022].

  • There may be documents for which there is no other 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 user information does not have its purpose identified [requirement number 10.1.3.5 Identify Input Purpose, of UNE-EN 301549:2022].

  • In some documents, color has been used as the only visual means to transmit information, indicate an action, elicit 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 there is no 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 may 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 loss of content or functionality, and in some documents, content may lose functionality or information when enlarged [requirement number 10.1.4.4 Resize text, of 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, content may lose functionality or information when enlarged [requirement number 10.1.4.10 Reflow, of UNE-EN 301549:2022].

  • In some documents, the contrast of user interface components and graphic 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 specified text spacing [requirement number 10.1.4.12 Text Spacing, of UNE-EN 301549:2022].

  • The content of some documents does not receive keyboard focus to perform any action [requirement number 10.1.4.13 Content on Hover or Focus, of UNE-EN 301549:2022].

  • There are documents that cannot be fully operated via the keyboard [requirement number 10.2.1.1 Keyboard, of UNE-EN 301549:2022].

  • In some documents, headings have not been defined and cannot be navigated by keyboard [requirement number 10.2.1.2 No Keyboard Trap, of UNE-EN 301549:2022].

  • In some documents, keyboard shortcuts 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 paused, adjusted, or extended [requirement number 10.2.2.1 Timing Adjustable, of UNE-EN 301549:2022].

  • Some documents may contain automatically moving information that does not have controls to pause, control, or hide [requirement number 10.2.2.2 Pause, Stop, Hide, of UNE-EN 301549:2022].

  • Some documents may contain elements that flash more than three times in a second or above the general threshold [requirement number 10.2.3.1 Three Flashes or Below Threshold, of UNE-EN 301549:2022].

  • Documents may exist that do not have a title [requirement number 10.2.4.2 Page Titled, of UNE-EN 301549:2022].

  • In some documents, headings have not been defined and cannot be navigated by keyboard [requirement number 10.2.4.3 Focus Order, of UNE-EN 301549:2022].

  • Some documents may contain a link that may not have its specific purpose textually defined [requirement number 10.2.4.4 Link Purpose (In Context), of UNE-EN 301549:2022].

  • In some documents, some heading 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 some documents with the keyboard [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 input that cannot be operated with only one 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 canceled when pressing the mouse [requirement number 10.2.5.2 Pointer Cancellation, of UNE-EN 301549:2022].

  • There are documents that have some labels accompanying controls that do not have the same name [requirement number 10.2.5.3 Label in Name, 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].

  • Documents may exist in which the main language is not identified [requirement number 10.3.1.1 Language of Page, of UNE-EN 301549:2022].

  • Content or phrases within some documents may exist whose language cannot be programmatically determined [requirement number 10.3.2.1 Language of Parts, of UNE-EN 301549:2022].

  • Components may exist in some documents that, when receiving focus, initiate a change of context [requirement number 10.3.2.1 On Focus, of UNE-EN 301549:2022].

  • User interaction with some controls 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 forms of some documents, an automatic context change may occur without warning the user [requirement number 10.3.3.2 Labels or Instructions, of UNE-EN 301549:2022].

  • In some documents, there may be an input error in some field/form that the user is not notified of with a 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 that is legally or financially compromising that is not reversible, reviewable, or has confirmation before submission [requirement number 10.3.3.4 Error Prevention (Legal, Financial, Data), of UNE-EN 301549:2022].

  • In some documents, duplicate attributes and IDs may exist [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 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 browser's user visual preferences are not respected on the page [requirement number 11.7 User Preferences, of UNE-EN 301549:2022].

  • The necessary information 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 be no mechanism that allows content to be created in an accessible way [requirement number 11.8.2 Accessible Content Creation, of UNE-EN 301549:2022].

  • There is no mechanism for preserving accessibility information during transformations [requirement number 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 number 11.8.4 Repair Service, of UNE-EN 301549:2022].

  • No template may be available that is compatible with the creation of content compliant with the requirements of Chapters 9 (Web) or 10 (Non-web documents) [requirement number 11.8.5 Templates, of UNE-EN 301549:2022].

  • Criterion 12 - Requirements applicable to documentation and support services: Not applicable.
  • 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].

  • 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 all the information on 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 cannot always be adapted 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].

b. Disproportionate burden: Not applicable.

c. Content not within the scope of applicable legislation:

  • There may be office files in PDF and other formats published before September 20, 2018, that do not fully meet all accessibility requirements. Although efforts have been made to ensure that most of them do.

  • There may be third-party content that is not developed by this Unit or under its control, such as images, interactive maps, videos, documents, players, etc.

  • There may be prerecorded 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 some update or change 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 26/06/2025. The method used to prepare the statement was a self-assessment carried out by the company itself. Last review of the statement: 26/06/2025

Observations and contact details

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

  • Reporting any possible non-compliance by this website.

  • Transmitting other difficulties in accessing content.

  • Making any other query or suggestion for improvement related to the accessibility of the website.

Through the following channels:

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

  • A complaint regarding compliance with the requirements of RD 1112/2018.

  • A request for accessible information regarding:

    • Content that is excluded from the scope of application of RD 1112/2018 as established by article 3, section 4.

    • Content that is exempt from complying with accessibility requirements due to imposing a disproportionate burden. In the Request for accessible information, the facts, reasons, and request that allow verifying that it is a reasonable and legitimate request must be clearly specified. Communications will be received and processed by the company's management, as the unit responsible for the content of this website.

Optional content The currently visible version of this website is from 26/06/2025, and on that date, the review of the accessibility level in force at that time was carried out.

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

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

  • Use of alternative text in images.

  • Links offer details of the function or destination of the hyperlink.

  • Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.

Compatibility

The website:

  • has been designed adapting to current accessibility standards and regulations, complying with priority 2 (AA) checkpoints defined in the Web Content Accessibility Guidelines (WCAG 2.1) specification.

  • is optimized for the latest current versions of Chrome, Edge, Firefox, Safari, and Opera.
  • is designed for correct viewing at any resolution and on desktop, tablet, or mobile devices (responsive design).
  • has been created 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 its interpretation and improve navigation through the web portal.

This Accessibility Statement document was created using the free online web accessibility statement template generator on 26/06/2025.