Accessibility statement
- Last updated
- 4 August 2026
- Law as at
- 4 August 2026
COMPLETIO Sp. z o.o. wants completio.pl to be usable also when you do not use a mouse, when you rely on a screen reader, when you enlarge text, or when animation makes you unwell. Below we describe what we have done, what we still cannot do, and how to report a problem.
1. What this document is
This is a voluntary accessibility statement. Completio has no statutory obligation to publish it. We publish it because users have a right to know what to expect from the site, and because we should name our own shortcomings before somebody else does it for us.
This document is deliberately not an accessibility statement within the meaning of the Polish Act of 4 April 2019 on the digital accessibility of websites and mobile applications of public sector bodies. The reasons are set out in Legal basis.
The absence of a legal obligation does not make accessibility optional. Many of the online stores we work for are themselves covered by accessibility rules, and a supplier's website can form part of their assessment. We treat this as part of service quality, not as compliance paperwork.
2. Scope
This statement covers the completio.pl website together with its English version at /en/, across all pages published at those addresses.
This statement does not cover external services linked from the site (Google Maps, social media platforms), nor the systems Completio uses to serve customers outside the website.
This statement concerns the website only and does not cover the physical accessibility of Completio's office or warehouse. Please address questions about access to those premises to the contact details given under Reporting a problem and contact.
3. Conformance status
The site is partially conformant with WCAG 2.1 level AA. The exceptions are listed under Known limitations.
Our reference point is the EN 301 549 standard, which for web content points to WCAG 2.1 level AA. We chose it because it is the European technical standard for digital accessibility, not because any statute imposes it on us.
The standard adopted is WCAG 2.1 AA, and it is against that standard that we describe the state of the site. The site has not been reviewed against the criteria added in WCAG 2.2, so we make no claim of conformance with that version.
4. What the site provides
The points below were verified in the site's code and in the production build, rather than copied from a template:
- Keyboard operation. All interactive elements (navigation, mega menu, forms, the consent dialog, galleries) can be reached and operated from the keyboard. The privacy settings dialog traps focus, closes with Esc, and returns focus to the element that opened it.
- Visible focus. Interactive elements have their own high-contrast
focus-visiblestyle, rather than a browser default that was removed without a replacement. - Skip navigation. The first element in tab order is a „Skip to content" link that jumps to the main content of the page.
- Document structure. Every page has exactly one H1 heading, sections marked with lower-level headings, and a
mainelement. The page language is declared in the markup (lang="pl"andlang="en"). - Reduced motion. The site honors the system prefers-reduced-motion setting: when it is on, entrance animations, scroll-driven sequences and background video are disabled, and video is replaced with a still frame. There is no flashing content.
- Zoom and text reflow. The layout is fluid and responsive, and content does not require horizontal scrolling on narrow screens.
- Forms. Fields have associated labels, error messages are text and are linked to the field, and after a failed validation focus moves to the first field in error.
- Text alternatives. Images carrying meaning have alternative descriptions; purely decorative graphics are hidden from assistive technology (
aria-hidden). - No embedded content loaded without your knowledge. Google Maps loads only after you consent. Until then no assets are fetched from third-party servers, and typefaces are served from our own server.
5. Known limitations
We are aware of the shortcomings below. We list them deliberately instead of claiming full conformance:
Contrast of the animated dots in the opening section
In the opening section of the home page, orange dots tracing routes travel across the video. The heading text is legible thanks to the darkened overlay, but at the moment a dot passes directly beneath a letter of the heading, local contrast momentarily falls below the required threshold. The effect is transient and involves a purely decorative element a few pixels across. It has been measured and is scheduled for correction.
Workaround for users: turning on the system reduced-motion setting stops the animation.
Video captions are burned into the picture
Some video material on the site carries an audio track, and the player allows sound to be turned on. That material does have captions, but the captions are burned into the picture rather than supplied as a separate, programmatic caption track.
In practice this means spoken content is available to someone who cannot hear, but: the captions cannot be turned off or enlarged, a screen reader cannot read them, and they will not change contrast when system settings change. This is a departure from the WCAG 2.1 requirement on captions (level A). We also do not provide text transcripts.
The site's player is prepared to accept a separate captions file in the WebVTT format. The caption files have not yet been produced, so for the time being the captions remain burned into the picture. We state no date by which this will change: we will give one only when we are able to meet it.
If you need the content of a particular video in text form, write to us at the contact details given under Reporting a problem and contact. We will prepare a transcript.
English version and archive material
Articles in the Knowledge hub are currently available in Polish only, and images for some of them still come from the previous version of the site. We will check their alternative descriptions when the archive is migrated.
The list above rests solely on our own assessment and on what we measured in the code and in the production build. No external audit has been carried out, so departures we did not detect may exist. The method is described under How this assessment was made.
6. How this assessment was made
This statement was prepared on 29 July 2026 on the basis of a self-assessment carried out by the site's developer, the DigiAds agency.
Method: a review of the code covering document structure, keyboard operation and honoring of reduced-motion settings; a keyboard walkthrough of the site; measurement of text contrast against the background in sections built on video; and a check of the site's behavior before cookie consent is given.
No audit by an external body and no testing with users of assistive technology were carried out. That is a material limitation of this assessment and we say so plainly.
This means that this statement is the self-assessment of the site's developer, not the result of an independent accessibility audit. We do not conceal that: for a voluntary statement a self-assessment is acceptable, but it carries less evidential weight than an audit by an external body. Should Completio commission such an audit, we will add its outcome and date to this section.
7. Reporting a problem and contact
If there is something you cannot use, write to us. We treat such reports as bug reports, not as complaints.
| Channel | Details |
|---|---|
| biuro@completio.pl | |
| Telephone | +48 22 888 51 01 |
| Postal address | COMPLETIO Sp. z o.o., Sales Office, Al. Jana Pawła II 24, 05-250 Radzymin, Poland |
It helps if your report includes: the address of the page, a description of what you could not do, and which browser or assistive technology you were using. If you need content from the site in another form (for example a document in a format your screen reader can handle), write to us and we will prepare it.
Accessibility reports are received and handled by Completio at biuro@completio.pl. We respond to a report within 14 days of receiving it. If resolving the problem takes longer, we will write within that same period to say what we intend to do and when.
8. Legal basis and why this statement is voluntary
We examined the two legal regimes governing digital accessibility in Poland. Neither obliges Completio to publish this document:
- The Act of 4 April 2019 on the digital accessibility of websites and mobile applications of public sector bodies (consolidated text: Journal of Laws 2023, item 1440). Its Article 2 sets out a closed list of addressees: public finance sector entities, bodies financed or controlled by the public sector, and specified non-governmental organizations. Completio, as a private limited liability company without public funding or supervision, falls into none of those categories. The duty to publish an accessibility statement (Article 10 of that Act) and the official template for such a statement arise from that Act alone.
- The Act of 26 April 2024 on ensuring that economic operators meet the accessibility requirements for certain products and services (Journal of Laws 2024, item 731), implementing Directive (EU) 2019/882 (the European Accessibility Act) and applicable from 28 June 2025. Its Article 3(2) covers a closed list of services offered or provided to consumers, including e-commerce services. Article 5(32) defines e-commerce as a service provided at the individual request of a consumer with a view to concluding a contract, and Article 5(14) excludes from the notion of a consumer anyone acting for purposes related to a business activity.
Completio provides fulfillment and logistics services to businesses, and completio.pl is an informational site with contact forms: it does not allow a contract to be concluded, and it has no sales, cart, payments or user accounts. Logistics services also do not appear in the list of services covered by the 2024 Act.
This assessment concerns the site as it stands today. Launching sales, online ordering, or an account allowing a contract to be concluded with a private individual would change it and could bring the site within the 2024 Act, together with its information duties (Article 32(2)). In that event this statement requires a fresh review.