Compliance status
Dra. Anna Tavarone Dental Clinic (hereinafter also Website) is partially compliant with Royal Decree 1112/2018, of September 7, due to the lack of conformity of the aspects indicated below.
Content not accessible
The content collected below is not accessible for the following reasons:
to. Lack of 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 any accessibility feature [requirement number 5.2 Activation of accessibility features, from UNE-EN 301549:2022]. Criterion 6 - Bidirectional voice communication capacity: No applies. A frequency range whose upper limit is at least 7000Hz may not be guaranteed [requirement number 6.1 Bandwidth for voice, of UNE-EN 301549:2022]. A bidirectional communication mode may not be provided. through RTT [requirement number 6.2.1.1 Communication through RTT, from UNE-EN 301549:2022]. A bidirectional communication mode of voice and text simultaneously may not be provided [requirement number 6.2.1.2 Simultaneous voice and text, from UNE -EN 301549:2022]. It may not clearly display the text sent from the text received in RTT communications [requirement number 6.2.2.1 Visually differentiable screen presentation, from UNE-EN 301549:2022]. The RTT sending and receiving address cannot be determined by software [requirement number 6.2.2.2 Sending and receiving address determinable by software, from UNE-EN 301549:2022]. The identification of the speaker may not be provided by RTT [ requirement number 6.2.2.3 Speaker identification, from UNE-EN 301549:2022]. There may not be an on-screen visual indicator of real-time audio activity [requirement number 6.2.2.4 Visual audio indicator with real-time text real, from UNE-EN 301549:2022]. It may not be able to guarantee compatibility with other systems with RTT functionalities [requirement number 6.2.3 Interoperability, from UNE-EN 301549:2022]. It may not be able to guarantee that RTT input is transmitted to the network within 500ms [requirement number 6.2.4 RTT Responsiveness, from UNE-EN 301549:2022]. An alternative to voice may not be provided to perform the tasks of assistance or interactive response [requirement number 6.4 Alternatives to voice-based services, from UNE-EN 301549:2022]. A minimum resolution of QVGA may not be guaranteed in video functionalities [requirement number 6.5.2 Resolution, from UNE-EN 301549:2022]. A minimum video rate of 20 FPS may not be guaranteed during communications [requirement number 6.5.3 Frame rate, from UNE-EN 301549:2022]. exceeds the maximum time of 100ms between the presentation of the voice and the video to the user [requirement number 6.5.4 Audio and video synchronization, of UNE-EN 301549:2022]. There may not be a mode for speaker identification for real-time sign language users [requirement number 6.5.6 Identification of the speaker with video communication, from UNE-EN 301549:2022]. Criterion 7 - Video capacity: Not applicable. It is possible that there is a player video that does not have an operating mode that allows displaying existing subtitles [requirement number 7.1.1 Subtitle playback, from UNE-EN 301549:2022]. It is possible that there is a video player that does not have an operating mode that allows the audio to be synchronized with the subtitles [requirement number 7.1.2 Subtitle synchronization, from UNE-EN 301549:2022]. It is possible that there is a video player that does not have a subtitle saving system [requirement number 7.1. 3 Preservation of subtitles, from 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, from UNE-EN 301549:2022] .It is possible that in all cases an operating mode that facilitates a spoken output of the available subtitles will not be provided [requirement number 7.1.5 Spoken subtitles, from UNE-EN 301549:2022]. It is possible that there is a player that does not has a way to select and play available audio descriptions [requirement number 7.2.1 Playing the audio description, from UNE-EN 301549:2022]. It is possible that there is a player that does not have a way to synchronize available audio descriptions [requirement number 7.2 .2 Synchronization of the audio description, from UNE-EN 301549:2022]. It is possible that there is a player that does not have a way to save available audio descriptions [requirement number 7.2.3 Preservation of the audio description, from UNE-EN 301549:2022 Some pages incorporate a video player that does not provide controls for the playback of 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, from 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 appropriate [requirement number 9.1.1.1 Non-textual content, from UNE-EN 301549:2022] .Some recorded videos do not have text-based alternatives or audio alternatives [requirement number 9.1.2.1 Audio only and video only, from UNE-EN 301549:2022]. Some recorded videos may not contain subtitles [requirement number 9.1.2.2 Subtitles (recorded), from UNE-EN 301549:2022]. Some pre-recorded videos on the website do not have audio description or alternative media [requirement number 9.1.2.3 Audio description or alternative media, from 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), from UNE-EN 301549:2022]. On some pages the information, structure and relationships are not determined by software or have no alternative such as text [requirement number 9.1.3.1 Information and relationships, from UNE-EN 301549:2022]. Some page does not have at least one correct reading sequence defined by the program [requirement number 9.1.3.2 Significant sequence, from UNE-EN 301549:2022 Identification of elements with only sensory characteristics such as shape, color, size, visual location, orientation or sound [requirement number 9.1.3.3 Sensory characteristics, from UNE-EN 301549:2022]. The content is not adapted when changing the orientation of the screen [requirement number 9.1.3.4 Orientation, from UNE-EN 301549:2022]. There are elements of forms in which the purpose of the entry is not identified [requirement number 9.1.3.5 Identify the purpose of entry , from UNE-EN 301549:2022]. On some pages, color has been used as the only visual means to transmit information, indicate an action, provoke a response or distinguish a visual element [requirement number 9.1.4.1 Use of color, from UNE -EN 301549:2022]. There are sound elements that play automatically and there is no mechanism to pause or stop it [requirement number 9.1.4.2 Audio control, from UNE-EN 301549:2022]. On some page the contrast ratio in text it 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 the text size and its possibility of customization when zooming [requirement number 9.1.4.4 Change of text size, from UNE-EN 301549:2022]. There are clipart images based only on text [requirement number 9.1.4.5 Text images, from UNE-EN 301549:2022]. There are errors when customize the font size, zoom level or text spacing [requirement number 9.1.4.10 Text readjustment, from UNE-EN 301549:2022]. Insufficient contrast in interface components or graphic objects [requirement number 9.1.4.11 Contrast of non-textual content, from 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, from UNE-EN 301549:2022]. When An element receives the pointer or keyboard focus, additional content is displayed that cannot be discarded without having to move the pointer or change the mouse focus [requirement number 9.1.4.13 Content with hover or focus, from UNE-EN 301549:2022 There are pages where keyboard navigation is not optimal and errors appear [requirement number 9.2.1.1 Keyboard, UNE-EN 301549:2022]. There are components that, upon receiving the focus, prevent it from being passed to another only with the tab or keys. direction keys [requirement number 9.2.1.2 Without focus traps, from UNE-EN 301549:2022]. There are keyboard shortcuts that do not work [requirement number 9.2.1.4 Shortcuts with character keys, from UNE-EN 301549:2022 There is some time limitation established that cannot be stopped, adjusted or extended [requirement number 9.2.2.1 Adjustable time, from UNE-EN 301549:2022]. There may be some information in automatic movement that does not have controls to pause, control or hide [requirement number 9.2.2.2 Pause, stop and hide, from UNE-EN 301549:2022]. There may be elements that flash more than three times in a second or above the general threshold [requirement number 9.2.3.1 Threshold of three flashes or less, from 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, from UNE-EN 301549:2022]. Inadequate description of some of the titles of the web pages [requirement number 9.2.4.2 Page titling, from UNE-EN 301549:2022]. In some documents, sequential navigation using the keyboard may not have a consistent order [requirement number 9.2. 4.3 Order of focus, from UNE-EN 301549:2022]. The purpose of the links, headers or labels of the portal may not always be sufficiently descriptive or consistent for all users [requirement number 9.2.4.4 Purpose of the links (in context), from UNE-EN 301549:2022]. Links to pages of related content or alternative forms of navigation are not always offered [requirement number 9.2.4.5 Multiple paths, from UNE-EN 301549:2022]. There are headers with repeated text and/or not very descriptive [requirement number 9.2.4.6 Headings and labels, from UNE-EN 301549:2022]. The location of the focus is not always visible when browsing with a keyboard [requirement number 9.2.4.7 Visible focus, from UNE-EN 301549:2022].There are elements that use multipoint or route-based that cannot be operated with just a pointer or without a route-based gesture [requirement number 9.2.5.1 Pointer gestures, from UNE-EN 301549:2022].There are pages where an event cannot be canceled by clicking the mouse [requirement number 9.2.5.2 Cancellation of the pointer, from 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 only operable 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 Language of the page, from UNE-EN 301549:2022]. There could be specific errors in editing and identification of the language in some part of the web page [requirement number 9.3.1.2 Language of the parts, from UNE-EN 301549:2022].There are components that when receiving the focus, initiate a context change [requirement number 9.3.2.1 Upon receiving the focus, from UNE-EN 301549:2022].The interaction of the user with some control causes page changes without prior warning [requirement number 9.3.2.2 When receiving entries, from 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 Coherent navigation, from 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, from UNE-EN 301549:2022].There are few error messages descriptive, or error messages that are not grouped into a single message as well as lack of suggestions in the form to fill in the fields correctly [requirement number 9.3.3.1 Identification of errors, from 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, from UNE-EN 301549:2022]. There could be an entry error in some field/ form in 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]. In data entry, errors are not detected nor is the user provided 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 and WAI-ARIA 1.1 tags and attributes [requirement number 9.4.1.1 Processing , from 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 accessibility guidelines [requirement number 9.4.1.2 Name, function, value, from UNE-EN 301549:2022]. On some pages the status messages may not be determined programmatically through functions or properties [requirement number 9.4.1.3 Status messages, from UNE-EN 301549:2022]. do not comply with some of the WCAG 2.1 requirements [requirement number 9.6 Conformity requirements of the WCAG guidelines, 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, from 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, from UNE-EN 301549:2022]. Videos may lack subtitles and audio descriptions [requirement number 10.1.2.2 Subtitles (recorded), from UNE-EN 301549:2022]. There may be no alternative for time-dependent media or an audio description for video content recorded within synchronized multimedia [requirement number 10.1.2.3 Audio description or alternative medium, from UNE-EN 301549:2022]. An audio description may not be provided for all video content recorded within multimedia content synchronized [requirement number 10.1.2.5 Audio description (recorded), from UNE-EN 301549:2022]. In some document 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 , from UNE-EN 301549:2022]. Some document does not have at least one correct reading sequence defined by the program [requirement number 10.1.3.2 Significant sequence, from UNE-EN 301549:2022]. There may be documents which do not exist another accessible alternative with which to operate and understand the content [requirement number 10.1.3.3 Sensory characteristics, from UNE-EN 301549:2022]. There may be documents whose content does not adapt when changing the orientation of the screen [requirement number 10.1. 3.4 Guidance, from UNE-EN 301549:2022]. In some forms, the input field that collects information about the user does not have the purpose identified [requirement number 10.1.3.5 Identify the purpose of entry, from UNE-EN 301549:2022] .In some documents, color has been used as the only visual means to transmit information, indicate an action, provoke a response or distinguish a visual element [requirement number 10.1.4.1 Use of color, from UNE-EN 301549:2022].There are elements audio in some document that plays automatically and there is no mechanism to pause or stop it [requirement number 10.1.4.2 Audio control, from UNE-EN 301549:2022]. In some document the contrast ratio in text may not be at least 4.5:1 [requirement number 10.1.4.3 Contrast (minimum), from UNE-EN 301549:2022]. In some texts the size cannot be changed by 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 expanded [requirement number 10.1.4.4 Change of text size, from UNE-EN 301549:2022]. In some documents, text images may have been used instead of text to transmit information [ requirement number 10.1.4.5 Text images, from UNE-EN 301549:2022]. In some document, the content may lose functionality or information when the content is expanded [requirement number 10.1.4.10 Readjustment of the text, from UNE-EN 301549:2022] .In some documents the contrast of the user interface components and graphic objects may not reach 3:1 with the adjacent colors [requirement number 10.1.4.11 Contrast of non-textual content, from UNE-EN 301549:2022].In For some texts, it is not possible to override the specified text spacing [requirement number 10.1.4.12 Text spacing, from 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, from UNE-EN 301549:2022. There are documents that cannot be operated entirely through the keyboard [requirement number 10.2.1.1 Keyboard, from UNE-EN 301549:2022]. some documents have not defined headings and cannot be navigated by keyboard [requirement number 10.2.1.2 Without focus traps, from UNE-EN 301549:2022]. In some documents there are keyboard shortcuts that do not work [requirement number 10.2.1.4 Shortcuts with character keys, from UNE-EN 301549:2022]. In some document there is established a time limitation that cannot be stopped, adjusted or extended [requirement number 10.2.2.1 Adjustable time, from UNE-EN 301549 :2022].Some document may contain information in automatic movement that does not have controls to pause, control or hide [requirement number 10.2.2.2 Pause, stop and hide, from UNE-EN 301549:2022].Some document may contain elements that flash more than three times in a second or above the general threshold [requirement number 10.2.3.1 Threshold of three flashes or less, from UNE-EN 301549:2022]. There may be documents that do not have a title [requirement number 10.2.4.2 Page titling, from UNE-EN 301549:2022]. In some documents, headings have not been defined and you cannot navigate by keyboard [requirement number 10.2.4.3 Focus order, from UNE-EN 301549:2022]. Some document may contain a link that may not have the specific purpose defined textually [requirement number 10.2.4.4 Purpose of links (in context), from UNE-EN 301549:2022]. In some document there may be a heading or some name of control that is not sufficiently descriptive of its purpose [requirement number 10.2.4.6 Headers and labels, of UNE-EN 301549:2022]. The location of the focus is not always visible when navigating with a keyboard through a document [requirement number 10.2. 4.7 Visible focus, from UNE-EN 301549:2022]. In some document there may be elements that use multipoint or route-based that cannot be operated with just a pointer or without a route-based gesture [requirement number 10.2.5.1 Gestures of the pointer, from UNE-EN 301549:2022]. There are documents where an event cannot be canceled by clicking the mouse [requirement number 10.2.5.2 Cancellation of the pointer, from UNE-EN 301549:2022]. There are documents that have some labels that that accompany the controls do not have the same name [requirement number 10.2.5.3 Name label, from UNE-EN 301549:2022]. There are documents whose functionality is only operable through movement [requirement number 10.2.5.4 Activation by movement, from 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 parties, from UNE-EN 301549:2022]. There may be components in a document that when it receives the focus, initiate a context change [requirement number 10.3.2.1 Upon receiving the focus, from UNE-EN 301549:2022]. The user's interaction with some control causes page changes without prior warning [requirement number 10.3.2.2 When receiving inputs, from UNE-EN 301549:2022]. There are input fields of data with the capacity for automatic error detection that does not identify where or how said error occurs [requirement number 10.3.3.1 Identification of errors, of UNE-EN 301549:2022]. In some form of a document, some change could occur of automatic context without warning the user [requirement number 10.3.3.2 Labels or instructions, from UNE-EN 301549:2022]. In some document there could be an entry error in a field/form for which the user is not notified of the suggestion to solve it [requirement number 10.3.3.3 Suggestions for errors, from UNE-EN 301549:2022]. In some document there may be a form for data collection or that compromises legally or financially that are not reversible, reviewable or have confirmation before sending them [ requirement number 10.3.3.4 Prevention of errors (legal, financial, data), from UNE-EN 301549:2022]. In some document there may be duplicate attributes and IDs [requirement number 10.4.1.1 Processing, from 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 accessibility guidelines [requirement number 10.4.1.2 Name, function, value, from 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, from UNE-EN 301549:2022]. Criterion 11 - Requirements applicable to software: Not applicable The visual user preferences of the browser are not respected on the page [requirement number 11.7 User preferences, of UNE-EN 301549:2022]. The information necessary for accessibility may not be compatible with the format used for the output of the authoring tool [requirement number 11.8.1 Content management technology, from 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 Content creation accessible, from 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, from UNE-EN 301549:2022]. There may not be a repair mechanism for the accessibility checker [requirement number 11.8.4 Repair service, from UNE-EN 301549:2022]. No template may be available that supports 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. Product documentation does not list or explain all available accessibility features [requirement number 12.1.1 Accessibility and compatibility features, from UNE-EN 301549:2022]. Product documentation may not be completely in accessible formats [requirement number 12.1.2 Accessible documentation , from UNE-EN 301549:2022]. Support services do not provide all the information on accessibility features that are included in the product documentation [requirement number 12.2.2 Information on accessibility and compatibility features, from UNE-EN 301549:2022]. EN 301549:2022]. Support services cannot always be adapted to the communication needs of users with disabilities [requirement number 12.2.3 Effective communication, from UNE-EN 301549:2022]. There may be documentation provided by the services support that is not in an accessible format [requirement number 12.2.4 Accessible documentation, from UNE-EN 301549:2022].
b. Disproportionate burden: Not applicable.
c. Content does not fall within the scope of applicable legislation:
There may be office files in PDF and other formats published before September 20, 2018 that do not fully meet all accessibility requirements. Although we have tried to ensure that most of them do comply. 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 the 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 any update or change in systems, not all generated or self-generated content may comply with all accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 06/06/2024
The method used to prepare the declaration has been a self-assessment carried out by the company itself.
Last revision of the declaration: 06/06/2024
Observations and contact information
You can make communications about accessibility requirements (article 10.2.a of Royal Decree 1112/2018, of September 7) such as, for example:
Report any possible non-compliance on the part of this website. Report other difficulties in accessing the content. Formulate any other query or suggestion for improvement regarding the accessibility of the website.
Through the following ways:
According to article 10.2.b of RD 1112/2018, you can also present:
A complaint regarding compliance with the requirements of RD 1112/2018. A request for accessible information regarding: Content that is excluded from the scope of application of RD 1112/2018 as established by article 3, section 4. Content that is exempt of compliance with accessibility requirements for imposing a disproportionate burden.
In the Request for accessible information, the facts, reasons and request must be clearly specified that allow us to verify that it is a reasonable and legitimate request.
Communications will be received and processed by the company management, as the unit responsible for the contents of this website.
Optional content
The currently visible version of this website is from 06/06/2024 and on that date the review of the accessibility level in force at that time was carried out.
From that date, partial daily reviews of new or modified web content are carried out, both of the templates and of the final published pages and documents, in order to ensure compliance with the accessibility requirements of the UNE-EN 301549 Standard. :2022, 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. Links offer 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 to adapt to current standards and regulations in relation to accessibility, complying with the priority 2 (AA) verification points defined in the Web Content Accessibility Guidelines (WCAG 2.1) specification. It is optimized for the latest current versions of Chrome, Edge, Firefox, Safari and Opera. It is designed for correct viewing on any resolution and desktop, tablet or mobile device (responsive design). It has been made using HTML5 as a markup language and CSS 3 style sheets for its design. .
In addition, continuous auditing and content review work is carried out to facilitate its interpretation and improve navigation through the web portal.
This Accessibility Declaration document has been created using the free online web accessibility declaration template generator on 06/06/2024.