Accessibility statement

Introduction
This website has 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

Due to the above, this website is PARTIALLY COMPLIANT, with the accessibility aspects with which this website complies with 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 Guidance (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 text size (Conditional)
9.1.4.5 Text Images (Conditional)
9.1.4.10 Text readjustment (Conditional)
9.1.4.11 Non-textual contrast (Conditional)
9.1.4.12 Text Spacing (Conditional)
9.1.4.13 Content pointed to by the pointer or having focus (Conditional)
9.2.1.1 Keyboard (Conditional)
9.2.1.2 No cheats for keyboard focus (Conditional)
9.2.1.4 Keyboard Shortcuts (Conditional)
9.2.2.1 Adjustable time (Conditional)
9.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 Ways (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 the tag in the name (Conditional)
9.2.5.4. Motion Activation (Conditional)
9.3.1.1 Page language (Conditional)
9.3.1.2 Language of the parties (Conditional)
9.3.2.1 Upon receiving the focus (Conditional)
9.3.2.2 Upon receipt of entries (Conditional)
9.3.2.3 Consistent Navigation (Conditional)
9.3.2.4 Consistent 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, value (Conditional)
9.4.1.3 Status messages (Conditional)
9.6 WCAG Guidelines Compliance 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 on accessibility and compatibility features
12.2.4 Accessible documentation

Content not accessible

On the contrary, the content of the points listed below are not accessible for the following reasons:

9.1.3.1 Information and relationships (Conditional)
The information, structure, and relationships communicated through the presentation may be determined by software or available as text.
https://www.w3.org/TR/WCAG/#info-and-relationships

9.1.3.5 Identification of the purpose of the entry (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
– 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 Avoid 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 Error identification (Conditional)
If an error is automatically detected in data entry, the erroneous 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 checking functionality of an authoring tool can detect that the content of a web page or electronic document does not comply with the requirements of Chapter 9 or 10 respectively (i.e., WCAG 2.1 Level AA) the authoring tool Author should provide repair suggestions. This does not preclude automated and semi-automated 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 May 6, 2024

The method used to prepare the declaration has been through self-analysis following the interpretation of the information guidance provided by the WCAG 2.1 AA guidelines. In this continued effort to remove barriers and will continue to improve this site until optimal accessibility and usability is achieved for all users.

Last revision of the declaration: May 6, 2024

Observations and contact information

If you encounter access barriers or problems with any page or function of this website that may represent an obstacle for visitors who want to access it, you can contact us at any time at the email address dominioromano@dominioromano.com