Accesibilidad
Accessibility statement
This accessibility statement applies to this website.
Compliance status
This website is partially compliant with RD 1112/2018 due to the exceptions and lack of conformity of the aspects indicated in the following point.
Content not accessible
The content collected below is not accessible due to the following:
9.1.3.1 Information and relationships (Conditional)
Condition: When the ICT is a web page.
The information, structure and relationships communicated through the presentation may be determined by software or available as text.
9.1.3.5 Identification of the purpose of the entry (Conditional)
Condition: When the 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
- Content is implemented using technologies with support for identifying the expected meaning of input data in forms.
9.1.4.13 Content pointed to by the pointer or having focus (Conditional)
Condition: When the ICT is a web page.
If receiving and then removing keyboard pointer or focus triggers additional content to become visible and then hidden, the following is true:
Can be removed: A mechanism is available to discard additional content without moving the keyboard pointer or focus, unless the additional content communicates an input error or does not obscure or replace other content;
Hoverable: If the pointer can activate the extra content, then the pointer can move over the extra content without the extra 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 the ICT is a web page.
All content functionality is operable through a keyboard interface without requiring a specific speed for each individual key press, except when the internal function requires an input that depends on the path of the user's movements and not only of the start and end points. (Level A)
Note 1: This exception refers to the underlying function, not the data entry technique. For example, if text entry is done by handwriting, the input technique (handwriting) depends on the stroke (traced path) but the internal function (enter text) does not.
Note 2: This does not prohibit and should not discourage authors from providing mouse input or other data entry methods in addition to keyboard operability. https://www.w3.org/TR/WCAG/#keyboard
9.2.1.2 No cheats for keyboard focus (Conditional)
Condition: When the ICT is a web page.
If it is possible to move focus to a component on the page using a keyboard interface, then focus can be removed from that component using only the keyboard interface and, if something other than the arrow or tab keys is required, informs the user of the appropriate method for moving 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 site, all content on the website (whether or not it meets other success criteria) must satisfy this criterion. See Compliance Requirement 5: No Interference.
9.2.1.4 Keyboard Shortcuts (Conditional)
Condition: When the ICT is a web page. In the event that keyboard shortcuts using a single letter, punctuation mark, number or symbol are used to activate interaction elements (links, buttons, etc.), then at least one of the following conditions must be met:
There is a mechanism that allows you to disable the keyboard shortcut
There is a mechanism that allows you to reassign the keyboard shortcut to use another non-printable key instead (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 the ICT is a web page.
Any keyboard-operable user interface has a way of operating in which the keyboard focus indicator is visible. (AA Level)
9.3.3.1 Error identification (Conditional)
Condition: When the ICT is a web page.
If an error is automatically detected in data entry, the erroneous element is identified and the error is described to the user in text. (Level A)
9.3.3.2 Labels or instructions (Conditional)
Condition: When the ICT is a web page.
Labels or instructions are provided when the content requires user input. (Level A)
9.6 WCAG Guidelines Compliance Requirements (Conditional)
Condition: When the ICT is a web page
The following five WCAG Guidelines 2.1 conformance requirements [5] must be satisfied at level AA:
- compliance level;
- full 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 is provided conforming to level AA (as defined in WCAG Guidelines 2.1 [5]), conformance requirement 1 will be met.
NOTE 2: According to WC3, “The WCAG 2.1 Guidelines expand on the Web Content Accessibility Guidelines 2.0 [4], which were published in WWW Recommendation format in December 2008. Content that conforms to the WCAG 2.1 Guidelines also They are with the WCAG 2.0 Guidelines and, consequently, with the policies that refer to the WCAG 2.0 Guidelines [4].
NOTE 3: Compliance requirement 5 states that all content on the page, including content that would not otherwise serve as a basis for compliance, complies with 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 equivalent mechanisms exist in the content management technology of the output, then 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 characteristics of the content are modified (for example, linearization tables, division of 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 checking functionality of an authoring tool can detect if content does not meet a requirement of Chapters 9 (Web) or 10 (Non-Web Documents), as applicable, then the authoring tool must provide an ) suggestion(s) for repair.
NOTE: This does not preclude automatic or semi-automatic repair, which is possible (and recommended) for many types of content accessibility issues.
Preparation of this accessibility statement
The method used to prepare the declaration has been a self-assessment carried out by the company itself.
Observations and contact information
You can make communications about accessibility requirements (article 10.2.a of RD 1112/2018) such as, for example:
- Report any possible breach by this website
- Transmit other content access difficulties
- Ask any other questions or suggestions for improvement regarding the accessibility of the website
Through the email address in the legal notice.
You can present:
- Complaint regarding compliance with the requirements of RD 1112/2018 or
- Request for accessible information related to:
Contents that are 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 imposes a disproportionate burden.
In the Request for accessible information, the facts, reasons and request must be clearly specified that allow us to verify that it is a reasonable and legitimate request.
Complaints and claims about accessible information will be made through the previous email.
