logo
Susana Solís

Accessibility

ACCESSIBILITY STATEMENT

https://susanasolis.com/

Compliance status

Susana Solis (hereinafter, also Website) is partially compliant with Royal Decree 1112/2018, of September 7, due to the lack of compliance of the aspects indicated below.

Content not accessible

The content below is not accessible for the following reasons:

a. Non-compliance with Royal Decree 1112/2018: Not applicable. Meets 100% of the web accessibility criteria.

    • Criterion 5 – General requirements: Not applicable.
  • Non-compatible means may be required to activate some accessibility features [requirement number 5.2 Activation of accessibility features, of UNE-EN 301549:2022].
    • Criterion 6 – Two-way voice communication capability: Not applicable.
  • It may not be possible to guarantee a frequency range with an upper limit of at least 7000Hz [requirement number 6.1 Voice bandwidth, of UNE-EN 301549:2022].
  • It may not be possible to provide a two-way communication mode using RTT [requirement number 6.2.1.1 Communication using RTT, of UNE-EN 301549:2022].
  • It may not be possible to provide a simultaneous two-way voice and text communication mode [requirement number 6.2.1.2 Simultaneous voice and text, of UNE-EN 301549:2022].
  • It may not clearly differentiate the sent text from the received text in RTT communications [requirement number 6.2.2.1 Visually distinguishable display, of UNE-EN 301549:2022].
  • It is possible that the RTT sending and receiving address cannot be determined by software [requirement number 6.2.2.2 Sending and receiving address determinable by software, of UNE-EN 301549:2022].
  • It may not be possible to provide the identification of the speaker by RTT [requirement number 6.2.2.3 Speaker identification, of UNE-EN 301549:2022].
  • There may not be an on-screen visual indicator of real-time audio activity [requirement number 6.2.2.4 Real-time audio visual indicator with text, of UNE-EN 301549:2022].
  • It may not be possible to guarantee compatibility with other systems with RTT functionalities [requirement number 6.2.3 Interoperability, of UNE-EN 301549:2022].
  • It may not be possible to guarantee that the RTT input will be transmitted to the network within 500ms [requirement number 6.2.4 RTT responsiveness, of UNE-EN 301549:2022].
  • It is possible that an alternative to voice may not be provided for performing interactive assistance or response tasks [requirement number 6.4 Alternatives to voice-based services, of UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum resolution of QVGA in the video functionalities [requirement number 6.5.2 Resolution, of UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum video frame rate of 20 FPS during communications [requirement number 6.5.3 Frame rate, of UNE-EN 301549:2022].
  • It is possible that the maximum time of 100ms between the presentation of the voice and the video to the user will not be exceeded [requirement number 6.5.4 Audio and video synchronization, of UNE-EN 301549:2022].
  • There may not be a way to identify the speaker for sign language users in real time [requirement number 6.5.6 Speaker identification with video communication, of UNE-EN 301549:2022].
    • Criterion 7 – Video capability: Not applicable.
  • There may be some video players that do not have an operating mode that allows displaying existing subtitles [requirement number 7.1.1 Subtitle playback, of UNE-EN 301549:2022].
  • There may be some video players that do not have an operating mode that allows synchronizing the audio with the subtitles [requirement number 7.1.2 Synchronization of subtitles, of UNE-EN 301549:2022].
  • There may be some video players that do not have a subtitle saving system [requirement number 7.1.3 Preservation of subtitles, of UNE-EN 301549:2022].
  • The user may not be able to adapt the characteristics of the subtitles to their individual requirements [requirement number 7.1.4 Characteristics of subtitles, of UNE-EN 301549:2022].
  • It is possible that a mode of operation that facilitates a spoken output of the available subtitles may not be provided in all cases [requirement number 7.1.5 Spoken subtitles, of UNE-EN 301549:2022].
  • There may be some players that do not have a mode to select and play available audio descriptions [requirement number 7.2.1 Playback of audio description, of UNE-EN 301549:2022].
  • There may be some players that do not have a mode to synchronize available audio descriptions [requirement number 7.2.2 Synchronization of audio description, of UNE-EN 301549:2022].
  • There may be some players that do not have a mode for saving available audio descriptions [requirement number 7.2.3 Preservation of audio description, of UNE-EN 301549:2022].
  • Some pages incorporate a video player that does not provide controls for playing subtitles and audio description at the same level of interaction as the rest of the controls [requirement number 7.3 User controls for subtitles and audio description, of UNE-EN 301549:2022].
    • Criterion 9 – Requirements applicable to web pages: Not applicable.
  • There are non-textual contents that lack a textual alternative, or that have an alternative that is not adequate [requirement number 9.1.1.1 Non-textual content, of UNE-EN 301549:2022].
  • Some recorded videos do not have text-based or audio alternatives [requirement number 9.1.2.1 Audio only and video only, of UNE-EN 301549:2022].
  • Some recorded videos may not contain subtitles [requirement number 9.1.2.2 Subtitles (recorded), of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative means [requirement number 9.1.2.3 Audio description or alternative means, of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative means [requirement number 9.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].
  • On some pages the information, structure and relationships are not determined by software or have no alternative as text [requirement number 9.1.3.1 Information and relationships, of UNE-EN 301549:2022].
  • Some pages do not have at least one correct reading sequence defined by the program [requirement number 9.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
  • Identification of elements based solely on sensory characteristics such as shape, color, size, visual location, orientation or sound [requirement number 9.1.3.3 Sensory characteristics, of UNE-EN 301549:2022].
  • The content does not adapt when changing the screen orientation [requirement number 9.1.3.4 Orientation, of UNE-EN 301549:2022].
  • There are form elements in which the purpose of the entry is not identified [requirement number 9.1.3.5 Identify the purpose of entry, of UNE-EN 301549:2022].
  • On some pages, color has been used as the sole visual means to convey information, indicate an action, provoke a response, or distinguish a visual element [requirement number 9.1.4.1 Use of color, of UNE-EN 301549:2022].
  • There are sound elements that play automatically and there is no mechanism to pause or stop them [requirement number 9.1.4.2 Audio control, of UNE-EN 301549:2022].
  • On some pages the text contrast ratio may not be at least 4.5:1 [requirement number 9.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].
  • There are errors on some pages related to text size and its customization options when zooming [requirement number 9.1.4.4 Text size change, of UNE-EN 301549:2022].
  • There are pre-designed images based solely on text [requirement number 9.1.4.5 Text images, of UNE-EN 301549:2022].
  • There are errors when customizing the font size, zoom level or text spacing [requirement number 9.1.4.10 Text readjustment, of UNE-EN 301549:2022].
  • Insufficient contrast in interface components or graphic objects [requirement number 9.1.4.11 Contrast of non-textual content, 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].
  • When an element receives the pointer or keyboard focus, additional content is displayed that cannot be dismissed without moving the pointer or changing the mouse focus [requirement number 9.1.4.13 Content with hover or focus, of UNE-EN 301549:2022].
  • There are pages where keyboard navigation is not optimal and errors appear [requirement number 9.2.1.1 Keyboard, of UNE-EN 301549:2022].
  • There are components that, when receiving focus, prevent passing it to another using only the tab key or arrow keys [requirement number 9.2.1.2 No focus traps, of UNE-EN 301549:2022].
  • There are keyboard shortcuts that do not work [requirement number 9.2.1.4 Shortcuts with character keys, of UNE-EN 301549:2022].
  • There is a set time limit that cannot be stopped, adjusted or extended [requirement number 9.2.2.1 Adjustable time, of UNE-EN 301549:2022].
  • There may be some automatically moving information that does not have controls to pause, control or hide [requirement number 9.2.2.2 Pause, stop and hide, of UNE-EN 301549:2022].
  • There may be elements that flash more than three times in one second or above the general threshold [requirement number 9.2.3.1 Threshold of three flashes or less, of UNE-EN 301549:2022].
  • On some pages there is no mechanism to omit blocks of content that are repeated on several pages [requirement number 9.2.4.1 Avoid blocks, of UNE-EN 301549:2022].
  • Inadequate description of some of the titles of the web pages [requirement number 9.2.4.2 Titles of pages, of UNE-EN 301549:2022].
  • In some documents, sequential navigation using the keyboard may not have a consistent order [requirement number 9.2.4.3 Focus order, of UNE-EN 301549:2022].
  • The purpose of the links, headings or labels of the portal may not always be sufficiently descriptive or consistent for all users [requirement number 9.2.4.4 Purpose of links (in context), of UNE-EN 301549:2022].
  • Links to related content pages or alternative navigation methods are not always provided [requirement number 9.2.4.5 Multiple ways, of UNE-EN 301549:2022].
  • There are headings with repeated and/or undescriptive text [requirement number 9.2.4.6 Headings and labels, of UNE-EN 301549:2022].
  • The location of the focus is not always visible when navigating with a keyboard [requirement number 9.2.4.7 Visible focus, of UNE-EN 301549:2022].
  • There are elements that use multipoint or path-based gestures that cannot be operated with just a pointer or without a path-based gesture [requirement number 9.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
  • There are pages where it is not possible to cancel an event by clicking the mouse [requirement number 9.2.5.2 Pointer Cancellation, of UNE-EN 301549:2022].
  • There are interface components that do not have visible labels [requirement number 9.2.5.3 Name label, of UNE-EN 301549:2022].
  • There is functionality that can only be operated by movement [requirement number 9.2.5.4 Activation by movement, of UNE-EN 301549:2022].
  • On some pages the default language used is not indicated [requirement number 9.3.1.1 Page language, of UNE-EN 301549:2022].
  • There could be occasional errors in editing and language identification in some parts of the web page [requirement number 9.3.1.2 Language of the parts, of UNE-EN 301549:2022].
  • There are components that, when they receive focus, initiate a context change [requirement number 9.3.2.1 When receiving focus, of UNE-EN 301549:2022].
  • User interaction with a control causes page changes without prior warning [requirement number 9.3.2.2 When receiving input, of UNE-EN 301549:2022].
  • There may be pages with inconsistent navigation, due to different links with the same destination [requirement number 9.3.2.3 Consistent navigation, of UNE-EN 301549:2022].
  • Certain interactive elements are not presented consistently in all cases, as they are displayed with different visual styles [requirement number 9.3.2.4 Consistent identification, of UNE-EN 301549:2022].
  • There are error messages that are not very descriptive, or error messages that are not grouped into a single message, as well as a lack of suggestions in the form to fill in the fields correctly [requirement number 9.3.3.1 Identification of errors, of UNE-EN 301549:2022].
  • There are 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 [requirement number 9.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • There could be some input error in some field/form for which the user was not notified of the suggestion to solve it [requirement number 9.3.3.3 Suggestions for errors 333, of UNE-EN 301549:2022].
  • The data entry does not detect errors nor does it provide the user with an opportunity to correct them [requirement number 9.3.3.4 Prevention of errors (legal, financial, data), of UNE-EN 301549:2022].
  • There may be errors in the use of HTML tags and attributes and WAI-ARIA 1.1 [requirement number 9.4.1.1 Processing, of UNE-EN 301549:2022].
  • On some pages, user interface components such as form elements, links, and script-generated components do not follow the structure recommended by the accessibility guidelines [requirement number 9.4.1.2 Name, function, value, of UNE-EN 301549:2022].
  • On some pages, status messages may not be determined programmatically through functions or properties [requirement number 9.4.1.3 Status messages, of UNE-EN 301549:2022].
  • Some of the WCAG 2.1 requirements are not met [requirement number 9.6 Conformity requirements of the WCAG guidelines, of UNE-EN 301549:2022].
    • Criterion 10 – Requirements applicable to non-web documents: Not applicable.
  • There may be documents with images that do not have an adequate textual alternative [requirement number 10.1.1.1 Non-textual content, of UNE-EN 301549:2022].
  • There may be no equivalent alternative for recorded audio-only or video-only content [requirement number 10.1.2.1 Audio only and video only, of UNE-EN 301549:2022].
  • The videos may lack subtitles and audio descriptions [requirement number 10.1.2.2 Subtitles (recorded), of UNE-EN 301549:2022].
  • There may not be an alternative for time-dependent media or an audio description for video content recorded in synchronized multimedia [requirement number 10.1.2.3 Audio description or alternative medium, of UNE-EN 301549:2022].
  • Audio description may not be provided for all recorded video content within synchronized multimedia content [requirement number 10.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].
  • In some documents, the information, structure, and relationships are not determined by software or have no alternative as text [requirement number 10.1.3.1 Information and relationships, of UNE-EN 301549:2022].
  • Some documents do not have at least one correct reading sequence defined by program [requirement number 10.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
  • There may be documents for which there is no other accessible alternative with which to operate and understand the content [requirement number 10.1.3.3 Sensory characteristics, of UNE-EN 301549:2022].
  • There may be documents whose content does not adapt when changing the screen orientation [requirement number 10.1.3.4 Orientation, of UNE-EN 301549:2022].
  • In some forms, the input field that collects information about the user does not have its purpose identified [requirement number 10.1.3.5 Identify the purpose of input, of UNE-EN 301549:2022].
  • In some documents, color has been used as the sole visual means to convey information, indicate an action, provoke a response, or distinguish a visual element [requirement number 10.1.4.1 Use of color, of UNE-EN 301549:2022].
  • There are audio elements in some documents that play automatically and there is no mechanism to pause or stop them [requirement number 10.1.4.2 Audio control, of UNE-EN 301549:2022].
  • In some documents the text contrast ratio may not be at least 4.5:1 [requirement number 10.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].
  • In some texts the size cannot be changed up to 200 percent without loss of content or functionality and in some documents the content may lose functionality or information when the content is enlarged [requirement number 10.1.4.4 Text size change, of UNE-EN 301549:2022].
  • In some documents, images of text may have been used instead of text to convey information [requirement number 10.1.4.5 Images of text, of UNE-EN 301549:2022].
  • In some documents, the content may lose functionality or information when the content is expanded [requirement number 10.1.4.10 Text readjustment, of UNE-EN 301549:2022].
  • In some documents, the contrast of user interface components and graphic objects may not reach 3:1 with adjacent colors [requirement number 10.1.4.11 Contrast of non-textual content, of UNE-EN 301549:2022].
  • In some texts it is not possible to override the specified text spacing [requirement number 10.1.4.12 Text spacing, of UNE-EN 301549:2022].
  • The content of some documents does not receive keyboard focus with which to perform any action [requirement number 10.1.4.13 Content with hover or focus, of UNE-EN 301549:2022].
  • There are documents that cannot be fully operated via keyboard [requirement number 10.2.1.1 Keyboard, of UNE-EN 301549:2022].
  • In some documents, the headers have not been defined and keyboard navigation is not possible [requirement number 10.2.1.2 No focus traps, of UNE-EN 301549:2022].
  • Some documents contain keyboard shortcuts that do not work [requirement number 10.2.1.4 Shortcuts with character keys, of UNE-EN 301549:2022].
  • Some document establishes a time limit that cannot be stopped, adjusted or extended [requirement number 10.2.2.1 Adjustable time, of UNE-EN 301549:2022].
  • Some documents may contain automatically moving information that does not have controls to pause, control or hide [requirement number 10.2.2.2 Pause, stop and hide, of UNE-EN 301549:2022].
  • Some documents may contain elements that flash more than three times in one second or above the general threshold [requirement number 10.2.3.1 Threshold of three flashes or less, of UNE-EN 301549:2022].
  • There may be documents that do not have a title [requirement number 10.2.4.2 Title of pages, of UNE-EN 301549:2022].
  • In some documents, the headers have not been defined and it is not possible to navigate using the keyboard [requirement number 10.2.4.3 Focus order, of UNE-EN 301549:2022].
  • Some documents may contain links that may not have a specific purpose defined in text [requirement number 10.2.4.4 Purpose of links (in context), of UNE-EN 301549:2022].
  • In some documents there may be a heading or control name that is not sufficiently descriptive of its purpose [requirement number 10.2.4.6 Headers and labels, of UNE-EN 301549:2022].
  • The focus location is not always visible when navigating through a document using the keyboard [requirement number 10.2.4.7 Visible focus, of UNE-EN 301549:2022].
  • Some documents may contain elements that use multipoint or path-based gestures that cannot be operated with just a pointer or without a path-based gesture [requirement number 10.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
  • There are documents where it is not possible to cancel an event by clicking the mouse [requirement number 10.2.5.2 Pointer Cancellation, of UNE-EN 301549:2022].
  • There are documents that have some labels accompanying the controls that do not have the same name [requirement number 10.2.5.3 Name label, of UNE-EN 301549:2022].
  • There are documents whose functionality is only operable through movement [requirement number 10.2.5.4 Activation by movement, of UNE-EN 301549:2022].
  • There may be documents in which the main language is not identified [requirement number 10.3.1.1 Language of the page, of UNE-EN 301549:2022].
  • There may be content or phrases within some documents whose language cannot be determined by program [requirement number 10.3.2.1 Language of the parts, of UNE-EN 301549:2022].
  • There may be components in some document that, when they receive focus, initiate a context change [requirement number 10.3.2.1 When focus is received, of UNE-EN 301549:2022].
  • User interaction with a control causes page changes without prior warning [requirement number 10.3.2.2 When receiving inputs, of UNE-EN 301549:2022].
  • There are data entry fields with automatic error detection capability that do not identify where or how the error occurs [requirement number 10.3.3.1 Error identification, of UNE-EN 301549:2022].
  • In some form of some document, some automatic context change could occur without warning the user [requirement number 10.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • In some document there might be an input error in some field/form that the user was not notified of the suggestion to solve it [requirement number 10.3.3.3 Suggestions for errors, of UNE-EN 301549:2022].
  • Some documents may contain forms for collecting data or that are legally or financially binding and are not reversible, reviewable, or have confirmation before being sent [requirement number 10.3.3.4 Prevention of errors (legal, financial, data), of UNE-EN 301549:2022].
  • Some documents may contain duplicate attributes and IDs [requirement number 10.4.1.1 Processing, of UNE-EN 301549:2022].
  • In some documents, user interface components such as form elements, links, and script-generated components do not follow the structure recommended by the accessibility guidelines [requirement number 10.4.1.2 Name, function, value, of UNE-EN 301549:2022].
  • In some documents, status messages may not be determined programmatically through functions or properties [requirement number 10.4.1.3 Status messages, of UNE-EN 301549:2022].
    • Criterion 11 – Requirements applicable to software: Not applicable.
  • The user’s browser visual preferences are not respected on the page [requirement number 11.7 User preferences, of UNE-EN 301549:2022].
  • The information required for accessibility may not be compatible with the format used for the authoring tool output [requirement number 11.8.1 Content management technology, of UNE-EN 301549:2022].
  • There may not be a mechanism that allows content to be created in an accessible way [requirement number 11.8.2 Creation of accessible content, of UNE-EN 301549:2022].
  • There is no mechanism for preserving accessibility information during transformations [requirement number 11.8.3 Preservation of accessibility information during transformations, of UNE-EN 301549:2022].
  • There may not be a repair mechanism for the accessibility checker [requirement number 11.8.4 Repair service, of UNE-EN 301549:2022].
  • There may not be any template available that is compatible with the creation of content in accordance with the requirements of chapters 9 (Web) or 10 (Non-web documents) [requirement number 11.8.5 Templates, of UNE-EN 301549:2022].
    • Criterion 12 – Requirements applicable to documentation and support services: Not applicable.
  • The product documentation does not list or explain all available accessibility features [requirement number 12.1.1 Accessibility and compatibility features, of UNE-EN 301549:2022].
  • Product documentation may not be fully in accessible formats [requirement number 12.1.2 Accessible documentation, of UNE-EN 301549:2022].
  • Support services do not provide all the information on accessibility features included in the product documentation [requirement number 12.2.2 Information on accessibility and compatibility features, of UNE-EN 301549:2022].
  • Support services cannot always be adapted to the communication needs of users with disabilities [requirement number 12.2.3 Effective communication, of UNE-EN 301549:2022].
  • There may be documentation provided by support services that is not in an accessible format [requirement number 12.2.4 Accessible documentation, of UNE-EN 301549:2022].

b. Disproportionate burden: Not applicable.

c. Content does not fall within the scope of the applicable legislation:

  • There may be office documents in PDF and other formats published before September 20, 2018, that do not fully comply with all accessibility requirements. However, every effort has been made to ensure that most of them do.
  • There may be third-party content that is not developed in this Unit or under its control, such as images, interactive maps, videos, documents, players, etc.
  • There may be pre-recorded files published before September 20, 2018 that do not fully meet all accessibility requirements.
  • Parts or all of the website may be created with a CMS (WordPress, Shopify, PrestaShop, etc.), so due to some update or change in the systems, not all generated or auto-generated content may comply with all accessibility regulations.

Preparation of this accessibility statement

This declaration was prepared on 28/11/2025

The method used to prepare the declaration was a self-assessment carried out by the company itself.

Last review of the statement: 28/11/2025

Notes and contact information

You can submit communications regarding accessibility requirements (article 10.2.a of Royal Decree 1112/2018, of September 7) such as, for example:

  • Report any potential breaches by this website.
  • To communicate other difficulties in accessing the content.
  • Submit any other query or suggestion for improvement related to the accessibility of the website.

Through the following means:

  • Email: susana.solis.14@icloud.com
  • Telephone: +34627003138

In accordance with article 10.2.b of RD 1112/2018, you can also submit:

  • A complaint regarding compliance with the requirements of Royal Decree 1112/2018.
  • A request for accessible information regarding:
    • Contents that are excluded from the scope of application of RD 1112/2018 as established by article 3, section 4.
    • Content that is exempt from compliance with accessibility requirements because it imposes a disproportionate burden.

In the Accessible Information Request, the facts, reasons and request that allow verification that it is a reasonable and legitimate request must be specified clearly.

Communications will be received and processed by the company’s management, as the unit responsible for the content of this website.

Optional content

The currently visible version of this website is from 28/11/2025 and on that date the review of the level of accessibility in force at that time was carried out.

From that date, daily partial reviews of new or modified web content are carried out, both of templates and of the final pages and documents published, in order to ensure compliance with the accessibility requirements of the UNE-EN 301549:2022 Standard, considering the exceptions of Royal Decree 1112/2018, of September 7.

Among others, the following measures are adopted to facilitate accessibility:

  • Use of alternative text in images.
  • The links provide details of the function or destination of the hyperlink.
  • Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.

Compatibility

The website:

  • It has been designed adapting to current standards and regulations regarding accessibility, complying with the priority 2 (AA) checkpoints defined in the Web Content Accessibility Guidelines (WCAG 2.1) specification.
  • It is optimized for the latest versions of Chrome, Edge, Firefox, Safari, and Opera.
  • It is designed for correct viewing on any resolution and device: desktop, tablets or mobile (responsive design)
  • It has been created using HTML5 as the markup language and CSS 3 stylesheets for its design.

In addition, ongoing auditing and content review is carried out to facilitate interpretation and improve navigation through the website.

This Accessibility Statement document was created using the free online web accessibility statement template generator on 28/11/2025.