Accessibility Statement

Tecvinser SL is committed to making the content of this website accessible in accordance with the accessibility criteria of the Digital Kit Program, following the UNE-EN 301 549:2022 standard.

This accessibility statement applies to the website https://www.tecvinser.com/.

1. Compliance Status

The web technologies on which this site’s accessibility compliance is based include HTML5, CSS, WAI-ARIA, DOM, and other WordPress platform technologies, URL: https://wordpress.org.
Therefore, this website is PARTIALLY COMPLIANT, and the aspects of accessibility with which this website complies are as follows:

Web Requirements Software Requirements Documentation and Support Services Requirements
9.1.1.1 Non-text Content
9.1.2.1 Audio-only and Video-only (Prerecorded)
9.1.2.2 Captions (Prerecorded)
9.1.2.3 Audio Description or Media Alternative (Prerecorded)
9.1.2.5 Audio Description (Prerecorded)
9.1.3.1 Information and Relationships
9.1.3.2 Meaningful Sequence
9.1.3.3 Sensory Characteristics
9.1.3.4 Orientation
9.1.3.5 Identify Input Purpose
9.1.4.1 Use of Color
9.1.4.2 Audio Control
9.1.4.3 Contrast (Minimum)
9.1.4.4 Resize Text
9.1.4.5 Images of Text
9.1.4.10 Reflow
9.1.4.11 Non-text Contrast
9.1.4.12 Text Spacing
9.1.4.13 Pointer or Target at Input
9.2.2.1 Keyboard
9.2.1.2 No Keyboard Trap
9.2.1.4 Keyboard Shortcuts
9.2.2.1 Timing Adjustable
9.2.3.1 Three Flashes or Below Threshold
9.2.4.2 Page Titled
9.2.4.3 Focus Order
9.2.4.4 Link Purpose (In Context)
9.2.4.6 Headings and Labels
9.2.5.1 Pointer Gestures
9.2.5.2 Pointer Cancellation
9.2.5.3 Label in Name
9.2.5.4 Motion Actuation
9.3.1.1 Language of Page
9.3.1.2 Language of Parts
9.3.2.1 On Input
9.3.2.2 On Change
9.3.2.3 Consistent Navigation
9.3.2.4 Consistent Identification
9.3.3.1 Error Identification
9.3.3.2 Labels or Instructions
9.3.3.3 Error Suggestion
9.3.3.4 Legal, Financial, Data Errors Prevention
9.4.1.1 Parsing		 11.8.1 Content Management Technology
11.8.2 Accessible Authoring Practices
11.8.3 Accessibility Information Preservation During Transformations
11.8.5 Templates		 12.1.1 Accessibility Features and Compatibility
12.1.2 Accessible Documentation
12.2.2 Information about Accessibility Features and Compatibility
12.2.3 Effective Communication
12.2.4 Accessible DocumentationValue

3. Non-accessible Content

The following content is not accessible for the following reasons:

  • Non-compliance with RD 1112/2018

    9.2.2.2 Pause, Stop, Hide

    Condition: When ICT is a web page.
    For information that has motion, flickering, scrolling, or automatically updating, the following cases are met: (Level A)

    • For all moving, flickering, or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for users to pause, stop, or hide it unless the motion, flickering, or scrolling is essential to an activity.
    • Automatic update: For all automatically updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for users to pause, stop, hide, or control the frequency of the update, unless the update is part of an activity where it is essential.NOTE
      For requirements related to flashing content, refer to Guideline 2.3.NOTE
      Since any content that fails this success criterion can interfere with the user’s ability to use the entire page, all content on the web page (whether used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.NOTE
      Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the beginning of the pause and the resumption of the presentation, as this may not be technically possible and in many situations could be misleading.NOTE
      An animation that occurs as part of a pre-loading phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or make them think that content froze or broke.

    https://www.w3.org/TR/WCAG/#pause-stop-hide

    9.2.4.1 Bypass Blocks (Conditional)

    Condition: When ICT is a web page.
    There is a mechanism to bypass repeated content blocks on multiple web pages (Level A).

    https://www.w3.org/TR/WCAG/#bypass-blocks

    9.2.4.5 Multiple Ways (Conditional)

    Condition: When ICT is a web page.
    More than one way is provided to locate a web page within a set of web pages, except when the page is the result or an intermediate step of a process (Level AA).

    https://www.w3.org/TR/WCAG/#multiple-ways

    9.2.4.7 Focus Visible (Conditional)

    Condition: When ICT is a web page.
    Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible (Level AA).

    https://www.w3.org/TR/WCAG/#focus-visible

    9.4.1.2 Name, Role, Value (Conditional)

    Condition: When ICT is a web page.
    For all user interface components (including but not limited to form elements, links, and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and changes to these elements can be programmatically determined and available to user agents, including assistive technologies. (Level A)

    NOTE. This success criterion is primarily for web authors who develop or script their own user interface components. For example, standard HTML controls automatically satisfy this success criterion when used in accordance with their specification.

    https://www.w3.org/TR/WCAG/#name-role-value

    9.4.1.3 Status Messages (Conditional)

    Condition: When ICT is a web page.
    In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

    https://www.w3.org/TR/WCAG/#status-messages

    9.6 WCAG Guidelines Conformance Requirements (Conditional)

    Condition: When ICT is a web page

    The five following WCAG 2.1 AA conformance requirements [5] must be satisfied at Level AA:

    1. 1. Conformance Level
    2. 2. Full Pages
    3. 3. Complete Processes
    4. 4. Only Accessibility-Supported Ways
    5. 5. No Interruptions

    NOTE 1. If a web page meets all the requirements from 9.1 to 9.4 or provides an alternative version that meets Level AA (as defined in WCAG 2.1 [5]), Conformance Requirement 1 will be met.
    NOTE 2. According to the W3C, “WCAG 2.1 extends Web Content Accessibility Guidelines 2.0 [4], which were published as a W3C Recommendation in December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0 and, therefore, meets policies that reference WCAG 2.0 [4].”

    NOTE 3. Conformance Requirement 5 states that all content on the page, including content that would otherwise not be used to meet conformance, meets Success Criteria 9.1.4.2, 9.2.1.2, 9.2.2.2, and 9.2.3.1.

    11.8.4 Repair Service (Conditional)

    Condition: When web content is an authoring tool.
    If an accessibility checking functionality of an authoring tool can detect that content does not conform to a requirement in Chapters 9 (Web) or 10 (Non-Web), as appropriate, the authoring tool must provide one or more suggestions for repairing the content.

    NOTE. This does not preclude automatic or semi-automatic repair, which is possible (and recommended) for many types of content accessibility problems.

  • Disproportionate burden
    Not applicable
  • The content falls outside the scope of applicable legislation
    Not applicable

3. Preparation of this Accessibility Statement

This statement was prepared on July 14, 2023.
The method used to prepare the statement was a self-evaluation carried out by the third-party company Tecnomedia Digital SLL, which certifies that this website substantially corresponds to the interpretation of the informational guide provided by WCAG 2.1 AA guidelines. In this ongoing effort to remove barriers, they will continue to improve this site to achieve optimal accessibility and usability for all users.

The Accessibility Statement has been reviewed and updated in June 2023.

4. Feedback and Contact Information

You can communicate accessibility requirements (Article 10.2.a of RD 1112/2018) by:

  • Reporting any possible non-compliance by this website.
  • Transmitting other difficulties in accessing the content.
  • Submitting any other queries or improvement suggestions regarding website accessibility.

Through the contact form on this website or by phone at (+34) 976 52 95 27.
You can submit:

  • A complaint regarding compliance with the requirements of RD 1112/2018.
  • A request for accessible information regarding:
    1. 1. Content excluded from the scope of RD 1112/2018 as established by Article 3, section 4.
    2. 2. Content exempt from complying with accessibility requirements due to a disproportionate burden.

In the Accessible Information Request, you must clearly specify the facts, reasons, and request that allow verifying that it is a reasonable and legitimate request.
Complaints and claims regarding accessible information will be received and processed by the TECVINSER SL administration department through the described contact channels.

5. Optional Content

This website applies the requirements of Standard UNE-EN 301549:2022, considering the exceptions of RD 1112/2018.
The latest accessibility review was conducted in June 2023.

The website is optimized for Microsoft Internet Explorer 8.0 or higher and the latest current versions of FireFox, Safari, Opera, and Google Chrome browsers. The recommended minimum web resolution is 1280×1024.

The website is designed for Responsive viewing, ensuring optimal display on tablets and mobile devices. It is optimized for viewing on the latest current versions of Chrome for mobile, Firefox for mobile, Safari mobile, Opera Mini, and native Android browser.

This portal is designed to allow users to change text size, colors, and page background using standard browser configuration options.

To change the font size of text in major graphical browsers, use the following menus:

  • Internet Explorer, Mozilla, and Firefox: View > Text Size
  • Opera: View > Zoom
  • Safari: View > Make Text Bigger
  • Chrome: Control the current page > Text Size

To change the size of everything on the page:

  1. 1. Ctrl + + to increase
  2. 2. Ctrl + – to decrease
  3. 3. Ctrl + 0 to restore the original text size

If you want to override the style sheet or modify the text color, you can refer to the page “How to Change Text Size or Colors” from WAI, which can be read in Spanish at ¿Cómo cambiar el tamaño del texto o colores?