info@print-makers.com
93 453 17 36
Request your quote

Accessibility Statement

https://print-makers.com/Compliance status

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

Non-accessible content

The content listed below is not accessible for the following reasons:

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

    • Criterion 5 – General requirements: Not applicable.

Some incompatible means may be required to activate an accessibility feature [requirement 5.2 Activation of accessibility features, 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 7000 Hz [requirement 6.1 Voice bandwidth, UNE-EN 301549:2022].
  • It may not be possible to provide a two-way communication mode using RTT [requirement 6.2.1.1 Communication using RTT, UNE-EN 301549:2022].
  • It may not be possible to provide a two-way communication mode with simultaneous voice and text [requirement 6.2.1.2 Simultaneous voice and text, UNE-EN 301549:2022].
  • It may not clearly differentiate on screen text sent from text received 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 sending and receiving direction of RTT [requirement 6.2.2.2 Sending/receiving direction determinable by software, UNE-EN 301549:2022].
  • It may not be possible to provide speaker identification in RTT [requirement 6.2.2.3 Speaker identification, UNE-EN 301549:2022].
  • There may be no 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 with RTT functionality [requirement 6.2.3 Interoperability, UNE-EN 301549:2022].
  • It may not be possible to ensure 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 to perform interactive support/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 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 100 ms between voice and video presentation to the user may not be met [requirement 6.5.4 Audio/video synchronization, 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.
  • There may be a video player without an operating mode that allows existing captions to be displayed [requirement 7.1.1 Caption playback, UNE-EN 301549:2022].
  • There may be a video player without an operating mode that allows audio to be synchronized with captions [requirement 7.1.2 Caption synchronization, UNE-EN 301549:2022].
  • There may be a video player without a caption saving/preservation system [requirement 7.1.3 Preservation of captioning, UNE-EN 301549:2022].
  • Users may not be able to adapt caption characteristics to their individual requirements [requirement 7.1.4 Caption characteristics, UNE-EN 301549:2022].
  • In some cases, an operating mode that facilitates spoken output of available captions may not be provided [requirement 7.1.5 Spoken captions, UNE-EN 301549:2022].
  • There may be a player without a mode to select and play available audio descriptions [requirement 7.2.1 Audio description playback, UNE-EN 301549:2022].
  • There may be a player without a mode to synchronize available audio descriptions [requirement 7.2.2 Audio description synchronization, UNE-EN 301549:2022].
  • There may be a player without a mode to save available audio descriptions [requirement 7.2.3 Preservation of audio description, UNE-EN 301549:2022].
  • Some pages include a video player that does not provide controls for captioning and audio description at the same interaction level as other 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 alternative [requirement 9.1.1.1 Non-text content, UNE-EN 301549:2022].
  • Some recorded videos do not have text-based alternatives or an audio alternative [requirement 9.1.2.1 Audio-only and video-only (recorded), UNE-EN 301549:2022].
  • Some recorded videos may not contain captions [requirement 9.1.2.2 Captions (recorded), UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative media [requirement 9.1.2.3 Audio description or media alternative (recorded), UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative media [requirement 9.1.2.5 Audio description (recorded), 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 correct reading sequence programmatically defined [requirement 9.1.3.2 Meaningful sequence, UNE-EN 301549:2022].
  • Elements may be identified solely through sensory characteristics such as shape, color, size, visual location, orientation, or sound [requirement 9.1.3.3 Sensory characteristics, UNE-EN 301549:2022].
  • Content does not adapt when the screen orientation changes [requirement 9.1.3.4 Orientation, UNE-EN 301549:2022].
  • There are form elements where the purpose of the input is not identified [requirement 9.1.3.5 Identify input purpose, UNE-EN 301549:2022].
  • On some pages, color has been used as the only visual means to convey information, indicate an action, prompt a response, or distinguish a visual element [requirement 9.1.4.1 Use of color, UNE-EN 301549:2022].
  • There are sounds that play automatically and there is no mechanism to pause or stop them [requirement 9.1.4.2 Audio control, UNE-EN 301549:2022].
  • On some pages, the contrast ratio for text may not be at least 4.5:1 [requirement 9.1.4.3 Contrast (minimum), UNE-EN 301549:2022].
  • There are errors on some pages related to text size and its ability to be customized when zooming [requirement 9.1.4.4 Resize text, UNE-EN 301549:2022].
  • There are pre-designed images based only on text [requirement 9.1.4.5 Images of text, UNE-EN 301549:2022].
  • There are errors when customizing font size, zoom level or text spacing [requirement 9.1.4.10 Reflow, UNE-EN 301549:2022].
  • Insufficient contrast in interface components or graphical objects [requirement 9.1.4.11 Non-text contrast, UNE-EN 301549:2022].
  • There is text that is not displayed correctly when changing spacing and line heights [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 focus [requirement 9.1.4.13 Content on hover or focus, UNE-EN 301549:2022].
  • There are pages where keyboard navigation is not optimal and errors appear [requirement 9.2.1.1 Keyboard, UNE-EN 301549:2022].
  • There are components that, when focused, prevent focus from moving to another using only Tab or arrow keys [requirement 9.2.1.2 No keyboard trap, UNE-EN 301549:2022].
  • There are keyboard shortcuts that do not work [requirement 9.2.1.4 Character key shortcuts, UNE-EN 301549:2022].
  • A time limit is 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 that does not provide controls to pause, stop, or hide it [requirement 9.2.2.2 Pause, stop, hide, UNE-EN 301549:2022].
  • There may be elements that flash more than three times in one second or above the general threshold [requirement 9.2.3.1 Three flashes or below threshold, UNE-EN 301549:2022].
  • On some pages there is no mechanism to skip blocks of content that are repeated on multiple pages [requirement 9.2.4.1 Bypass blocks, UNE-EN 301549:2022].
  • Inadequate descriptions of some web page titles [requirement 9.2.4.2 Page titled, UNE-EN 301549:2022].
  • In some documents, sequential keyboard navigation may not have a consistent order [requirement 9.2.4.3 Focus order, UNE-EN 301549:2022].
  • The purpose of links, headings, or labels on the portal 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 pages or alternative ways of navigating are not always offered [requirement 9.2.4.5 Multiple ways, UNE-EN 301549:2022].
  • There are headings with repeated and/or not very descriptive text [requirement 9.2.4.6 Headings and labels, UNE-EN 301549:2022].
  • The focus indicator is not always visible when navigating by 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].
  • There are pages where a mouse event cannot be cancelled [requirement 9.2.5.2 Pointer cancellation, UNE-EN 301549:2022].
  • There are interface components that do not have visible labels [requirement 9.2.5.3 Label in name, UNE-EN 301549:2022].
  • Some functionality is only operable by motion [requirement 9.2.5.4 Motion actuation, UNE-EN 301549:2022].
  • On some pages, the default language in use is not indicated [requirement 9.3.1.1 Language of page, UNE-EN 301549:2022].
  • There may be occasional editing and language-identification issues in some parts of the website [requirement 9.3.1.2 Language of parts, UNE-EN 301549:2022].
  • There are components that, when focused, initiate a change of context [requirement 9.3.2.1 On focus, UNE-EN 301549:2022].
  • User interaction with some controls causes page changes without prior warning [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 may not be presented consistently, as they are displayed with different visual styles [requirement 9.3.2.4 Consistent identification, UNE-EN 301549:2022].
  • There are non-descriptive error messages, or error messages are not grouped into a single message, and there are missing suggestions to complete form fields correctly [requirement 9.3.3.1 Error identification, UNE-EN 301549:2022].
  • There are forms with required fields where users are not informed, and fields may lack a textual example of the expected format [requirement 9.3.3.2 Labels or instructions, UNE-EN 301549:2022].
  • There may be an input error in a field/form for which the user is not notified of a suggested fix [requirement 9.3.3.3 Error suggestion, UNE-EN 301549:2022].
  • Data entry errors are not detected and the user is not provided 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, user interface components such as form elements, links and script-generated components do not follow the structure recommended by 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 roles or properties [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 do not have an appropriate text alternative [requirement 10.1.1.1 Non-text content, UNE-EN 301549:2022].
  • There may be no equivalent alternative for recorded audio-only or video-only content [requirement 10.1.2.1 Audio-only and video-only (recorded), UNE-EN 301549:2022].
  • Videos may lack captions and audio descriptions [requirement 10.1.2.2 Captions (recorded), UNE-EN 301549:2022].
  • There may be no alternative for time-based media or audio description for recorded video content in synchronized multimedia [requirement 10.1.2.3 Audio description or media alternative, UNE-EN 301549:2022].
  • Audio description may not be provided for all recorded video content within synchronized multimedia [requirement 10.1.2.5 Audio description (recorded), UNE-EN 301549:2022].
  • In some documents, information, structure and relationships are not programmatically determined or do not have a text alternative [requirement 10.1.3.1 Info and relationships, UNE-EN 301549:2022].
  • Some documents do not have at least one correct reading sequence programmatically defined [requirement 10.1.3.2 Meaningful sequence, UNE-EN 301549:2022].
  • There may be documents with no other accessible alternative to operate and understand the content [requirement 10.1.3.3 Sensory characteristics, UNE-EN 301549:2022].
  • There may be documents whose content does not adapt when the screen orientation changes [requirement 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 10.1.3.5 Identify input purpose, UNE-EN 301549:2022].
  • In some documents, color 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 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 10.1.4.2 Audio control, UNE-EN 301549:2022].
  • In some documents, the contrast ratio for text may not be at least 4.5:1 [requirement 10.1.4.3 Contrast (minimum), UNE-EN 301549:2022].
  • In some texts, the size cannot be increased up to 200% without loss of content or functionality, and in some documents content may lose functionality or information when enlarged [requirement 10.1.4.4 Resize text, UNE-EN 301549:2022].
  • In some documents, images of text may have been used instead of text to convey information [requirement 10.1.4.5 Images of text, UNE-EN 301549:2022].
  • In some documents, content may lose functionality or information when enlarged [requirement 10.1.4.10 Reflow, UNE-EN 301549:2022].
  • In some documents, contrast of user interface components and graphical objects may not reach 3:1 against adjacent colors [requirement 10.1.4.11 Non-text contrast, UNE-EN 301549:2022].
  • In some texts, it is not possible to override the specified text spacing [requirement 10.1.4.12 Text spacing, UNE-EN 301549:2022].
  • The content of some documents does not receive keyboard focus to perform any action [requirement 10.1.4.13 Content on hover or focus, UNE-EN 301549:2022].
  • There are documents that cannot be fully operated via keyboard [requirement 10.2.1.1 Keyboard, UNE-EN 301549:2022].
  • In some documents, headings are not defined and keyboard navigation is not possible [requirement 10.2.1.2 No keyboard trap, UNE-EN 301549:2022].
  • In some documents, character-key shortcuts do not work [requirement 10.2.1.4 Character key shortcuts, UNE-EN 301549:2022].
  • In some documents, a time limit is set that cannot be stopped, adjusted, or extended [requirement 10.2.2.1 Timing adjustable, UNE-EN 301549:2022].
  • Some documents may contain automatically moving information without controls to pause, stop, or hide it [requirement 10.2.2.2 Pause, stop, hide, UNE-EN 301549:2022].
  • Some documents may contain elements that flash more than three times per second or above the general threshold [requirement 10.2.3.1 Three flashes or below threshold, UNE-EN 301549:2022].
  • There may be documents that do not have a title [requirement 10.2.4.2 Page titled, UNE-EN 301549:2022].
  • In some documents, headings are not defined and keyboard navigation is not possible [requirement 10.2.4.3 Focus order, UNE-EN 301549:2022].
  • Some documents may contain a link whose specific purpose may not be defined textually [requirement 10.2.4.4 Link purpose (in context), UNE-EN 301549:2022].
  • In some documents, a heading or control name may not be sufficiently descriptive of its purpose [requirement 10.2.4.6 Headings and labels, UNE-EN 301549:2022].
  • The focus indicator is not always visible when navigating by keyboard in some documents [requirement 10.2.4.7 Focus visible, UNE-EN 301549:2022].
  • In some documents, elements using multipoint or path-based gestures cannot be operated with a single pointer or without a path-based gesture [requirement 10.2.5.1 Pointer gestures, UNE-EN 301549:2022].
  • There are documents where a mouse event cannot be cancelled [requirement 10.2.5.2 Pointer cancellation, UNE-EN 301549:2022].
  • There are documents where some labels that accompany controls do not have the same name [requirement 10.2.5.3 Label in name, UNE-EN 301549:2022].
  • There are documents whose functionality is only operable by motion [requirement 10.2.5.4 Motion actuation, UNE-EN 301549:2022].
  • There may be documents where the primary language is not identified [requirement 10.3.1.1 Language of page, UNE-EN 301549:2022].
  • There may be content or phrases within some documents whose language cannot be programmatically determined [requirement 10.3.2.1 Language of parts, UNE-EN 301549:2022].
  • There may be components in a document that, when focused, initiate a change of context [requirement 10.3.2.1 On focus, UNE-EN 301549:2022].
  • User interaction with some controls causes page changes without prior warning [requirement 10.3.2.2 On input, UNE-EN 301549:2022].
  • There are data entry fields with automatic error detection that do not identify where or how the error occurs [requirement 10.3.3.1 Error identification, UNE-EN 301549:2022].
  • In some forms within a document, an automatic context change may occur without warning the user [requirement 10.3.3.2 Labels or instructions, UNE-EN 301549:2022].
  • In some documents, there may be an input error in a field/form for which the user is not notified of a suggested fix [requirement 10.3.3.3 Error suggestion, UNE-EN 301549:2022].
  • In some documents, there may be a form for data collection that has legal/financial implications that is not reversible, reviewable, or does not have confirmation before submission [requirement 10.3.3.4 Error prevention (legal, financial, data), UNE-EN 301549:2022].
  • In some documents, there may be duplicate attributes and IDs [requirement 10.4.1.1 Parsing, 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 10.4.1.2 Name, role, value, UNE-EN 301549:2022].
  • In some documents, status messages may not be programmatically determined through roles or properties [requirement 10.4.1.3 Status messages, UNE-EN 301549:2022].
    • Criterion 11 – Requirements applicable to software: Not applicable.
  • The browser’s visual preferences are not respected on the page [requirement 11.7 User preferences, UNE-EN 301549:2022].
  • The information required for accessibility may not be compatible with the format used for the authoring tool output [requirement 11.8.1 Content management technology, UNE-EN 301549:2022].
  • There may be no mechanism enabling content to be created in an accessible way [requirement 11.8.2 Accessible content creation, UNE-EN 301549:2022].
  • There is no mechanism to preserve accessibility information during transformations [requirement 11.8.3 Preservation of accessibility information during transformations, UNE-EN 301549:2022].
    There may be no accessibility checker repair mechanism [requirement 11.8.4 Repair service, UNE-EN 301549:2022].
  • There may be no template available that supports creating content compliant with the requirements of chapters 9 (Web) or 10 (Non-web documents) [requirement 11.8.5 Templates, 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 12.1.1 Accessibility and compatibility features, UNE-EN 301549:2022].
  • Product documentation may not be fully available in accessible formats [requirement 12.1.2 Accessible documentation, UNE-EN 301549:2022].
  • Support services do not provide all information about accessibility and compatibility features included in the product documentation [requirement 12.2.2 Information on accessibility and compatibility features, UNE-EN 301549:2022].
  • Support services may not always be adaptable to the communication needs of users with disabilities [requirement 12.2.3 Effective communication, UNE-EN 301549:2022].
  • Documentation provided by support services may not be in an accessible format [requirement 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 20 September 2018 that do not fully meet all accessibility requirements, although efforts have been made to ensure that most of them do comply.
  • There may be third-party content not developed by this Unit nor under its control, such as images, interactive maps, videos, documents, players, etc.
  • There may be pre-recorded 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.), so due to updates or changes in the systems, not all generated or auto-generated content may comply with all accessibility standards.

Preparation of this accessibility statement

This statement was prepared on 20/11/2025.

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

Last review of the statement: 20/11/2025.

Observations and contact details

You may submit communications regarding accessibility requirements (Article 10.2.a of Royal Decree 1112/2018 of 7 September), for example:

  • Reporting any possible non-compliance by this website.
  • Reporting other difficulties in accessing content.
  • Submitting any other query or suggestion for improvement related to the website’s accessibility.

Through the following channels:

  • Email: info@print-makers.com
  • Telephone: B08923542

In accordance with Article 10.2.b of Royal Decree 1112/2018, you may also submit:

  • A complaint regarding compliance with the requirements of Royal Decree 1112/2018.
  • A request for accessible information relating to:
    • Content excluded from the scope of Royal Decree 1112/2018 as set out in Article 3(4).
    • Content exempt from compliance with accessibility requirements due to imposing a disproportionate burden.

In the request for accessible information, the facts, reasons and request must be clearly specified so that it can be established that the request is reasonable and legitimate.

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

Optional content

The currently visible version of this website is dated 20/11/2025, and on that date the accessibility level 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 the final published pages and documents—in order to ensure compliance with the accessibility requirements of Standard UNE-EN 301549:2022, taking into account the exceptions in Royal Decree 1112/2018 of 7 September.

Among other measures, the following 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.

Compatibility

The website:

  • Has been designed in accordance with current accessibility standards and regulations, meeting Priority 2 (AA) checkpoints defined in the Web Content Accessibility Guidelines (WCAG 2.1).
  • Is optimized for the latest current versions of Chrome, Edge, Firefox, Safari and Opera.
  • Is designed for correct display at any resolution and on any desktop, tablet or mobile device (responsive design).
  • Has been built using HTML5 as the markup language and CSS 3 stylesheets for its design.

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