favicon warnachy

Accessibility

wanarchy.es

Compliance Status

Wanarchy (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 listed below.

Content not accessible

The content 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-compliant means may be required to activate certain accessibility features [Requirement 5.2, “Activation of Accessibility Features,” of 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 7000 Hz [Requirement 6.1, “Bandwidth for voice,” of UNE-EN 301549:2022].
  • It may not be possible to provide two-way communication via RTT [requirement 6.2.1.1 Communication via RTT, of UNE-EN 301549:2022].
  • It may not be possible to provide simultaneous two-way voice and text communication [Requirement 6.2.1.2, “Simultaneous Voice and Text,” of UNE-EN 301549:2022].
  • It may not clearly distinguish between sent and received text in RTT communications [Requirement 6.2.2.1, “Visually distinguishable on-screen display,” of UNE-EN 301549:2022].
  • It may not be possible to determine the RTT transmission and reception addresses via software [requirement 6.2.2.2, “Transmission and reception addresses determinable via software,” of UNE-EN 301549:2022].
  • Speaker identification via RTT may not be possible [requirement 6.2.2.3, “Speaker Identification,” of UNE-EN 301549:2022].
  • There may not be a visual indicator on the screen showing real-time audio activity [Requirement 6.2.2.4: Visual audio indicator with real-time text, from UNE-EN 301549:2022].
  • We may not be able to guarantee compatibility with other systems that support RTT functionality [Requirement 6.2.3 Interoperability, of UNE-EN 301549:2022].
  • It may not be possible to guarantee that the RTT input is transmitted to the network within 500 ms [Requirement 6.2.4, RTT Response Time, of UNE-EN 301549:2022].
  • A non-voice alternative for performing assistance or interactive response tasks may not be provided [Requirement 6.4, Alternatives to voice-based services, of UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum resolution of QVGA for video features [requirement 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 6.5.3 Frame Rate, of UNE-EN 301549:2022].
  • The maximum delay of 100 ms between the presentation of audio and video to the user must not be exceeded [Requirement 6.5.4, Audio and Video Synchronization, of UNE-EN 301549:2022].
  • There may not be a method for speaker identification for sign language users in real time [Requirement 6.5.6: Speaker Identification in Video Communication, from UNE-EN 301549:2022].
  • Criterion 7 – Video capability: Not applicable.
  • There may be some video players that do not have a mode of operation that allows existing subtitles to be displayed [Requirement 7.1.1, Subtitle Playback, of UNE-EN 301549:2022].
  • There may be some video players that do not have a mode of operation that allows the audio to be synchronized with the subtitles [Requirement 7.1.2, “Subtitle Synchronization,” of UNE-EN 301549:2022].
  • There may be some video players that do not have a system for saving subtitles [Requirement 7.1.3, Preservation of Subtitles, of UNE-EN 301549:2022].
  • Users may not be able to customize the subtitle settings to meet their individual needs [Requirement 7.1.4, “Subtitle Settings,” of UNE-EN 301549:2022].
  • An operating mode that provides spoken output of available captions may not be provided in all cases [Requirement 7.1.5, Spoken Captions, of UNE-EN 301549:2022].
  • There may be some media players that do not include a feature for selecting and playing available audio descriptions [Requirement 7.2.1: Audio Description Playback, of UNE-EN 301549:2022].
  • There may be some media players that do not include a feature for synchronizing available audio descriptions [Requirement 7.2.2, “Synchronization of Audio Description,” of UNE-EN 301549:2022].
  • Some media players may not include a feature to save available audio descriptions [Requirement 7.2.3, Preservation of Audio Description, of UNE-EN 301549:2022].
  • Some web pages include a video player that does not provide controls for subtitles and audio description with the same level of interactivity as the other controls [Requirement 7.3: User controls for subtitles and audio description, from UNE-EN 301549:2022].
  • Criterion 9 – Requirements for websites: Not applicable.
  • There is non-textual content that lacks a text alternative, or that has an inadequate text alternative [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 include captions [Requirement 9.1.2.2 Captions (recorded), of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not include audio description or alternative media [requirement 9.1.2.3, “Audio Description or Alternative Media,” of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not include audio description or alternative formats [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-based alternative [requirement 9.1.3.1 Information and Relationships, of UNE-EN 301549:2022].
  • Some pages do not have at least one valid reading sequence defined by the program [Requirement 9.1.3.2, “Meaningful Sequence,” of UNE-EN 301549:2022].
  • Identification of elements based solely on 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 adjust when the screen orientation changes [Requirement 9.1.3.4 Orientation, of UNE-EN 301549:2022].
  • There are form fields for which the purpose of the input is not specified [requirement 9.1.3.5, “Identify the purpose of the 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, from 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 meet the minimum requirement of 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 the ability to adjust it when zooming [requirement 9.1.4.4 Text resizing, from UNE-EN 301549:2022].
  • There are text-only clipart images [requirement 9.1.4.5 Text Images, of UNE-EN 301549:2022].
  • Errors occur when adjusting the font size, zoom level, or text spacing [Requirement 9.1.4.10 Text Adjustment, of UNE-EN 301549:2022].
  • Insufficient contrast in interface components or graphic objects [Requirement 9.1.4.11, “Contrast of Non-Textual Content,” of UNE-EN 301549:2022].
  • There is text that does not display correctly when the spacing and line heights are changed [Requirement 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 shifting the mouse focus [Requirement 9.1.4.13: Content with hover or focus, from UNE-EN 301549:2022].
  • There are websites where keyboard navigation is not optimal and errors occur [Requirement 9.2.1.1 Keyboard, from UNE-EN 301549:2022].
  • There are components that, when the focus is on them, prevent it from being moved to another element using only the Tab key or arrow keys [Requirement 9.2.1.2: No focus traps, from UNE-EN 301549:2022].
  • There are keyboard shortcuts that do not work [Requirement 9.2.1.4: Shortcuts using character keys, from UNE-EN 301549:2022].
  • There is a time limit in place that cannot be paused, adjusted, or extended [Requirement 9.2.2.1 Adjustable Time, of UNE-EN 301549:2022].
  • Some automatically scrolling content may not include controls for pausing, controlling, or hiding it [Requirement 9.2.2.2: Pause, Stop, and Hide, of UNE-EN 301549:2022].
  • There may be elements that flash more than three times per second or exceed the general threshold [Requirement 9.2.3.1, “Threshold of three flashes or fewer,” of UNE-EN 301549:2022].
  • Some pages lack the mechanism to omit blocks of content that are repeated on multiple pages [requirement 9.2.4.1, “Avoid blocks,” of UNE-EN 301549:2022].
  • Inadequate descriptions of some webpage titles [Requirement 9.2.4.2: Page Titles, of UNE-EN 301549:2022].
  • In some documents, sequential navigation using the keyboard 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 pages with related content 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 position is not always visible when navigating with the keyboard [requirement 9.2.4.7, “Visible Focus,” of UNE-EN 301549:2022].
  • There are elements that use multi-touch or are route-based and cannot be operated using only a pointer or without a route-based gesture [requirement 9.2.5.1, “Pointer Gestures,” of UNE-EN 301549:2022].
  • There are pages where you cannot cancel an event by clicking the mouse [requirement 9.2.5.2, “Cancelation of the pointer,” 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 are functions that can only be operated by motion [requirement 9.2.5.4, “Activation by motion,” of UNE-EN 301549:2022].
  • Some pages do not specify the default language used [requirement 9.3.1.1, “Language of the page,” of UNE-EN 301549:2022].
  • There may be occasional errors in editing or language identification in certain parts of the website [Requirement 9.3.1.2 Language of the parts, of UNE-EN 301549:2022].
  • There are components that, when they receive focus, trigger a context switch [Requirement 9.3.2.1, “Upon receiving focus,” of UNE-EN 301549:2022].
  • User interaction with a control causes the page to change without prior warning [Requirement 9.3.2.2, “Upon Receipt of Input,” of UNE-EN 301549:2022].
  • There may be pages with inconsistent navigation due to different links leading 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 using different visual styles [Requirement 9.3.2.4, “Consistent Identification,” of UNE-EN 301549:2022].
  • There are error messages that lack clarity, or error messages that are not consolidated into a single message, as well as a lack of form prompts to help users fill in the fields correctly [Requirement 9.3.3.1, Error Identification, of UNE-EN 301549:2022].
  • There are forms with required fields where users are not informed of this, as well as fields where a textual example of the field format is missing [requirement 9.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • There may be an input error in a field or form for which the user is not notified of a suggestion for resolving it [Requirement 9.3.3.3, Error Messages 333, of UNE-EN 301549:2022].
  • The system does not detect errors during data entry, nor does it provide the user with an opportunity to correct them [Requirement 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 9.4.1.1 Processing, 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 9.4.1.2, “Name, Function, Value,” of UNE-EN 301549:2022].
  • On some pages, status messages may not be programmatically defined using functions or properties [Requirement 9.4.1.3 Status Messages, of UNE-EN 301549:2022].
  • Some of the WCAG 2.1 requirements are not met [Requirement 9.6: Conformity Requirements for WCAG Guidelines, from UNE-EN 301549:2022].
  • Criterion 10 – Requirements for non-web documents: Not applicable.
  • There may be documents containing images that do not have an adequate text alternative [Requirement 10.1.1.1, Non-textual content, of UNE-EN 301549:2022].
  • There may be no equivalent alternative for recorded audio-only or video-only content [Requirement 10.1.2.1 Audio-only and video-only, of UNE-EN 301549:2022].
  • The videos may lack captions and audio descriptions [requirement 10.1.2.2 Captions (recorded), of UNE-EN 301549:2022].
  • There may be no alternative for time-dependent media or audio description for video content recorded in synchronized multimedia [requirement 10.1.2.3 Audio Description or Alternative Media, of UNE-EN 301549:2022].
  • Audio description may not be provided for all video content recorded 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 do not have a text-based alternative [Requirement 10.1.3.1 Information and Relationships, of UNE-EN 301549:2022].
  • Some documents do not have at least one valid reading sequence defined by the program [Requirement 10.1.3.2, “Meaningful Sequence,” of UNE-EN 301549:2022].
  • There may be documents for which there is no other accessible alternative available to use and understand the content [Requirement 10.1.3.3, Sensory Characteristics, of UNE-EN 301549:2022].
  • There may be documents whose content does not display properly when the screen orientation is changed [Requirement 10.1.3.4 Orientation, of UNE-EN 301549:2022].
  • In some forms, the input field that collects user information does not specify its purpose [requirement 10.1.3.5, “Identify the purpose of the input,” 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 a document 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 text contrast ratio may not meet the minimum requirement of 4.5:1 [Requirement 10.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].
  • In some texts, the text size cannot be increased by up to 200 percent without losing content or functionality, and in some documents, the content may lose functionality or information when enlarged [Requirement 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 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 a ratio of 3:1 with adjacent colors [Requirement 10.1.4.11, “Contrast of Non-Textual Content,” of UNE-EN 301549:2022].
  • In some documents, it is not possible to override the specified text spacing [Requirement 10.1.4.12 Text Spacing, of UNE-EN 301549:2022].
  • The content of some documents does not receive keyboard focus, preventing users from performing any actions [Requirement 10.1.4.13: Content with hover or focus, from UNE-EN 301549:2022].
  • There are documents that cannot be fully operated using only the keyboard [Requirement 10.2.1.1 Keyboard, of UNE-EN 301549:2022].
  • In some documents, headings have not been defined, and users cannot navigate using the keyboard [requirement 10.2.1.2, “No focus traps,” of UNE-EN 301549:2022].
  • In some documents, certain keyboard shortcuts do not work [Requirement 10.2.1.4: Character Key Shortcuts, from UNE-EN 301549:2022].
  • Some documents specify a time limit that cannot be paused, adjusted, or extended [Requirement 10.2.2.1 Adjustable Time, of UNE-EN 301549:2022].
  • Some documents may contain automatically scrolling content that lacks controls for pausing, controlling, or hiding it [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 per second or exceed the general threshold [Requirement 10.2.3.1, “Threshold of three flashes or fewer,” of UNE-EN 301549:2022].
  • There may be documents that do not have a title [Requirement 10.2.4.2, “Page Titles,” of UNE-EN 301549:2022].
  • In some documents, headings have not been defined, and users cannot navigate using the keyboard [requirement 10.2.4.3 Focus Order, of UNE-EN 301549:2022].
  • Some documents may contain links whose specific purpose is not explicitly stated in the text [Requirement 10.2.4.4 Purpose of links (in context), of UNE-EN 301549:2022].
  • Some documents may contain a heading or control label that is not sufficiently descriptive of its purpose [Requirement 10.2.4.6, Headings and Labels, of UNE-EN 301549:2022].
  • The focus position is not always visible when navigating a document using the keyboard [Requirement 10.2.4.7, “Visible Focus,” of UNE-EN 301549:2022].
  • Some documents may contain elements that use multi-touch or are route-based and cannot be operated using only a pointer or without a route-based gesture [Requirement 10.2.5.1, “Pointer Gestures,” of UNE-EN 301549:2022].
  • There are documents in which an event cannot be canceled by clicking the mouse [requirement 10.2.5.2, “Cancelation of the pointer,” of UNE-EN 301549:2022].
  • There are documents in which some labels accompanying the controls do not have the same name [Requirement 10.2.5.3, “Name Label,” of UNE-EN 301549:2022].
  • There are devices that can only be operated by motion [requirement 10.2.5.4, “Activation by motion,” of UNE-EN 301549:2022].
  • There may be documents in which the primary language is not identified [Requirement 10.3.1.1, “Language of the page,” of UNE-EN 301549:2022].
  • Some documents may contain content or phrases whose language cannot be determined by the software [Requirement 10.3.2.1 Language of the parts, of UNE-EN 301549:2022].
  • There may be components in a document that, when they receive focus, trigger a context switch [Requirement 10.3.2.1, “Upon receiving focus,” of UNE-EN 301549:2022].
  • User interaction with a control causes the page to change without prior warning [Requirement 10.3.2.2, “Upon Receipt of Inputs,” 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 a form within a document, an automatic context change could occur without notifying the user [Requirement 10.3.3.2, “Labels or Instructions,” of UNE-EN 301549:2022].
  • A document may contain an input error in a field or form for which the user was not notified of a suggestion to resolve it [Requirement 10.3.3.3, “Error Handling,” of UNE-EN 301549:2022].
  • Some documents may contain forms for data collection or forms that entail legal or financial obligations that cannot be reversed, revised, or confirmed 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].
  • 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 10.4.1.2: Name, Function, Value, of UNE-EN 301549:2022].
  • In some documents, status messages may not be programmatically defined through 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 user display preferences are not honored 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 output by the authoring tool [Requirement 11.8.1, Content Management Technology, of UNE-EN 301549:2022].
  • There may not be a mechanism that allows for the creation of accessible content [Requirement 11.8.2: Creation of Accessible Content, from UNE-EN 301549:2022].
  • There is 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 not be a correction mechanism in the accessibility checker [Requirement 11.8.4, Correction Service, of UNE-EN 301549:2022].
  • There may not be any templates available that support the creation of content in accordance with the requirements of Chapter 9 (Web) or Chapter 10 (Non-Web Documents) [Requirement 11.8.5 Templates, of UNE-EN 301549:2022].
  • Criterion 12 – Requirements for 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 Compatibility,” 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 regarding accessibility features included in the product documentation [Requirement 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 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. Undue burden: Not applicable.

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

  • There may be office documents in PDF and other formats published before September 20, 2018, that do not fully meet all accessibility requirements. However, every effort has been made to ensure that most of them do meet these requirements.
  • There may be third-party content that is not developed by this Unit or under its control, such as images, interactive maps, videos, documents, media 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 have been created using 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 standards.

Preparation of this accessibility statement

This statement was prepared on March 5, 2026

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

Last revision of the statement: March 5, 2026

Comments and contact information

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

  • Please report any potential violations by this website.
  • Report other difficulties accessing the content.
  • Please submit any other questions or suggestions for improvement regarding the website’s accessibility.

Through the following channels:

  • Email: info@wanarchy.es
  • Phone: +34 881 253 666

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

  • A complaint regarding compliance with the requirements of Royal Decree 1112/2018.
  • A request for accessible information regarding:
    • Content that is excluded from the scope of application of Royal Decree 1112/2018, as established in Article 3, paragraph 4.
    • Content that is exempt from compliance with accessibility requirements because it would impose a disproportionate burden.

The request for accessible information must clearly specify the facts, reasons, and request that demonstrate that the request is reasonable and legitimate.

Communications will be received and handled by company management, which is responsible for the content of this website.

Optional content

The version of this website currently displayed is dated March 5, 2026, and the accessibility review was conducted on that date based on the standards in effect at that time.

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

Among other measures, the following steps are being taken to improve accessibility:

  • Using alt text for 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 accessibility standards and regulations, meeting the Priority 2 (AA) success criteria 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
  • is designed to display properly on any resolution and on any device, including desktops, tablets, and mobile phones (responsive design)
  • It was created using HTML5 as the markup language and CSS3 for styling.

In addition, we continuously audit and review content to make it easier to understand and improve navigation on the website.