ACCESSIBILITY STATEMENT
https://christineclouxdanza.com/
Christine Cloux Danza (hereinafter, the “Website”) is partially compliant with Royal Decree 1112/2018 of 7 September due to the non-conformities indicated below.
The content listed below is not accessible for the following reasons:
a. Non-compliance with RD 1112/2018: Not applicable. It meets 100% of the web accessibility criteria.
Criterion 5 – General requirements: Not applicable.
Non-compatible means may be required to activate some accessibility feature [requirement 5.2 Activation of accessibility features, UNE-EN 301549:2022].
Criterion 6 – Bidirectional voice communication: Not applicable.
It may not be possible to guarantee a frequency range with an upper limit of at least 7000 Hz [requirement 6.1 Bandwidth for voice, UNE-EN 301549:2022].
It may not be possible to provide a bidirectional communication mode using RTT [requirement 6.2.1.1 RTT communication, UNE-EN 301549:2022].
It may not be possible to provide a bidirectional mode of voice and text simultaneously [requirement 6.2.1.2 Simultaneous voice and text, UNE-EN 301549:2022].
It may not clearly distinguish on screen between sent and received text in RTT communications [requirement 6.2.2.1 Visually distinguishable on-screen presentation, UNE-EN 301549:2022].
It may not be possible for software to determine the RTT send/receive direction [requirement 6.2.2.2 Software-determinable send/receive direction, UNE-EN 301549:2022].
It may not be possible to provide speaker identification via RTT [requirement 6.2.2.3 Speaker identification, UNE-EN 301549:2022].
There may not be an on-screen visual indicator of real-time audio activity [requirement 6.2.2.4 Visual indicator of audio with real-time text, UNE-EN 301549:2022].
It may not be possible to guarantee compatibility with other systems providing RTT features [requirement 6.2.3 Interoperability, UNE-EN 301549:2022].
It may not be possible to guarantee that RTT input is transmitted to the network within 500 ms [requirement 6.2.4 RTT responsiveness, UNE-EN 301549:2022].
An alternative to voice may not be provided for assistance or interactive response tasks [requirement 6.4 Alternatives to voice-based services, UNE-EN 301549:2022].
It may not be possible to guarantee a minimum QVGA resolution in video features [requirement 6.5.2 Resolution, UNE-EN 301549:2022].
It may not be possible to guarantee a minimum video frame rate of 20 FPS during communications [requirement 6.5.3 Frame rate, UNE-EN 301549:2022].
The maximum time of 100 ms between presenting voice and video to the user may not be met [requirement 6.5.4 Audio-video synchronisation, UNE-EN 301549:2022].
There may be no mode for speaker identification for real-time sign-language users [requirement 6.5.6 Speaker identification with video communication, UNE-EN 301549:2022].
Criterion 7 – Video capability: Not applicable.
Some video players may lack an operation mode that allows displaying available captions [requirement 7.1.1 Caption playback, UNE-EN 301549:2022].
Some video players may lack an operation mode that allows synchronising audio with captions [requirement 7.1.2 Caption synchronisation, UNE-EN 301549:2022].
Some video players may lack a system to preserve captions [requirement 7.1.3 Caption preservation, UNE-EN 301549:2022].
Users may be unable to adapt caption characteristics to their individual requirements [requirement 7.1.4 Caption characteristics, UNE-EN 301549:2022].
A mode that facilitates spoken output of available captions may not be provided in all cases [requirement 7.1.5 Spoken captions, UNE-EN 301549:2022].
Some players may lack a mode to select and play available audio descriptions [requirement 7.2.1 Audio-description playback, UNE-EN 301549:2022].
Some players may lack a mode to synchronise available audio descriptions [requirement 7.2.2 Audio-description synchronisation, UNE-EN 301549:2022].
Some players may lack a mode to preserve available audio descriptions [requirement 7.2.3 Audio-description preservation, UNE-EN 301549:2022].
Some pages include a video player that does not provide controls for caption and audio-description playback at the same level of interaction as the rest of the controls [requirement 7.3 User controls for captions and audio description, UNE-EN 301549:2022].
Criterion 9 – Requirements applicable to web pages: Not applicable.
There is non-text content that lacks a text alternative or has an inadequate one [requirement 9.1.1.1 Non-text content, UNE-EN 301549:2022].
Some prerecorded videos lack text-based alternatives or audio alternatives [requirement 9.1.2.1 Audio-only and video-only (prerecorded), UNE-EN 301549:2022].
Some prerecorded videos may lack captions [requirement 9.1.2.2 Captions (prerecorded), UNE-EN 301549:2022].
Some prerecorded videos on the website lack audio description or alternative media [requirement 9.1.2.3 Audio description or media alternative, UNE-EN 301549:2022].
Some prerecorded videos on the website lack audio description or alternative media [requirement 9.1.2.5 Audio description (prerecorded), UNE-EN 301549:2022].
On some pages, information, structure and relationships are not programmatically determined or do not have a text alternative [requirement 9.1.3.1 Info and relationships, UNE-EN 301549:2022].
Some pages do not have at least one programmatically determined correct reading sequence [requirement 9.1.3.2 Meaningful sequence, UNE-EN 301549:2022].
Identification of elements relies solely on sensory characteristics such as shape, colour, size, visual location, orientation or sound [requirement 9.1.3.3 Sensory characteristics, UNE-EN 301549:2022].
Content does not adapt when changing screen orientation [requirement 9.1.3.4 Orientation, UNE-EN 301549:2022].
There are form elements where the purpose of input is not identified [requirement 9.1.3.5 Identify input purpose, UNE-EN 301549:2022].
On some pages, colour alone is used to convey information, indicate an action, prompt a response or distinguish a visual element [requirement 9.1.4.1 Use of colour, UNE-EN 301549:2022].
Some audio elements play automatically with no mechanism to pause or stop them [requirement 9.1.4.2 Audio control, UNE-EN 301549:2022].
On some pages, the contrast ratio of text may be below 4.5:1 [requirement 9.1.4.3 Contrast (minimum), UNE-EN 301549:2022].
There are errors related to text size and its customisation when zooming [requirement 9.1.4.4 Resize text, UNE-EN 301549:2022].
There are text-only images [requirement 9.1.4.5 Images of text, UNE-EN 301549:2022].
There are errors when customising font size, zoom level or text spacing [requirement 9.1.4.10 Reflow, UNE-EN 301549:2022].
Insufficient contrast in user-interface components or graphical objects [requirement 9.1.4.11 Non-text contrast, UNE-EN 301549:2022].
Some text does not display correctly when line and paragraph spacing is changed [requirement 9.1.4.12 Text spacing, UNE-EN 301549:2022].
When an element receives pointer hover or keyboard focus, additional content appears that cannot be dismissed without moving the pointer or changing keyboard focus [requirement 9.1.4.13 Content on hover or focus, UNE-EN 301549:2022].
Some pages do not offer optimal keyboard navigation and errors occur [requirement 9.2.1.1 Keyboard, UNE-EN 301549:2022].
Some components trap focus so it cannot be moved using only Tab or arrow keys [requirement 9.2.1.2 No keyboard trap, UNE-EN 301549:2022].
Some keyboard shortcuts do not work [requirement 9.2.1.4 Character key shortcuts, UNE-EN 301549:2022].
A time limit may be set that cannot be stopped, adjusted or extended [requirement 9.2.2.1 Timing adjustable, UNE-EN 301549:2022].
There may be automatically moving information without controls to pause, stop or hide it [requirement 9.2.2.2 Pause, stop, hide, UNE-EN 301549:2022].
Some elements may flash more than three times per second or above the general threshold [requirement 9.2.3.1 Three flashes or below threshold, UNE-EN 301549:2022].
Some pages do not provide a mechanism to skip blocks of content repeated across pages [requirement 9.2.4.1 Bypass blocks, UNE-EN 301549:2022].
Some page titles are not adequately descriptive [requirement 9.2.4.2 Page titled, UNE-EN 301549:2022].
In some documents, sequential keyboard navigation may not follow a consistent order [requirement 9.2.4.3 Focus order, UNE-EN 301549:2022].
The purpose of links, headings or labels may not always be sufficiently descriptive or consistent for all users [requirement 9.2.4.4 Link purpose (in context), UNE-EN 301549:2022].
Links to related content or alternative navigation methods are not always offered [requirement 9.2.4.5 Multiple ways, UNE-EN 301549:2022].
Some headings contain repeated and/or poorly descriptive text [requirement 9.2.4.6 Headings and labels, UNE-EN 301549:2022].
Focus location is not always visible when navigating with the keyboard [requirement 9.2.4.7 Focus visible, UNE-EN 301549:2022].
There are elements using multipoint or path-based gestures that cannot be operated with a single pointer or without a path-based gesture [requirement 9.2.5.1 Pointer gestures, UNE-EN 301549:2022].
On some pages it is not possible to cancel an event triggered by mouse down [requirement 9.2.5.2 Pointer cancellation, UNE-EN 301549:2022].
Some interface components have visible labels that do not match their accessible names [requirement 9.2.5.3 Label in name, UNE-EN 301549:2022].
There is functionality operable only by motion [requirement 9.2.5.4 Motion actuation, UNE-EN 301549:2022].
On some pages the default page language is not indicated [requirement 9.3.1.1 Language of page, UNE-EN 301549:2022].
There may be occasional failures in detecting and identifying the language of parts [requirement 9.3.1.2 Language of parts, UNE-EN 301549:2022].
Some components start a change of context upon receiving focus [requirement 9.3.2.1 On focus, UNE-EN 301549:2022].
User interaction with a control may cause page changes without prior notice [requirement 9.3.2.2 On input, UNE-EN 301549:2022].
There may be pages with inconsistent navigation due to different links pointing to the same destination [requirement 9.3.2.3 Consistent navigation, UNE-EN 301549:2022].
Certain interactive elements are not presented consistently in all cases, as they appear with different visual styles [requirement 9.3.2.4 Consistent identification, UNE-EN 301549:2022].
There are error messages that are not descriptive enough, or errors are not grouped into a single message; forms may lack suggestions to complete fields correctly [requirement 9.3.3.1 Error identification, UNE-EN 301549:2022].
Some required fields in forms are not indicated as such, and some fields lack a textual example of the expected format [requirement 9.3.3.2 Labels or instructions, UNE-EN 301549:2022].
There may be input errors for which the user is not notified with a suggestion to correct them [requirement 9.3.3.3 Error suggestion, UNE-EN 301549:2022].
For data entry, errors are neither detected nor is the user given an opportunity to correct them [requirement 9.3.3.4 Error prevention (legal, financial, data), UNE-EN 301549:2022].
There may be errors in the use of HTML and WAI-ARIA 1.1 labels and attributes [requirement 9.4.1.1 Parsing, UNE-EN 301549:2022].
On some pages, UI components such as form elements, links and script-generated components do not follow the structure recommended by the accessibility guidelines [requirement 9.4.1.2 Name, role, value, UNE-EN 301549:2022].
On some pages, status messages may not be programmatically determined through properties or roles [requirement 9.4.1.3 Status messages, UNE-EN 301549:2022].
Some WCAG 2.1 requirements are not met [requirement 9.6 WCAG conformance requirements, UNE-EN 301549:2022].
Criterion 10 – Requirements applicable to non-web documents: Not applicable.
There may be documents with images that lack an appropriate text alternative [requirement 10.1.1.1 Non-text content, UNE-EN 301549:2022].
There may be no equivalent alternative for prerecorded audio-only or video-only content [requirement 10.1.2.1].
Videos may lack captions and audio descriptions [requirement 10.1.2.2].
There may be no alternative for time-based media or audio description for prerecorded video within synchronised media [requirement 10.1.2.3].
Audio description may not be provided for all prerecorded video content within synchronised media [requirement 10.1.2.5].
In some documents, information, structure and relationships are not programmatically determined or do not have a text alternative [requirement 10.1.3.1].
Some documents do not have at least one programmatically determined correct reading sequence [requirement 10.1.3.2].
Some documents may lack an accessible alternative through which to operate and understand the content [requirement 10.1.3.3].
Some documents may not adapt when changing screen orientation [requirement 10.1.3.4].
In some forms, the input field that collects user information does not have its purpose identified [requirement 10.1.3.5].
In some documents, colour has been used as the only visual means to convey information, indicate an action, prompt a response or distinguish a visual element [requirement 10.1.4.1].
Some documents contain audio elements that play automatically without a mechanism to pause or stop them [requirement 10.1.4.2].
In some documents, the text contrast ratio may be below 4.5:1 [requirement 10.1.4.3].
In some texts, size cannot be increased up to 200% without loss of content or functionality, and some documents may lose functionality or information when enlarged [requirement 10.1.4.4].
Some documents may use images of text instead of text to convey information [requirement 10.1.4.5].
In some documents, content may lose functionality or information when enlarged [requirement 10.1.4.10].
In some documents, the contrast of UI components and graphical objects may not reach 3:1 against adjacent colours [requirement 10.1.4.11].
In some texts, it is not possible to override specified text spacing [requirement 10.1.4.12].
Some documents’ content does not receive keyboard focus to perform any action [requirement 10.1.4.13].
There are documents that cannot be fully operated via keyboard [requirement 10.2.1.1].
In some documents, headings are not defined and keyboard navigation is not possible [requirement 10.2.1.2].
Some documents contain keyboard shortcuts that do not work [requirement 10.2.1.4].
Some documents set a time limit that cannot be stopped, adjusted or extended [requirement 10.2.2.1].
Some documents may contain automatically moving information without controls to pause, stop or hide it [requirement 10.2.2.2].
Some documents may include elements that flash more than three times per second or above the general threshold [requirement 10.2.3.1].
Some documents may not have a title [requirement 10.2.4.2].
In some documents, headings are not defined and keyboard navigation is not possible [requirement 10.2.4.3].
Some documents may contain links whose specific purpose is not textually defined [requirement 10.2.4.4].
Some documents may include a heading or control name that is not sufficiently descriptive of its purpose [requirement 10.2.4.6].
Focus location is not always visible when navigating documents by keyboard [requirement 10.2.4.7].
Some documents may include elements using multipoint or path-based gestures that cannot be operated with a single pointer or without a path-based gesture [requirement 10.2.5.1].
There are documents where an event cannot be cancelled on mouse down [requirement 10.2.5.2].
There are documents where labels accompanying controls do not match the accessible name [requirement 10.2.5.3].
There are documents whose functionality is operable only by motion [requirement 10.2.5.4].
There may be documents in which the main language is not identified [requirement 10.3.1.1].
There may be content or phrases within documents whose language cannot be programmatically determined [requirement 10.3.2.1].
There may be components in some documents that start a change of context upon receiving focus [requirement 10.3.2.1].
User interaction with a control may cause page changes without prior notice [requirement 10.3.2.2].
There are data-entry fields with automatic error detection that do not identify where or how the error occurs [requirement 10.3.3.1].
In some document forms, an automatic change of context could occur without warning the user [requirement 10.3.3.2].
There may be input errors in some document forms without notifying the user with a suggestion to fix them [requirement 10.3.3.3].
Some documents may include data-collection or legally/financially committing forms that are not reversible, reviewable or confirmed before submission [requirement 10.3.3.4].
Some documents may have duplicated attributes and IDs [requirement 10.4.1.1].
In some documents, UI components such as form elements, links and script-generated components do not follow the structure recommended by the accessibility guidelines [requirement 10.4.1.2].
In some documents, status messages may not be programmatically determined through roles or properties [requirement 10.4.1.3].
Criterion 11 – Requirements applicable to software: Not applicable.
Browser user visual preferences are not respected on the page [requirement 11.7 User preferences, UNE-EN 301549:2022].
The information necessary for accessibility may not be compatible with the output format used by the authoring tool [requirement 11.8.1 Content management technology].
There may be no mechanism enabling accessible content creation [requirement 11.8.2 Creation of accessible content].
There is no mechanism to preserve accessibility information during transformations [requirement 11.8.3 Preservation of accessibility information during transformations].
There may be no accessibility checker repair service [requirement 11.8.4 Repair service].
No template may be available that is compatible with creating content conforming to the requirements of Chapters 9 (Web) or 10 (Non-web documents) [requirement 11.8.5 Templates].
Criterion 12 – Requirements applicable to documentation and support services: Not applicable.
Product documentation does not list or explain all available accessibility features [requirement 12.1.1].
Product documentation may not be fully available in accessible formats [requirement 12.1.2].
Support services do not provide all information on the accessibility features included in the product documentation [requirement 12.2.2].
Support services cannot always be adapted to the communication needs of users with disabilities [requirement 12.2.3].
Support-service documentation may not be in an accessible format [requirement 12.2.4].
b. Disproportionate burden: Not applicable.
c. Content not within the scope of the applicable legislation:
There may be office files in PDF and other formats published before 20 September 2018 that do not fully meet all accessibility requirements, although most of them have been made to comply.
There may be third-party content not developed by this unit or under its control, such as images, interactive maps, videos, documents, players, etc.
There may be prerecorded files published before 20 September 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.). Due to updates or system changes, not all generated or auto-generated content may comply with all accessibility regulations.
This statement was prepared on 29/04/2025.
The method used to prepare the statement was a self-assessment carried out by the company itself.
Last review of the statement: 29/04/2025.
You may submit communications regarding accessibility requirements (Article 10.2.a of Royal Decree 1112/2018 of 7 September), such as:
Reporting any possible non-compliance by this website.
Conveying other difficulties in accessing the content.
Making any other query or suggestion for improving the accessibility of the website.
Contact channels:
Phone:
Pursuant to Article 10.2.b of RD 1112/2018, you may also submit:
A complaint regarding compliance with the requirements of RD 1112/2018.
A request for accessible information relating to:
Content excluded from the scope of RD 1112/2018 as established by Article 3(4).
Content exempt from accessibility requirements because it imposes a disproportionate burden.
Requests for accessible information must clearly specify the facts, reasons and request enabling verification that it is a reasonable and legitimate request.
Communications will be received and handled by the company’s management, as the unit responsible for the content of this website.
The currently visible version of this website is dated 29/04/2025, and on that date, the level of accessibility in force at that time was reviewed.
From that date onwards, partial daily reviews are carried out of new or modified web content—both templates and final published pages and documents—in order to ensure compliance with the accessibility requirements of UNE-EN 301549:2022, considering the exceptions of Royal Decree 1112/2018 of 7 September.
Among others, the following measures are adopted to facilitate accessibility:
Use of alternative text for images.
Links provide details of the function or destination of the hyperlink.
Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.
The website:
has been designed in accordance with current accessibility standards and regulations, complying with Level AA success criteria defined in the Web Content Accessibility Guidelines (WCAG 2.1);
is optimised for the latest supported versions of Chrome, Edge, Firefox, Safari and Opera;
is designed for correct display at any resolution and on desktop, tablet or mobile devices (responsive design);
has been developed using HTML5 as the markup language and CSS 3 for presentation.
In addition, continuous auditing and content review work is carried out to facilitate interpretation and improve navigation throughout the website.
