Hugo Lasarte

Hugo lasarte

Accessibility

Hugo Lasarte has committed to making its website accessible in accordance with Royal Decree 1112/2018, of September 7, on the accessibility of websites and applications for mobile devices in the public sector.

This accessibility statement applies to the website www.todopconline.com

compliance status
This website is partially in accordance with RD 1112/2018 due to the exceptions and the lack of conformity of the aspects indicated below.

content not accessible
The content listed below is not accessible for the following reasons:

There are logos and images with incorrect or confusing alternative text and complex images without textual description [requirement number 9.1.1.1 Non-textual content, of UNE-EN 301549:2022].

There are lists created incorrectly (without a list label), tables with incorrectly labeled cells and invisible labels in form elements [requirement number 9.1.3.1 Information and relationships, of UNE-EN 301549:2022].
There are tables that are not adapted to small screen sizes and form fields that are not displayed correctly on small screen sizes [requirement number 9.1.4.10 Text readjustment, of UNE-EN 301549:2022].

There is text that, when changing the spaces and line heights, is not displayed correctly [requirement number 9.1.4.12 Text spacing, of UNE-EN 301549:2022].
There are elements that are not accessible by keyboard, such as links to social networks, the text editor for comments, elements to sort search results, the search results pagination or the calendar arrows [requirement number 9.2.1.1 Keyboard , of UNE-EN 301549:2022].

There are elements that do not receive the focus and therefore cannot be interacted with using the keyboard [requirement number 9.2.4.3 Focus order, of UNE-EN 301549:2022].
There are links in which their function is not correctly identified (they have an inadequate description, a text that is too generic, an inappropriate title…) [requirement number 9.2.4.4 Purpose of links, of UNE-EN 301549:2022].

There are headers with repeated and/or little descriptive text [requirement number 9.2.4.6 Headers and labels, of UNE-EN 301549:2022].

There are images, infographics, text of links or buttons, text of headlines and content that are not translated into other languages [requirement number 9.3.1.2 Language of the parties, of UNE-EN 301549:2022].

The same icon is being used on some page for different purposes, which causes confusion [requirement number 9.3.2.4 Coherent identification, of UNE-EN 301549:2022].

Existence of non-descriptive error messages or error messages that are not grouped into a single message, as well as lack of suggestions in forms to fill in the fields correctly [requirement number 9.3.3.1 Error identification, of UNE-EN 301549:2022] .

Existence of forms with mandatory fields where the user is not informed of this, as well as fields where a textual example of the field format is missing (such as the DNI) [requirement number 9.3.3.2 Labels and instructions, of UNE-EN 301549: 2022].

Existence of form fields where an error is reported when an incorrect value is entered but a suggestion for its correction is not reported [requirement number 9.3.3.3 Suggestions for errors, of UNE-EN 301549:2022].
Existence of pages with syntax errors and, therefore, some support product may not correctly interpret the content (duplicate page IDs, unclosed tags, incorrect tag construction…) [requirement number 9.4.1.1 Processing, from UNE-EN 301549:2022].

Existence of pages in which the support products will not be able to obtain information, interact and be aware of the state of the user interface controls, such as help messages, action result status messages, attribute attributes. links, page language image, which cannot be read by screen readers at the time they appear [requirement number 9.4.1.2 Name, function, value of UNE-EN 301549:2022].

There could be occasional editing errors on some web page.
disproportionate burden
Does not apply.

The content does not fall within the scope of applicable law
There could be office files in PDF or other formats published before September 20, 2018 that do not fully meet all accessibility requirements. Although efforts have been made to ensure that most of them do comply.

Preparation of this accessibility statement
This statement was prepared on JANUARY 17, 2023.

The method used to prepare the statement has been a self-assessment carried out by the body itself.

Last revision of the statement: FEBRUARY 1, 2023.

Observations and contact information
You can make communications about accessibility requirements (article 10.2.a) of RD 1112/201

Accessibility