Logo Aza Translation
Request information

Accessibility

azatranslation.com

Compliance status

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

Content not accessible

The content below is not accessible for the following reasons:

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

  • Criterion 5 – General requirements: Not applicable.
  • Non-compliant means may be required to activate certain accessibility features [requirement number 5.2 Activation of accessibility features, from UNE-EN 301549:2022].
  • Criterion 6 – Two-way voice communication capability: Not applicable.
  • It may not be possible to guarantee a frequency range with an upper limit of at least 7000Hz [requirement number 6.1 Bandwidth for voice, from UNE-EN 301549:2022].
  • It may not be possible to provide two-way communication via RTT [requirement number 6.2.1.1 Communication via RTT, from UNE-EN 301549:2022].
  • It may not be possible to provide two-way voice and text communication simultaneously [requirement number 6.2.1.2 Simultaneous voice and text, from UNE-EN 301549:2022].
  • It may not clearly differentiate between sent and received text in RTT communications [requirement number 6.2.2.1 Visually distinguishable display, from UNE-EN 301549:2022].
  • It may not be possible to determine the RTT send and receive address by software [requirement number 6.2.2.2 Send and receive address determinable by software, from UNE-EN 301549:2022].
  • It may not be possible to provide speaker identification via RTT [requirement number 6.2.2.3 Speaker identification, from UNE-EN 301549:2022].
  • There may be no visual indicator on screen for real-time audio activity [requirement number 6.2.2.4 Visual audio indicator with real-time text, from UNE-EN 301549:2022].
  • It may not be possible to guarantee compatibility with other systems with RTT functionality [requirement number 6.2.3 Interoperability, from 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 number 6.2.4 RTT responsiveness, from UNE-EN 301549:2022].
  • An alternative to voice may not be provided for performing assistance or interactive response tasks [requirement number 6.4 Alternatives to voice-based services, from UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum resolution of QVGA in video functionalities [requirement number 6.5.2 Resolution, from 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, from UNE-EN 301549:2022].
  • The maximum time of 100 ms between the presentation of the voice and the video to the user may not be exceeded [requirement number 6.5.4 Audio and video synchronization, from UNE-EN 301549:2022].
  • There may be no way to identify the speaker for real-time sign language users [requirement number 6.5.6 Speaker identification with video communication, from 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 existing subtitles to be displayed [requirement number 7.1.1 Subtitle playback, from UNE-EN 301549:2022].
  • There may be some video players that do not have an operating mode that allows audio to be synchronized with subtitles [requirement number 7.1.2 Subtitle synchronization, from UNE-EN 301549:2022].
  • There may be some video players that do not have a system for saving subtitles [requirement number 7.1.3 Preservation of subtitles, from 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 Characteristics of subtitles, from UNE-EN 301549:2022].
  • An operating mode that facilitates spoken output of available subtitles may not be provided in all cases [requirement number 7.1.5 Spoken subtitles, from UNE-EN 301549:2022].
  • There may be some players that do not have a mode for selecting and playing available audio descriptions [requirement number 7.2.1 Audio description playback, from UNE-EN 301549:2022].
  • There may be some players that do not have a mode for synchronizing available audio descriptions [requirement number 7.2.2 Audio description synchronization, from UNE-EN 301549:2022].
  • There may be some players that do not have a mode for saving available audio descriptions [requirement number 7.2.3 Preservation of audio description, from UNE-EN 301549:2022].
  • Some pages incorporate video players that do not provide controls for playing subtitles and audio description at the same level of interaction as the rest of the controls [requirement number 7.3 User controls for subtitles and audio description, from UNE-EN 301549:2022].
  • Criterion 9 – Requirements applicable to web pages: Not applicable.
  • There is non-textual content that lacks a textual alternative, or that has an alternative that is not adequate [requirement number 9.1.1.1 Non-textual content, from 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, from UNE-EN 301549:2022].
  • Some recorded videos may not contain subtitles [requirement number 9.1.2.2 Subtitles (recorded), from 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, from 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 (recorded), from UNE-EN 301549:2022].
  • On some pages, the information, structure, and relationships are not determined by software or do not have an alternative in text form [requirement number 9.1.3.1 Information and relationships, from UNE-EN 301549:2022].
  • Some pages do not have at least one correct reading sequence defined by program [requirement number 9.1.3.2 Meaningful sequence, from UNE-EN 301549: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, from UNE-EN 301549:2022].
  • The content does not adapt when changing the screen orientation [requirement number 9.1.3.4 Orientation, from UNE-EN 301549:2022].
  • There are form elements in which the purpose of the input is not identified [requirement number 9.1.3.5 Identify the purpose of the input, from UNE-EN 301549:2022].
  • On some pages, color has been used as the sole visual means of conveying information, indicating an action, eliciting a response, or distinguishing a visual element [requirement number 9.1.4.1 Use of color, from 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, from UNE-EN 301549:2022].
  • On some pages, the contrast ratio in text may not be at least 4.5:1 [requirement number 9.1.4.3 Contrast (minimum), from UNE-EN 301549:2022].
  • There are errors on some pages related to text size and the ability to customize it when zooming [requirement number 9.1.4.4 Text size change, from UNE-EN 301549:2022].
  • There are clip art images based solely on text [requirement number 9.1.4.5 Text images, from UNE-EN 301549:2022].
  • There are errors when customizing the font size, zoom level, or text spacing [requirement number 9.1.4.10 Text readjustment, from UNE-EN 301549:2022].
  • Insufficient contrast in interface components or graphic objects [requirement number 9.1.4.11 Contrast of non-textual content, from UNE-EN 301549:2022].
  • There is text that is not displayed correctly when changing line spacing and height [requirement number 9.1.4.12 Text spacing, from 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 with hover or focus, from UNE-EN 301549:2022].
  • There are pages where keyboard navigation is not optimal and errors appear [requirement number 9.2.1.1 Keyboard, from UNE-EN 301549:2022].
  • There are components that, when receiving focus, prevent it from being passed to another component using only the tab key or arrow keys [requirement number 9.2.1.2 No focus traps, from UNE-EN 301549:2022].
  • There are keyboard shortcuts that do not work [requirement number 9.2.1.4 Character key shortcuts, from UNE-EN 301549:2022].
  • There is a time limit that cannot be stopped, adjusted, or extended [requirement number 9.2.2.1 Adjustable time, from UNE-EN 301549:2022].
  • There may be some information in automatic motion that does not have controls to pause, control, or hide [requirement number 9.2.2.2 Pause, stop, and hide, from UNE-EN 301549:2022].
  • There may be elements that flash more than three times per second or above the general threshold [requirement number 9.2.3.1 Threshold of three flashes or less, from UNE-EN 301549:2022].
  • Some pages do not have a mechanism for skipping blocks of content that are repeated on several pages [requirement number 9.2.4.1 Avoid blocks, from UNE-EN 301549:2022].
  • Inadequate description of some of the web page titles [requirement number 9.2.4.2 Page titles, from 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, from 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 Purpose of links (in context), from UNE-EN 301549:2022].
  • Links to related content pages or alternative navigation methods are not always provided [requirement number 9.2.4.5 Multiple pathways, from UNE-EN 301549:2022].
  • There are headings with repeated and/or uninformative text [requirement number 9.2.4.6 Headings and labels, from UNE-EN 301549:2022].
  • The focus location is not always visible when navigating with a keyboard [requirement number 9.2.4.7 Visible focus, from UNE-EN 301549:2022].
  • There are elements that use multipoint or path-based input that cannot be operated with just a pointer or without a path-based gesture [requirement number 9.2.5.1 Pointer gestures, from UNE-EN 301549:2022].
  • There are pages where you cannot cancel an event by clicking the mouse [requirement number 9.2.5.2 Pointer cancellation, from UNE-EN 301549:2022].
  • There are interface components that do not have visible labels [requirement number 9.2.5.3 Name label, from UNE-EN 301549:2022].
  • There is functionality that can only be operated by movement [requirement number 9.2.5.4 Activation by movement, from UNE-EN 301549:2022].
  • Some pages do not indicate the default language used [requirement number 9.3.1.1 Language of the page, from 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 the parties, from UNE-EN 301549:2022].
  • There are components that, when they receive focus, initiate a context change [requirement number 9.3.2.1 Upon receiving focus, from UNE-EN 301549:2022].
  • User interaction with a control causes page changes without prior warning [requirement number 9.3.2.2 Upon receiving input, from 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, from 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, from 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 suggestions in the form for filling in the fields correctly [requirement number 9.3.3.1 Identification of errors, from 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, from UNE-EN 301549:2022].
  • There may be an input error in a field/form for which the user is not notified of a suggestion to resolve it [requirement number 9.3.3.3 Suggestions for errors 333, from UNE-EN 301549:2022].
  • The data entry does not detect errors, nor does it provide the user with an opportunity to correct them [requirement number 9.3.3.4 Error prevention (legal, financial, data), from 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 Processing, from 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, function, 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, from UNE-EN 301549:2022].
  • Some of the WCAG 2.1 requirements are not met [requirement number 9.6 Compliance requirements of the WCAG guidelines, from UNE-EN 301549:2022].
  • Criterion 10 – Requirements for non-web documents: Not applicable.
  • There may be documents with images that do not have an adequate textual alternative [requirement number 10.1.1.1 Non-textual content, from UNE-EN 301549:2022].
  • There may be no equivalent alternative for recorded audio-only or video-only content [requirement number 10.1.2.1 Audio-only and video-only, from UNE-EN 301549:2022].
  • The videos may lack subtitles and audio descriptions [requirement number 10.1.2.2 Subtitles (recorded), from UNE-EN 301549:2022].
  • There may be no alternative for time-dependent media or audio description for video content recorded in synchronized multimedia [requirement number 10.1.2.3 Audio description or alternative media, from UNE-EN 301549:2022].
  • Audio description may not be provided for all video content recorded within synchronized multimedia content [requirement number 10.1.2.5 Audio description (recorded), from UNE-EN 301549:2022].
  • In some documents, the information, structure, and relationships are not determined by software or have no alternative as text [requirement number 10.1.3.1 Information and relationships, from UNE-EN 301549:2022].
  • Some documents do not have at least one correct reading sequence defined by program [requirement number 10.1.3.2 Meaningful sequence, from 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, from UNE-EN 301549:2022].
  • There may be documents whose content does not adapt when changing the screen orientation [requirement number 10.1.3.4 Orientation, from UNE-EN 301549:2022].
  • In some forms, the input field that collects information about the user does not identify its purpose [requirement number 10.1.3.5 Identify the purpose of the input, from UNE-EN 301549:2022].
  • In some documents, color has been used as the sole visual means of conveying information, indicating an action, eliciting a response, or distinguishing a visual element [requirement number 10.1.4.1 Use of color, from 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, from UNE-EN 301549:2022].
  • In some documents, the contrast ratio in text may not be at least 4.5:1 [requirement number 10.1.4.3 Contrast (minimum), from 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 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 Text images, from UNE-EN 301549:2022].
  • In some documents, content may lose functionality or information when enlarged [requirement number 10.1.4.10 Text readjustment, 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 number 10.1.4.11 Contrast of non-textual content, from UNE-EN 301549:2022].
  • In some texts, it is not possible to override the specified text spacing [requirement number 10.1.4.12 Text spacing, from UNE-EN 301549:2022].
  • The content of some documents does not receive keyboard focus with which to perform any action [requirement number 10.1.4.13 Content with hover or focus, from UNE-EN 301549:2022].
  • There are documents that cannot be fully operated using the keyboard [requirement number 10.2.1.1 Keyboard, from UNE-EN 301549:2022].
  • In some documents, headers have not been defined and it is not possible to navigate using the keyboard [requirement number 10.2.1.2 No focus traps, from UNE-EN 301549:2022].
  • In some documents, there are keyboard shortcuts that do not work [requirement number 10.2.1.4 Character key shortcuts, from UNE-EN 301549:2022].
  • Some document establishes a time limitation that cannot be stopped, adjusted, or extended [requirement number 10.2.2.1 Adjustable time, from UNE-EN 301549:2022].
  • Some documents may contain information that moves automatically and does not have controls to pause, control, or hide it [requirement number 10.2.2.2 Pause, stop, and hide, from UNE-EN 301549:2022].
  • Some documents may contain elements that flash more than three times per second or above the general threshold [requirement number 10.2.3.1 Threshold of three flashes or less, from UNE-EN 301549:2022].
  • There may be documents that do not have a title [requirement number 10.2.4.2 Page titles, from UNE-EN 301549:2022].
  • In some documents, headers have not been defined and it is not possible to navigate using the keyboard [requirement number 10.2.4.3 Focus order, from UNE-EN 301549:2022].
  • Some documents may contain links that do not have a specific purpose defined in text form [requirement number 10.2.4.4 Purpose of links (in context), from 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, from UNE-EN 301549:2022].
  • The focus location is not always visible when navigating a document using the keyboard [requirement number 10.2.4.7 Visible focus, from UNE-EN 301549:2022].
  • Some documents may contain elements that use multipoint or path-based controls that cannot be operated with a pointer alone or without a path-based gesture [requirement number 10.2.5.1 Pointer gestures, from UNE-EN 301549:2022].
  • There are documents where an event cannot be canceled by clicking the mouse [requirement number 10.2.5.2 Pointer cancellation, from 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 Name label, from UNE-EN 301549:2022].
  • There are documents whose functionality can only be operated by movement [requirement number 10.2.5.4 Activation by movement, from UNE-EN 301549:2022].
  • There may be documents in which the main language is not identified [requirement number 10.3.1.1 Language of the page, from UNE-EN 301549:2022].
  • There may be content or phrases within some documents whose language cannot be determined by program [requirement number 10.3.2.1 Language of the parties, from UNE-EN 301549:2022].
  • There may be components in a document that, when they receive focus, initiate a context switch [requirement number 10.3.2.1 Upon receiving focus, from UNE-EN 301549:2022].
  • User interaction with a control causes page changes without prior warning [requirement number 10.3.2.2 Upon receiving input, from UNE-EN 301549:2022].
  • There are data entry fields with automatic error detection capabilities that do not identify where or how the error occurs [requirement number 10.3.3.1 Error identification, from UNE-EN 301549:2022].
  • In some forms in some documents, an automatic context change could occur without warning the user [requirement number 10.3.3.2 Labels or instructions, from 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 to correct it [requirement number 10.3.3.3 Suggestions for errors, from UNE-EN 301549:2022].
  • Some documents may contain forms for data collection or that involve legal or financial commitments that are not reversible, reviewable, or confirmed before being sent [requirement number 10.3.3.4 Prevention of errors (legal, financial, data), from UNE-EN 301549:2022].
  • Some documents may contain duplicate attributes and IDs [requirement number 10.4.1.1 Processing, from 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, function, 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, from 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 number 11.7 User preferences, from UNE-EN 301549:2022].
  • The information required for accessibility may not be compatible with the format used for output from the authoring tool [requirement number 11.8.1 Content management technology, from UNE-EN 301549:2022].
  • There may not be a mechanism that allows content to be created in an accessible manner [requirement number 11.8.2 Creation of accessible content, from 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, from UNE-EN 301549:2022].
  • There may not be a repair mechanism for the accessibility verifier [requirement number 11.8.4 Repair service, from UNE-EN 301549:2022].
  • There may be no templates available that are compatible with creating content that complies with the requirements of chapters 9 (Web) or 10 (Non-web documents) [requirement number 11.8.5 Templates, from UNE-EN 301549:2022].
  • Criterion 12 – Requirements applicable to documentation and support services: Not applicable.
  • The product documentation does not list or explain all available accessibility features [requirement number 12.1.1 Accessibility and compatibility features, from UNE-EN 301549:2022].
  • The product documentation may not be fully accessible [requirement number 12.1.2 Accessible documentation, from 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 and compatibility features, from 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, from 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, from UNE-EN 301549:2022].

b. Disproportionate burden: Not applicable.

c. Content not covered by 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. However, every effort has been made to ensure that most of them do comply.
  • 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 pre-recorded files published before September 20, 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 changes in the systems, not all generated or auto-generated content may comply with all accessibility regulations.

Preparation of this accessibility statement

This statement was prepared on 09/26/2025.

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

Last revision of the statement: 09/26/2025

Comments and contact details

You may communicate accessibility requirements (Article 10.2.a of Royal Decree 1112/2018, of September 7), such as:

  • Report any possible non-compliance by this website.
  • Convey other difficulties in accessing content.
  • Submit any other questions or suggestions for improvement regarding the accessibility of the website.

Through the following channels:

  • Email: info@azatranslation.com
  • Phone: 952 118325

In accordance with Article 10.2.b of RD 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 that is excluded from the scope of application of RD 1112/2018 as established by Article 3, Section 4.
    • Content that is exempt from compliance with accessibility requirements because it would impose a disproportionate burden.

In the Request for Accessible Information, the facts, reasons, and request must be clearly specified so that it can be verified that the request is reasonable and legitimate.

Communications will be received and handled by the company’s management, as the unit responsible for the content of this website.

Optional content

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

From that date onwards, partial daily reviews of new or modified web content are carried out, both of templates and of final published pages and documents, in order to ensure compliance with the accessibility requirements of Standard UNE-EN 301549:2022, taking into account 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.
  • The links provide details about the function or destination of the hyperlink.
  • Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.

Compatibility

The website:

  • It has been designed in accordance with current standards and regulations regarding accessibility, 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 for proper viewing on any resolution and device, including desktops, tablets, and mobile phones (responsive design).
  • It has been created using HTML5 as the markup language and CSS 3 style sheets for its design.

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