Accessibility Statement

Introduction

[Your Company Name] is committed to universal digital accessibility, working continuously to ensure that our digital assets are usable by all people, regardless of their abilities, age, or personal circumstances.

Our Accessibility Statement is based on the latest version of the harmonized European technical standard EN 301 549, which is the European standard for digital accessibility, approved by the European Commission. This standard defines accessibility requirements for technological products and services.

The scope of this statement covers the digital web asset https://www.example.com, excluding embedded content from external domains. However, [Your Company Name] and its external providers actively commit to improving the accessibility of external content included within their digital assets, in order to ensure the most inclusive digital experience possible.

Our goal is to carry out continuous monitoring and correction of potential digital accessibility barriers, with the ultimate aim of offering an inclusive and obstacle-free experience for all users.

Beyond legal compliance, [Your Company Name] aspires to exceed regulatory requirements regarding digital accessibility. Our commitment is to reach the highest accessibility standards, aiming to meet AAA criteria, continuously improve the usability of our digital products, and achieve certifications that endorse our excellence in accessibility.

To achieve this ambitious goal, we have implemented a Comprehensive Digital Accessibility Service (S.I.A.), developing corrective measures that include specialized training for our teams, systems for continuous evaluation and improvement of accessibility, and proactive actions both on our websites and mobile applications, with the ultimate aim of guaranteeing a truly universal and inclusive digital experience.

Adopted Criteria

[Your Company Name] follows the EN 301 549 standard to guarantee the digital accessibility of its digital assets. Some of the features implemented to improve content accessibility are:

  • (7.2.1) Use of video players that include a feature to select and play available audio descriptions.

  • (9.1.1.1) A thorough review of all relevant images is carried out to ensure that they have appropriate alternative text (alt), making visual information accessible to people with visual impairments.

  • (9.1.2.1) Audio-only or visual-only resources are reviewed to ensure that they have equivalent text alternatives such as transcripts or detailed descriptions.

  • (9.1.2.3) The implementation of audio descriptions or alternative means for all recorded videos is considered to ensure that visual content is accessible in other ways.

  • (9.1.2.5) Alternative versions of videos with integrated audio description are prepared, or a second channel is provided to enable them, thus expanding the accessibility of audiovisual content.

  • (9.1.3.1) Structural elements such as headings, field groups, lists, and tables are audited to ensure that visual relationships are correctly reflected in the code.

  • (9.1.3.2) Different presentations of content are reviewed to ensure that the reading order maintains its logical coherence, regardless of the device or format used.

  • (9.1.3.5) Appropriate autocomplete attributes are added to forms to improve the user experience, especially on mobile devices or in assisted access environments.

  • (9.1.4.3) Automatic and manual tools are used to verify that the contrast between text and background meets the minimum required standards to ensure readability.

  • (9.1.4.4) It is verified that content can be enlarged up to 200% using browser functions without loss of functionality or information.

  • (9.1.4.10) All designs are validated to ensure that content adapts correctly to resizing on small screens without the need for horizontal scrolling.

  • (9.1.4.11) It is verified that all graphic elements and non-text controls have sufficient contrast with the background to facilitate visual recognition.

  • (9.2.1.1) The development team adapts all interactive components to guarantee full functionality via keyboard, enabling navigation without the need for a mouse.

  • (9.2.2.2) All automatically moving elements are audited to ensure that they have accessible and visible pause or closing mechanisms.

  • (9.2.4.1) Mechanisms are implemented to allow users to skip repetitive blocks such as menus, facilitating direct access to the main content.

  • (9.2.4.2) Page titles are reviewed to ensure they clearly describe the content and improve orientation within the site.

  • (9.2.4.3) It is verified that the tab order is logical and coherent, allowing sequential navigation that does not alter meaning or operability.

  • (9.2.4.4) Link texts are strengthened so that they are more descriptive by themselves and understandable without additional context.

  • (9.2.4.6) A clear and logical hierarchy is applied to headings and labels to facilitate content comprehension and structured navigation.

  • (9.2.4.7) All interactive elements are reviewed to ensure that the keyboard focus is always visible through clear and high-contrast styles.

  • (9.3.1.2) lang attributes are added to fragments of content that are in a different language than the main one, ensuring correct pronunciation by multilingual screen readers.

  • (9.3.2.1) All interactive elements receiving focus are reviewed to ensure they do not cause unexpected context changes without prior notice.

  • (9.3.3.2) All forms are reviewed to ensure that each field has a clear label or instruction about its purpose.

  • (9.4.1.2) Work is carried out to improve the semantic accessibility of all custom components, ensuring they correctly transmit their role, state, and value to assistive technologies.

  • (9.4.1.3) Correct implementation of ARIA roles and accessible attributes is ensured so that dynamic messages (such as errors, confirmations, or alerts) are detected and announced by screen readers.

  • (9.6) The five conformance principles required by WCAG level AA are guaranteed, ensuring that pages, processes, and technologies used do not interfere with the general accessibility of content.

  • (12.2.4) Documentation provided by support services is available in an accessible format.

  • (10.1.3.1) In documents, information, structure, and relationships are determined by software or have a text alternative.

  • (10.1.3.2) In documents, a correct reading sequence is defined by software.

  • (10.2.1.1) Ensure that in documents, elements correctly receive keyboard focus.

  • (10.2.4.2) Documents include the identified page title.

  • (10.2.4.3) In any document, sequential navigation using the keyboard has a consistent order.

  • (10.2.4.6) Headings and/or control names are sufficiently descriptive of their purpose.

  • (10.2.5.3) Verify that labels accompanying controls always have a distinctive name.

  • (10.3.1.1) In documents, the default language used is indicated.

  • (10.4.1.2) In documents, user interface components such as form elements, links, and script-generated components follow the recommended structure of accessibility guidelines.

Preparation of this Accessibility Statement

This statement was prepared on 29/07/2025.

The method used to prepare the statement was a manual review, based on the requirements of the EN 301 549 standard, carried out by Everycode S.L. on 17/07/2025.

Everycode S.L. has an independent inspection unit accredited by ENAC (Entidad Nacional de Acreditación) according to the requirements of ISO/IEC 17020, for website and mobile application inspection activities under EN 301 549.

Last review of the statement: 29/07/2025

Feedback and Contact Information

We value your active participation in the continuous improvement of our digital accessibility. If you wish to make suggestions, report incidents, or request information about the accessibility of our website, you can contact us through the following channels: