Accessibility statement
Introduction
This website is committed to making content accessible in accordance with the accessibility criteria of the Digital Kit Programme, in accordance with the annexes to the UNE-EN 301 549:2022 standard.
Compliance status
The web technologies on which the conformance of the accessibility of this site is based are HTML5, CSS, WAI-ARIA, ECMAScript 5, DOM as well as OTHER technologies of the WordPress platform url: https://wordpress.org
Due to the foregoing, this website is PARTIALLY COMPLIANT, being the accessibility aspects with which this website conforms the following:
Web requirements:
9.1.1.1 Non-text content (Conditional)
9.1.2.1 Audio Only and Video Only (Recorded) (Conditional)
9.1.2.2 Subtitles (recorded) (Conditional)
9.1.2.3 Audio description or Alternative Media (recorded) (Conditional)
9.1.2.5 Audio description (recorded) (Conditional)
9.1.3.2 Significant sequence (Conditional)
9.1.3.3 Sensory characteristics (Conditional)
9.1.3.4 Orientation (Conditional)
9.1.4.1 Use of Color (Conditional)
9.1.4.2 Audio Control (Conditional)
9.1.4.3 Contrast (Minimum) (Conditional)
9.1.4.4 Changing (Conditional) Text Size
9.1.4.5 Text images (Conditional)
9.1.4.10 Text readjustment (Conditional)
9.1.4.11 Non-text contrast (Conditional)
9.1.4.12 Text spacing (Conditional)
9.1.4.13 Pointed or focused-out content (Conditional)
9.2.1.1 Keyboard (Conditional)
9.2.1.2 No Keyboard Focus Traps (Conditional)
9.2.1.4 Keyboard shortcuts (Conditional)
9.2.2.1 Adjustable (Conditional) Time
9.2.2.2 Pause, Stop, Hide (Conditional)
9.2.3.1 Threshold of three flashes or less (Conditional)
9.2.4.2 Page titles (Conditional)
9.2.4.3 Focus order (Conditional)
9.2.4.4 Purpose of links (in context) (Conditional)
9.2.4.5 Multiple Pathways (Conditional)
9.2.4.6 Headings and Labels (Conditional)
9.2.4.7 Focus Visible (Conditional)
9.2.5.1 Pointer gestures (Conditional)
9.2.5.2 Pointer cancellation (Conditional)
9.2.5.3 Include the tag in the name (Conditional)
9.2.5.4. Activation by movement (Conditional)
9.3.1.1 Page language (Conditional)
9.3.1.2 Language of the parties (Conditional)
9.3.2.1 Upon receiving focus (Conditional)
9.3.2.2 Upon receiving tickets (Conditional)
9.3.2.3 Consistent (Conditional) Navigation
9.3.2.4 Coherent identification (Conditional)
9.3.3.2 Labels or instructions (Conditional)
9.3.3.3 Error Suggestions (Conditional)
9.3.3.4 Error prevention (legal, financial, data) (Conditional)
9.4.1.1 Processing (Conditional)
9.4.1.2 Name, Function, (Conditional) Value
9.4.1.3 Status Messages (Conditional)
9.6 WCAG Guidelines Conformance Requirements (Conditional)
Software requirements
11.7 User preferences
11.8.1 Content Management Technology (Conditional)
11.8.2 Creation of accessible content (Conditional)
11.8.3 Preservation of accessibility information during transformations (Conditional)
11.8.5 Templates (Conditional)
Documentation requirements and support services
12.1.1 Accessibility and Compatibility Features
12.1.2 Accessible documentation
12.2.2 Information about accessibility and compatibility features
12.2.4 Accessible documentation
Non-accessible content
However, the content of the points listed below is not accessible for the following reasons:
9.1.3.1 Information and relationships (Conditional)
The information, structure, and relationships communicated through presentation can be determined by software or are available as text.
https://www.w3.org/TR/WCAG/#info-and-relationships
9.1.3.5 Identification of the purpose of the input (Conditional)
The purpose of each input field that collects information about the user can be determined programmatically when:
– The input field serves an identifying purpose for the input purposes of user interface components, and
– Content is implemented using supported technologies to identify the expected meaning of input data to forms.
https://www.w3.org/TR/WCAG/#identify-input-purpose
9.2.4.1 Avoiding blocks (Conditional)
There is a mechanism to avoid blocks of content that are repeated on multiple web pages (Level A)
https://www.w3.org/TR/WCAG/#bypass-blocks
9.3.3.1 Identification of errors (Conditional)
If you automatically detect an error in the data entry, the wrong element is identified and the error is described to the user using text (Level A)
https://www.w3.org/TR/WCAG/#error-identification
11.8.4 Repair Service (Conditional)
If the accessibility verification functionality of an author tool can detect that the content of a web page or electronic document does not meet the requirements of chapter 9 or 10 respectively (i.e., level AA of WCAG 2.1), the author tool must provide repair suggestions. This does not exclude semi-automated and auto-repair, which is possible (and recommended) for many types of content accessibility issues.
12.2.3 Effective communication
The support service must meet the needs of people with disabilities, either directly or through a reference point.
Preparation of this accessibility statement
This statement was prepared on June 3, 2024
The method used to prepare the statement was through self-analysis following the interpretation of the information guide provided by the WCAG 2.1 AA guidelines. In this continuous effort to remove barriers and will continue to improve this site until achieving optimal accessibility and usability for all users
Last revision of the statement: June 3, 2024
Observations and contact details
If you encounter access barriers or problems with any page or feature of this website that may hinder visitors who wish to access it, you can contact us at any time at the email address
silumin@silumin.es
