ACCESSIBILITY STATEMENT
\nAt COMMUN, we are committed to ensuring accessibility of our website in accordance with the Royal Decree 1112\/2018, dated
\nSeptember 7, regarding the accessibility of websites and mobile applications in the public sector. This accessibility statement pertains to the website https:\/\/commun.digital.
\nCOMPLIANCE STATUS
\nThis website is partially compliant with RD 1112\/2018 due to exceptions and non-conformities detailed below.
\nINACCESSIBLE CONTENT
\nThe following content is not accessible due to:
\nNon-compliance with RD 1112\/2018:
\n\uf0b7 Logos and images lacking or having incorrect alternative text, and complex images without textual description [requirement
\nnumber 9.1.1.1 Non-text content, of UNE-EN 301549:2022].
\n\uf0b7 Lists created improperly (without list tags), tables with incorrectly labeled cells, and invisible labels on form elements
\n[requirement number 9.1.3.1 Information and relationships, of UNE-EN 301549:2022].
\n\uf0b7 Tables not adjusted for small screen sizes and form fields not displaying correctly on small screens [requirement number
\n9.1.4.10 Reflow, of UNE-EN 301549:2022].
\n\uf0b7 Text not displaying correctly when changing spaces and line heights [requirement number 9.1.4.12 Text spacing, of UNE-EN
\n301549:2022].
\n\uf0b7 Elements inaccessible by keyboard, such as social media links, text editor for comments, sorting elements for search results,
\nsearch result pagination, or calendar arrows [requirement number 9.2.1.1 Keyboard, of UNE-EN 301549:2022].
\n\uf0b7 Elements not receiving focus and therefore not interactable via keyboard, e.g., [requirement number 9.2.4.3 Focus order, of UNE-
\nEN 301549:2022].
\n\uf0b7 Links not properly identified in function (inadequate descriptions, generic text, inappropriate titles, etc.) [requirement
\nnumber 9.2.4.4 Link purpose, of UNE-EN 301549:2022].<\/p>\n
\uf0b7 Repetitive and\/or uninformative headings [requirement number 9.2.4.6 Headings and labels, of UNE-EN 301549:2022].
\n\uf0b7 Images, infographics, link texts or buttons, headline texts, and content not translated into other languages [requirement
\nnumber 9.3.1.2 Language of parts, of UNE-EN 301549:2022].
\n\uf0b7 Use of the same icon for different purposes, leading to confusion [requirement number 9.3.2.4 Consistent identification, of UNE-
\nEN 301549:2022].
\n\uf0b7 Lack of descriptive error messages, ungrouped error messages, and lack of suggestions in forms for filling fields correctly
\n[requirement number 9.3.3.1 Error identification, of UNE-EN 301549:2022].
\n\uf0b7 Forms with mandatory fields not notifying users, and fields lacking textual examples of field format (e.g., the ID)
\n[requirement number 9.3.3.2 Labels and instructions, of UNE-EN 301549:2022].
\n\uf0b7 Form fields informing of errors when incorrect values are entered but not providing correction suggestions [requirement
\nnumber 9.3.3.3 Error suggestions, of UNE-EN 301549:2022].
\n\uf0b7 Pages with syntax errors causing some assistive technology misinterpretation (duplicate page IDs, unclosed tags, incorrect
\ntag construction, etc.) [requirement number 9.4.1.1 Processing, of UNE-EN 301549:2022].
\n\uf0b7 Pages where assistive technologies cannot obtain information, interact, or be aware of user interface control statuses, e.g., help
\nmessages, action result status messages, link attributes, page language image… which cannot be read by screen readers when
\nthey appear [requirement number 9.4.1.2 Name, function, value of UNE-EN 301549:2022].
\n\uf0b7 Possible occasional editing errors on some web pages.
\nDISPROPORTIONATE BURDEN
\nNot applicable.
\nContent outside the scope of applicable legislation:
\nThere may be office document files in PDF or other formats published before September 20, 2018, that do not fully comply with all
\naccessibility requirements. Although efforts have been made to ensure that the majority of them do comply.
\nPREPARATION OF THIS ACCESSIBILITY STATEMENT<\/p>\n
This statement was prepared on 10\/03\/2024. The method used for preparation was self-assessment conducted by the entity. Last review of the statement: 10\/03\/2024.
\nCOMMENTS AND CONTACT DETAILS
\nYou can communicate accessibility requirements (article 10.2.a) of RD 1112\/2018) such as:
\n\uf0b7 Reporting any potential non-compliance by this website.
\n\uf0b7 Conveying other accessibility challenges to content.
\n\uf0b7 Making any other queries or suggestions for improvement regarding website accessibility.
\nThrough the following contact form.
\nYou can submit:
\n\uf0b7 A Complaint regarding compliance with the requirements of RD 1112\/2018 or
\n\uf0b7 An Accessible Information Request concerning:
\n\uf0b7 Content excluded from the scope of RD 1112\/2018 as per article 3, section 4.
\n\uf0b7 Content exempt from accessibility requirement compliance due to imposing a disproportionate burden.
\nFor an Accessible Information Request, clearly state the facts, reasons, and request to demonstrate it's a reasonable and legitimate request.
\nOPTIONAL CONTENT
\nThis website applies the requirements of UNE-EN 301549:2022 considering exceptions of RD 1112\/2018. The last accessibility review was conducted on 10\/03\/2024. The website is optimized for Microsoft Internet Explorer 8.0 or higher browsers and the latest versions of FireFox, Safari, Opera, and Google Chrome. The recommended minimum web resolution is 1280\u00d71024. The website is designed for Responsive viewing, optimizing display on tablet and mobile devices.
\nIt's optimized for viewing on the latest versions of Chrome for mobile, Firefox for mobile, Safari mobile, Opera Mini, and the native Android browser on these devices.<\/p>\n","protected":false},"excerpt":{"rendered":"ACCESSIBILITY STATEMENT At COMMUN, we are committed to ensuring accessibility of our website in accordance with the Royal Decree 1112\/2018, dated September 7, regarding the accessibility of websites and mobile applications in the public sector. This accessibility statement pertains to the website https:\/\/commun.digital. COMPLIANCE STATUS This website is partially compliant with RD 1112\/2018 due to… View Article<\/a>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"template-legal.php","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-1012","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\n