Accessibility Statement

Pvc Plus (hereinafter, also referred to as the Website) is partially compliant with Royal Decree 1112/2018, of September 7, due to the non-compliance of the aspects listed below.

Inaccessible Content

The content listed below is not accessible for the following reasons: a. Lack of compliance with RD 1112/2018: Does not apply. It meets 100% of the web accessibility criteria.
    • Criterion 5 – General requirements: Does not apply.
  • Non-compatible means may be required to activate some accessibility features [Requirement 5.2 Activation of accessibility features, UNE-EN 301549:2022].
    • Criterion 6 – Bidirectional voice communication capability: Does not apply.
  • It may not be possible to guarantee a frequency range with an upper limit of at least 7000Hz [Requirement 6.1 Bandwidth for voice, UNE-EN 301549:2022].
  • A bidirectional communication mode via RTT may not be provided [Requirement 6.2.1.1 RTT communication, UNE-EN 301549:2022].
  • A bidirectional voice and text communication mode may not be provided simultaneously [Requirement 6.2.1.2 Simultaneous voice and text, UNE-EN 301549:2022].
  • Text sent and received in RTT communications may not be clearly differentiated visually [Requirement 6.2.2.1 Visually differentiated display, UNE-EN 301549:2022].
  • The sending and receiving direction of RTT may not be determined by software [Requirement 6.2.2.2 Sending and receiving direction determinable by software, UNE-EN 301549:2022].
  • Speaker identification in RTT may not be provided [Requirement 6.2.2.3 Speaker identification, UNE-EN 301549:2022].
  • There may be no visual indicator on screen of real-time audio activity [Requirement 6.2.2.4 Visual indicator of real-time audio with text, UNE-EN 301549:2022].
  • Compatibility with other RTT systems may not be guaranteed [Requirement 6.2.3 Interoperability, UNE-EN 301549:2022].
  • RTT input may not be transmitted to the network within 500ms [Requirement 6.2.4 RTT response capability, UNE-EN 301549:2022].
  • No alternative to voice for assistance or interactive response tasks may be provided [Requirement 6.4 Alternatives to voice-based services, UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum QVGA resolution for 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 100ms between voice and video presentation to the user may not be met [Requirement 6.5.4 Audio and video synchronization, UNE-EN 301549:2022].
  • A mode for speaker identification for sign language users in real-time may not be available [Requirement 6.5.6 Speaker identification with video communication, UNE-EN 301549:2022].
    • Criterion 7 – Video capability: Does not apply.
  • Some video players may not have an operation mode that allows displaying existing subtitles [Requirement 7.1.1 Subtitle playback, UNE-EN 301549:2022].
  • Some video players may not have an operation mode that allows syncing audio with subtitles [Requirement 7.1.2 Subtitle synchronization, UNE-EN 301549:2022].
  • Some video players may not have a system for saving subtitles [Requirement 7.1.3 Subtitle preservation, UNE-EN 301549:2022].
  • Users may not be able to adapt subtitle features to their individual requirements [Requirement 7.1.4 Subtitle features, UNE-EN 301549:2022].
  • In all cases, a mode of operation that facilitates spoken output of available subtitles may not be provided [Requirement 7.1.5 Spoken subtitles, UNE-EN 301549:2022].
  • Some players may not have a mode to select and play available audio descriptions [Requirement 7.2.1 Audio description playback, UNE-EN 301549:2022].
  • Some players may not have a mode to sync available audio descriptions [Requirement 7.2.2 Audio description synchronization, UNE-EN 301549:2022].
  • Some players may not have a mode to save available audio descriptions [Requirement 7.2.3 Audio description preservation, UNE-EN 301549:2022].
  • Some pages include video players that do not provide controls for subtitle and audio description playback at the same level of interaction as other controls [Requirement 7.3 User controls for subtitles and audio description, UNE-EN 301549:2022].
    • Criterion 9 – Requirements for web pages: Does not apply.
    • Non-textual content may lack a textual alternative or may have an inadequate alternative [Requirement 9.1.1.1 Non-textual content, UNE-EN 301549:2022].
    • Some recorded videos may not have text-based or audio alternatives [Requirement 9.1.2.1 Audio-only and video-only, UNE-EN 301549:2022].
    • Some recorded videos may not have subtitles [Requirement 9.1.2.2 Subtitles (recorded), UNE-EN 301549:2022].
    • Some pre-recorded videos on the website may not have audio descriptions or alternative media [Requirement 9.1.2.3 Audio description or alternative media, UNE-EN 301549:2022].
    • Some pre-recorded videos on the website may not have audio descriptions or alternative media [Requirement 9.1.2.5 Audio description (recorded), UNE-EN 301549:2022].
    • Some pages may have information, structure, and relationships that are not determined by software or do not have an alternative in text [Requirement 9.1.3.1 Information and relationships, 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 Meaningful Sequence, from UNE-EN 301549:2022].
    • Identification of elements only with 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].
    • Content does not adapt when the screen orientation changes [Requirement number 9.1.3.4 Orientation, from UNE-EN 301549:2022].
    • There are form elements where the input purpose is not identified [Requirement number 9.1.3.5 Identify Input Purpose, from UNE-EN 301549:2022].
    • On some page, color is used as the only 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, from UNE-EN 301549:2022].
    • There are audio elements that play automatically and do not have a mechanism to pause or stop them [Requirement number 9.1.4.2 Audio Control, from UNE-EN 301549:2022].
    • On some page, the text contrast ratio might not be at least 4.5:1 [Requirement number 9.1.4.3 Contrast (Minimum), from UNE-EN 301549:2022].
    • There are errors on some pages related to text size and its customization possibility when zooming [Requirement number 9.1.4.4 Text Size Change, from UNE-EN 301549:2022].
    • There are pre-designed images based only on text [Requirement number 9.1.4.5 Text Images, from UNE-EN 301549:2022].
    • There are errors when customizing font size, zoom level, or text spacing [Requirement number 9.1.4.10 Text Adjustment, from UNE-EN 301549:2022].
    • Insufficient contrast in interface components or graphical objects [Requirement number 9.1.4.11 Contrast of Non-Text Content, from UNE-EN 301549:2022].
    • Text might not display correctly when changing spaces and line heights [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 shown that cannot be dismissed without moving the pointer or changing focus [Requirement number 9.1.4.13 Hover or Focus Content, from UNE-EN 301549:2022].
    • There are pages where keyboard navigation is not optimal and errors appear [Requirement number 9.2.1.1 Keyboard, from UNE-EN 301549:2022].
    • There are components that, when they receive focus, prevent tabbing or using directional keys to move focus [Requirement number 9.2.1.2 No Focus Traps, from UNE-EN 301549:2022].
    • There are keyboard shortcuts that do not work [Requirement number 9.2.1.4 Character Key Shortcuts, from UNE-EN 301549:2022].
    • A time limit is set that cannot be stopped, adjusted, or extended [Requirement number 9.2.2.1 Adjustable Time, from UNE-EN 301549:2022].
    • There may be automatic moving information that does not have controls to pause, stop, 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 per second or exceed the general threshold [Requirement number 9.2.3.1 Three Flashes or Less Threshold, from UNE-EN 301549:2022].
    • On some pages, there is no mechanism to skip content blocks that repeat across pages [Requirement number 9.2.4.1 Avoid Repeated Blocks, from UNE-EN 301549:2022].
    • Improper description of some page titles [Requirement number 9.2.4.2 Page Titles, from UNE-EN 301549:2022].
    • In some documents, sequential keyboard navigation may not have a consistent order [Requirement number 9.2.4.3 Focus Order, from UNE-EN 301549:2022].
    • The purpose of links, headers, or portal labels may not always be sufficiently descriptive or consistent for all users [Requirement number 9.2.4.4 Link Purpose (in Context), from UNE-EN 301549:2022].
    • Links to related content or alternative navigation methods are not always provided [Requirement number 9.2.4.5 Multiple Ways, from UNE-EN 301549:2022].
    • There are headers with repeated and/or non-descriptive text [Requirement number 9.2.4.6 Headers and Labels, from UNE-EN 301549:2022].
    • The focus location is not always visible when navigating with a keyboard [Requirement number 9.2.4.7 Visible Focus, from UNE-EN 301549:2022].
    • There are elements that use multipoint or path-based gestures that cannot be operated with only one pointer or without a path-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 Pointer Cancellation, from UNE-EN 301549:2022].
    • There are interface components without visible labels [Requirement number 9.2.5.3 Name Label, from UNE-EN 301549:2022].
    • There is functionality that is only operable through movement [Requirement number 9.2.5.4 Activation Through Movement, from UNE-EN 301549:2022].
    • On some page, the default language used is not indicated [Requirement number 9.3.1.1 Language of the Page, from UNE-EN 301549:2022].
    • There may be occasional language editing and identification failures on some parts of the website [Requirement number 9.3.1.2 Language of Parts, from UNE-EN 301549:2022].
    • There are components that, when receiving focus, initiate a change of context [Requirement number 9.3.2.1 Upon Receiving Focus, from UNE-EN 301549:2022].
    • User interaction with a control causes a page change without prior warning [Requirement number 9.3.2.2 Upon Receiving Input, from UNE-EN 301549:2022].
    • There may be pages with inconsistent navigation due to different links leading to the same destination [Requirement number 9.3.2.3 Consistent Navigation, from UNE-EN 301549:2022].
    • Certain interactive elements may not be presented consistently across 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 poorly descriptive error messages, or error messages that are not grouped into one, as well as lack of suggestions in forms for correctly filling out fields [Requirement number 9.3.3.1 Error Identification, from UNE-EN 301549:2022].
    • There are forms with mandatory fields where the user is not informed, and fields that lack an example of the required format [Requirement number 9.3.3.2 Labels or Instructions, from UNE-EN 301549:2022].
    • There may be an input error in a field/form where the user is not notified of the suggested solution [Requirement number 9.3.3.3 Suggestions for Errors, from UNE-EN 301549:2022].
    • In data entry, errors are not detected, nor is there an opportunity to correct them [Requirement number 9.3.3.4 Error Prevention (Legal, Financial, Data), from UNE-EN 301549:2022].
    • There may be errors in the use of HTML tags and WAI-ARIA 1.1 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 accessibility guidelines’ recommended structure [Requirement number 9.4.1.2 Name, Function, Value, from UNE-EN 301549:2022].
    • In some cases, there is improper labeling for assistive technologies [Requirement number 9.4.1.3 Status Messages, from 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-text content, UNE-EN 301549:2022].
  • There may be no equivalent alternative for content that is only audio or only pre-recorded video [requirement number 10.1.2.1 Only audio and only video, UNE-EN 301549:2022].
  • There may be videos without subtitles and audio descriptions [requirement number 10.1.2.2 Subtitles (recorded), UNE-EN 301549:2022].
  • There may be no alternative for time-dependent media or an audio description for recorded video content in synchronized multimedia [requirement number 10.1.2.3 Audio description or alternative media, UNE-EN 301549:2022].
  • An audio description may not be provided for all recorded video content within synchronized multimedia content [requirement number 10.1.2.5 Audio description (recorded), UNE-EN 301549:2022].
  • In some documents, the information, structure, and relationships are not determined by software or do not have a textual alternative [requirement number 10.1.3.1 Information and relationships, UNE-EN 301549:2022].
  • Some documents do not have at least one correct reading sequence defined by the program [requirement number 10.1.3.2 Meaningful sequence, UNE-EN 301549:2022].
  • There may be documents where no other accessible alternative exists to operate and understand the content [requirement number 10.1.3.3 Sensory characteristics, UNE-EN 301549:2022].
  • There may be documents whose content does not adapt when the screen orientation is changed [requirement number 10.1.3.4 Orientation, UNE-EN 301549:2022].
  • In some forms, the input field that collects user information does not have its purpose identified [requirement number 10.1.3.5 Identifying input purpose, UNE-EN 301549:2022].
  • In some documents, color has been used as the only 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, 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, UNE-EN 301549:2022].
  • In some documents, the contrast ratio in text might not be at least 4.5:1 [requirement number 10.1.4.3 Contrast (minimum), 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, content may lose functionality or information when zooming [requirement number 10.1.4.4 Text resizing, UNE-EN 301549:2022].
  • In some documents, text images may have been used instead of text to convey information [requirement number 10.1.4.5 Text images, UNE-EN 301549:2022].
  • In some documents, content may lose functionality or information when resizing the content [requirement number 10.1.4.10 Text reflow, UNE-EN 301549:2022].
  • In some documents, the contrast of user interface components and graphical objects may not reach 3:1 with adjacent colors [requirement number 10.1.4.11 Non-text content contrast, 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, UNE-EN 301549:2022].
  • The content of some documents does not receive keyboard focus, which would allow performing any action [requirement number 10.1.4.13 Content with hover or focus, UNE-EN 301549:2022].
  • There are documents where it is not possible to fully operate through the keyboard [requirement number 10.2.1.1 Keyboard, UNE-EN 301549:2022].
  • In some documents, headers have not been defined, and it is not possible to navigate via the keyboard [requirement number 10.2.1.2 No focus traps, UNE-EN 301549:2022].
  • In some documents, keyboard shortcuts do not work [requirement number 10.2.1.4 Keyboard shortcuts, UNE-EN 301549:2022].
  • In some documents, a time limitation is set that cannot be stopped, adjusted, or extended [requirement number 10.2.2.1 Adjustable time, UNE-EN 301549:2022].
  • Some documents may contain automatically moving information without controls to pause, control, or hide it [requirement number 10.2.2.2 Pause, stop, and hide, UNE-EN 301549:2022].
  • Some documents may contain elements that blink more than three times per second or exceed the general threshold [requirement number 10.2.3.1 Three flashes or less threshold, UNE-EN 301549:2022].
  • There may be documents that do not have a title [requirement number 10.2.4.2 Page titles, UNE-EN 301549:2022].
  • In some documents, headers have not been defined, and it is not possible to navigate via the keyboard [requirement number 10.2.4.3 Focus order, UNE-EN 301549:2022].
  • Some documents may contain links that may not have a clearly defined purpose in text [requirement number 10.2.4.4 Purpose of links (in context), UNE-EN 301549:2022].
  • In some documents, a header or control name may not be sufficiently descriptive of its purpose [requirement number 10.2.4.6 Headers and labels, UNE-EN 301549:2022].
  • The location of the focus is not always visible when navigating through the document via keyboard [requirement number 10.2.4.7 Visible focus, UNE-EN 301549:2022].
  • Some documents may have elements that use multi-point or path-based interactions that cannot be operated with just one pointer or without a path-based gesture [requirement number 10.2.5.1 Pointer gestures, UNE-EN 301549:2022].
  • There are documents where events cannot be canceled by clicking the mouse [requirement number 10.2.5.2 Pointer cancellation, UNE-EN 301549:2022].
  • There are documents where some labels accompanying controls do not have the same name [requirement number 10.2.5.3 Name of label, UNE-EN 301549:2022].
  • There are documents whose functionality can only be operated through movement [requirement number 10.2.5.4 Activation by movement, UNE-EN 301549:2022].
  • There may be documents where the main language is not identified [requirement number 10.3.1.1 Page language, UNE-EN 301549:2022].
  • There may be content or phrases within some documents where the language cannot be determined by the program [requirement number 10.3.2.1 Language of parts, UNE-EN 301549:2022].
  • There may be components in some documents that, when focused, initiate a context change [requirement number 10.3.2.1 Upon receiving focus, UNE-EN 301549:2022].
  • User interaction with some control causes page changes without prior notice [requirement number 10.3.2.2 Upon receiving input, UNE-EN 301549:2022].
  • There are data input fields with automatic error detection that do not identify where or how the error occurs [requirement number 10.3.3.1 Error identification, UNE-EN 301549:2022].
  • In some form of a document, there may be an automatic context change without notifying the user [requirement number 10.3.3.2 Labels or instructions, UNE-EN 301549:2022].
  • In some documents, there could be an input error in a field/form where the user is not notified of suggestions for correction [requirement number 10.3.3.3 Suggestions for errors, UNE-EN 301549:2022].
  • In some documents, there could be a form for collecting data or legal or financial commitments that are irreversible, not reviewable, or without confirmation before submission [requirement number 10.3.3.4 Error prevention (legal, financial, data), UNE-EN 301549:2022].
  • In some documents, there could be duplicate attributes and IDs [requirement number 10.4.1.1 Processing, UNE-EN 301549:2022].
  • In some documents, user interface components like 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, UNE-EN 301549:2022].
  • In some documents, status messages might not be programmatically determined through functions or properties [requirement number 10.4.1.3 Status messages, UNE-EN 301549:2022].
        • Criterion 11 – Requirements applicable to software: Not applicable.
  • The user’s visual preferences from the browser are not respected on the page [requirement number 11.7 User Preferences, UNE-EN 301549:2022].
  • The necessary information for accessibility might not be compatible with the format used for the output of the authoring tool [requirement number 11.8.1 Content Management Technology, UNE-EN 301549:2022].
  • There might not be a mechanism to create content in an accessible way [requirement number 11.8.2 Creating Accessible Content, UNE-EN 301549:2022].
  • There is no mechanism to preserve accessibility information during transformations [requirement number 11.8.3 Preserving Accessibility Information during Transformations, UNE-EN 301549:2022].
  • There might not be a mechanism for repairing the accessibility checker [requirement number 11.8.4 Repair Service, UNE-EN 301549:2022].
  • There might not be a template available that is compatible with content creation according to the requirements of chapters 9 (Web) or 10 (Non-web Documents) [requirement number 11.8.5 Templates, UNE-EN 301549:2022].
        • Criterion 12 – Requirements applicable to documentation and support services: Not applicable.
  • The product documentation does not list or explain all the available accessibility features [requirement number 12.1.1 Accessibility Features and Compatibility, UNE-EN 301549:2022].
  • The product documentation might not be fully available in accessible formats [requirement number 12.1.2 Accessible Documentation, UNE-EN 301549:2022].
  • Support services do not provide all the information about the accessibility features included in the product documentation [requirement number 12.2.2 Information on Accessibility Features and Compatibility, UNE-EN 301549:2022].
  • Support services are not always adaptable to the communication needs of users with disabilities [requirement number 12.2.3 Effective Communication, 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, UNE-EN 301549:2022].
b. Disproportionate burden: Not applicable. c. Content outside 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. However, efforts have been made to ensure that most of them do meet the requirements.
  • There may be third-party content 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 the entire website may have been created with a CMS (WordPress, Shopify, PrestaShop, etc.), so due to updates or changes in systems, not all content generated or auto-generated may comply with all accessibility regulations.

Preparación de la presente declaración de accesibilidad

La presente declaración fue preparada el día 10/09/2024 El método empleado para preparar la declaración ha sido una autoevaluación llevada a cabo por la propia empresa. Última revisión de la declaración: 10/09/2024

Observaciones y datos de contacto

Puede realizar comunicaciones sobre requisitos de accesibilidad (artículo 10.2.a del Real Decreto 1112/2018, de 7 de septiembre) como, por ejemplo:
  • Informar sobre cualquier posible incumplimiento por parte de este sitio web.
  • Transmitir otras dificultades de acceso al contenido.
  • Formular cualquier otra consulta o sugerencia de mejora relativa a la accesibilidad del sitio web.
A través de las siguientes vías:
  • Correo electrónico: rpelaez.pvc@gmail.com
  • Teléfono: 685 677 154
Acorde al artículo 10.2.b del RD 1112/2018, también puedes presentar:
  • Una queja relativa al cumplimiento de los requisitos del RD 1112/2018.
  • Una solicitud de información accesible relativa a:
    • Contenidos que están excluidos del ámbito de aplicación del RD 1112/2018 según lo establecido por el artículo 3, apartado 4.
    • Contenidos que están exentos del cumplimiento de los requisitos de accesibilidad por imponer una carga desproporcionada.
En la Solicitud de información accesible, se debe concretar, con toda claridad, los hechos, razones y petición que permitan constatar que se trata de una solicitud razonable y legítima. Las comunicaciones serán recibidas y tratadas por la dirección de la empresa, como unidad responsable de los contenidos de este sitio web.

Contenido opcional

La versión actualmente visible de este sitio web es del día 10/09/2024 y en esa fecha se hizo la revisión del nivel de accesibilidad vigente en aquel momento. A partir de dicha fecha se llevan a cabo revisiones parciales diarias del contenido web nuevo o modificado, tanto de las plantillas como de las páginas y documentos finales publicados, a fin de asegurar el cumplimiento de los requerimientos de accesibilidad de la Norma UNE-EN 301549:2022, considerando las excepciones del Real Decreto 1112/2018, de 7 de septiembre. Entre otras se adoptan las siguientes medidas para facilitar la accesibilidad:
  • Utilización de texto alternativo en las imágenes.
  • Los enlaces ofrecen detalles de la función o destino del hipervínculo.
  • Uso de los estándares del W3C: XHTML 1.0, CSS 3.0, WAI AA.

Compatibilidad

El sitio web:
  • se ha diseñado adaptándose a los estándares y normativas vigentes en relación a la accesibilidad, cumpliendo con los puntos de verificación de prioridad 2 (AA) definidos en la especificación de Pautas de Accesibilidad al Contenido en la Web (WCAG 2.1)
  • está optimizado para las últimas versiones vigentes de Chrome, Edge, Firefox, Safari y Opera
  • está diseñado para su correcta visualización en cualquier resolución y dispositivo de escritorio, tabletas o móviles (diseño responsive)
  • se ha realizado utilizando HTML5 como lenguaje de marcado y hojas de estilo CSS 3 para su diseño.
Además, se realiza un trabajo continuo de auditoría y revisión de contenidos para facilitar su interpretación y mejorar la navegación por el portal web.
Scroll to Top