Introduction
This website is committed to making content accessible in accordance with the accessibility criteria of the Digital Kit Program, in accordance with the annexes of the UNE-EN 301 549:2022 standard.
Compliance status
The web technologies on which the accessibility compliance of this site is based are HTML5 , CSS , WAI-ARIA , DOM as well as OTHER technologies of the WordPress platform url: https://wordpress.org
In view of the foregoing, this website is PARTIALLY COMPLIANT, the accessibility aspects with which this website is compliant being the following:
Web requirements:
9.1.1.1 Non-textual 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 Text resizing (Conditional)
9.1.4.5 Text images (Conditional)
9.1.4.10 Text Reset (Conditional)
9.1.4.11 Non-textual contrast (Conditional)
9.1.4.12 Text Spacing (Conditional)
9.1.4.13 Pointed or focused content (Conditional)
9.2.1.1 Keypad (Conditional)
9.2.1.2 No traps for keyboard focus (Conditional)
9.2.1.4 Keyboard shortcuts (Conditional)
9.2.2.1 Adjustable time (Conditional)
9.2.2.2.2 Pause, stop, hide (Conditional)
9.2.3.1 Threshold of three flashes or less (Conditional)
9.2.4.2 Page Titling (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 Headers and labels (Conditional)
9.2.4.7 Visible focus (Conditional)
9.2.5.1 Pointer gestures (Conditional)
9.2.5.2 Pointer cancellation (Conditional)
9.2.5.3 Inclusion of tag in name (Conditional)
9.2.5.4. Activation by motion (Conditional)
9.3.1.1 Language of page (Conditional)
9.3.1.2 Language of parts (Conditional)
9.3.2.1 On receiving focus (Conditional)
9.3.2.2 On receiving input (Conditional)
9.3.2.3 Consistent navigation (Conditional)
9.3.2.4 Consistent identification (Conditional)
9.3.3.3.2 Labels or instructions (Conditional)
9.3.3.3.3 Error hints (Conditional)
9.3.3.4 Error prevention (legal, financial, data) (Conditional)
9.4.1.1 Processing (Conditional)
9.4.1.2 Name, function, value (Conditional)
9.4.1.3 Status messages (Conditional)
9.6 WCAG conformance requirements (Conditional)
Software requirements
11.7 User Preferences
11.8.1 Content Management Technology (Conditional)
11.8.2 Creating Accessible Content (Conditional)
11.8.3 Preserving 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 Accessibility and compatibility features information
12.2.4 Accessible documentation
Content not accessible
However, the content of the items listed below is not accessible for the following reasons:
9.1.3.1 Information and Relationships (Conditional)
The information, structure and relationships communicated through the presentation can be determined by software or are available as text.
https://www.w3.org/TR/WCAG/#info-and-relationships
9.1.3.5 Input Purpose Identification (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 in the input purposes of the user interface components, and
–
The content is implemented using technologies with support for identifying the expected meaning of input data in forms.
https://www.w3.org/TR/WCAG/#identify-input-purpose
9.2.4.1 Block Avoidance (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 Error identification (Conditional)
If an error is automatically detected in the data entry, the erroneous element is identified and the error is described to the user by means of a text (Level A)
https://www.w3.org/TR/WCAG/#error-identification
11.8.4 Repair Service (Conditional)
If the accessibility checking functionality of an authoring 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. WCAG 2.1 level AA) the authoring tool shall provide repair suggestions. This does not exclude automatic and semi-automated repair, which is possible (and recommended) for many types of content accessibility problems.
12.2.3 Effective communication
The support service shall meet the needs of persons with disabilities, either directly or through a point of reference.
Preparation of this accessibility statement
This statement was prepared on May 15, 2025.
The method used to prepare the statement has been by self-analysis following the interpretation of the informative guidance provided by the WCAG 2.1 AA guidelines. In this ongoing effort to remove barriers and will continue to improve this site to achieve optimal accessibility and usability for all users.
Last revision of the statement: May 15, 2025
Remarks and contact information
If you encounter barriers to access or problems with any page or function of this website that may be an obstacle to visitors seeking access, you may contact us at any time at teideled@gmail.com.
