Accesibilidad
Accessibility statement
This accessibility statement applies to this website.
Compliance status
This website is partially compliant with RD 1112/2018 due to exceptions and the lack of compliance with the aspects indicated in the following point.
Inaccessible content
The content collected below is not accessible for the following reasons:
9.1.3.1 Information and relationships (Conditional)
Condition: When ICT is a web page.
The information, structure, and relationships communicated through the presentation can be determined by software or are available as text.
9.1.3.5 Identification of the purpose of the input (Conditional)
Condition: When ICT is a web page.
The purpose of each input field that collects information about the user can be determined programmatically when:
The input field serves a purpose identified in the input purposes of the user interface components; and
The content is implemented using technologies that support identifying the expected meaning of input data in forms.
9.1.4.3 Contrast (minimum) (Conditional)
Condition: When ICT is a web page.
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
Large text: The text and large-scale text images have a contrast ratio of at least 3:1;
Incidental: Text or images of text that are part of an inactive user interface component, which are purely decorative, not visible to anyone, or part of an image that contains other significant visual content, do not have contrast requirements.
Logos: The text that is part of a logo or brand does not have a minimum contrast requirement.
9.1.4.11 Non-text contrast (Conditional)
Condition: When ICT is a web page.
The visual presentation of the following elements has a contrast ratio of at least 3:1 with respect to adjacent colors:
User interface components: Visual information necessary to identify the components and states of the user interface, except in the case of inactive components or when the appearance of the component is determined by the user agent and not modified by the author;
Graphic objects: Parts of the graphics necessary to understand the content, except when a particular presentation of the graphics is essential to the information being conveyed
9.1.4.13 Content pointed to or focused (Conditional)
Condition: When ICT is a web page.
If the additional content is activated to become visible and then hidden upon receiving and then removing the pointer or keyboard focus, the following is true:
- Can be dismissed: A mechanism is available to dismiss the additional content without moving the pointer or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
- Hoverable: If the pointer can activate the additional content, then the pointer can move over the additional content without the additional content disappearing;
- Persistent: Additional content remains visible until the cursor or focus trigger is removed, the user dismisses it, or its information becomes invalid.
https://www.w3.org/TR/WCAG/#content-on-hover-or-focus
9.2.1.1 Keyboard (Conditional)
Condition: When ICT is a web page.
All functionality of the content is operable through a keyboard interface without requiring a specific speed for each individual key press, except when the internal function requires input that depends on the path of the user's movements and not just on the starting and ending points. (Level A)
Note 1: This exception refers to the underlying function, not the data entry technique. For example, if text input is done by handwriting, the input technique (handwriting) depends on the stroke (traced path) but the internal function (entering text) does not.
Note 2: This does not prohibit or should not discourage authors from providing mouse input or other additional data entry methods to operability through the keyboard. https://www.w3.org/TR/WCAG/#keyboard
9.2.1.2 No traps for keyboard focus (Conditional)
Condition: When ICT is a web page.
If it is possible to move the focus to a component of the page using a keyboard interface, then the focus can be removed from that component using only the keyboard interface and, if something more than the arrow keys or tab key is required, the user is informed of the appropriate method to move the focus. (Level A)
Note: To the extent that any content that does not meet this criterion may interfere with the user's ability to fully use the page, all content on the web page (whether or not it meets other conformance criteria) must meet this criterion. See Conformance Requirement 5: No interference.
Keyboard shortcuts (Conditional)
Condition: When ICT is a web page. In the event that keyboard shortcuts using a single letter, punctuation mark, number, or symbol are used to activate interactive elements (links, buttons, etc.), at least one of the following conditions must be met:
- There is a mechanism that allows disabling the keyboard shortcut
- There is a mechanism that allows reassigning the keyboard shortcut to use another non-printable key (e.g., Ctrl, Alt, etc.)
- The keyboard shortcut can only be activated when the component has keyboard focus.
9.2.4.7 Visible focus (Conditional)
Condition: When ICT is a web page.
Any user interface operable by keyboard has a way of operating in which the keyboard focus indicator is visible. (Level AA)
9.3.3.1 Error identification (Conditional)
Condition: When ICT is a web page.
If an error in data entry is automatically detected, the erroneous element is identified and the error is described to the user through text. (Level A)
9.3.3.2 Labels or instructions (Conditional)
Condition: When ICT is a web page.
Labels or instructions are provided when the content requires user data entry. (Level A)
9.6 Conformity requirements of the WCAG Guidelines (Conditional)
Condition: When ICT is a web page
The following five conformity requirements of the WCAG 2.1 Guidelines must be met at level AA [5]:
- level of conformity;
- complete pages;
- complete processes;
- use of technologies exclusively according to methods that are compatible with accessibility;
- without interference.
NOTE 1: In the event that a web page meets all requirements 9.1 to 9.4 or an alternative version conforming to level AA (as defined in the WCAG 2.1 Guidelines [5]) is provided, conformity requirement 1 will be met.
NOTE 2: According to WC3, "The WCAG 2.1 Guidelines extend the Web Content Accessibility Guidelines 2.0 [4], which were published in Recommendation format by the WWW in December 2008. Content that conforms to the WCAG 2.1 Guidelines also conforms to the WCAG 2.0 Guidelines and, consequently, to policies that reference the WCAG 2.0 Guidelines [4].
NOTE 3: Conformity requirement 5 states that all content on the page, including content that would otherwise not serve as a basis for achieving conformity, meets sections 9.1.4.2, 9.2.1.2, 9.2.2.2, and 9.2.3.1.
11.8.3 Preservation of accessibility information during transformations (Conditional)
Condition: When the web content is an authoring tool.
If the authoring tool provides restructuring or recoding transformations and if there are equivalent mechanisms in the content management technology of the output, then the accessibility information must be preserved in the output.
NOTE 1: Restructuring transformations are transformations in which the content management technology remains the same, while the structural features of the content are modified (for example, linearization tables, dividing the document into pages).
NOTE 2: Recoding transformations are transformations in which the technology used to encode the content changes.
11.8.4 Repair service (Conditional)
Condition: When the web content is an authoring tool.
If the accessibility verification functionality of an authoring tool can detect if the content does not meet a requirement of chapters 9 (Web) or 10 (Non-web documents), as applicable, then the authoring tool must provide a suggestion(s) for its repair.
NOTE: This does not exclude an automatic or semi-automatic repair, which is possible (and recommended) for many types of accessibility issues in the content.
Preparation of this accessibility statement
The method used to prepare the statement has been a self-assessment carried out by the company itself.
Observations and contact details
You can make communications about accessibility requirements (Article 10.2.a of RD 1112/2018) such as, for example:
- Inform about any possible non-compliance by this website
- Report other access difficulties to the content
- Make any other inquiry or suggestion for improvement regarding the accessibility of the website
Through the email address of the legal notice.
You can submit:
- Complaint regarding compliance with the requirements of RD 1112/2018 or
- Accessible Information Request regarding:
Contents that are excluded from the scope of application of RD 1112/2018 as established by Article 3, section 4
Contents that are exempt from meeting accessibility requirements due to imposing a disproportionate burden.
In the Accessible Information Request, the facts, reasons, and request must be clearly specified to verify that it is a reasonable and legitimate request.
Complaints and claims regarding accessible information will be made through the above email.
