Accessibility Statement
We want as many people as possible to be able to use quidly. This statement describes the current state of accessibility of our service, known limitations, and how you can report barriers to us.
Scope
This statement applies to the website quidly.de and the web application available at app.quidly.de.
The applicable standard is WCAG 2.1 Level AA (via the harmonised standard EN 301 549), as referenced by the German Accessibility Reinforcement Act (BFSG) for digital services. The assessment is based on a self-evaluation.
Conformance status
In our assessment, quidly is partially conformant with WCAG 2.1 AA. "Partially conformant" means that most requirements are met, but some content has not yet been fully tested or implemented.
We review accessibility on an ongoing basis — including automated tests (axe-core) and static code analysis — and are currently completing a full manual review (keyboard operation, screen readers, zoom and reflow, colour contrast).
Known limitations
Some areas of the web application have not yet been conclusively reviewed for accessibility by hand. If you encounter barriers there, please let us know — we will fix them as quickly as possible.
Reporting barriers (feedback)
Have you found a barrier, or do you need content in a form accessible to you? Please get in touch:
Email: kontakt@quidly.de
Contact form: quidly.de/contact
We usually confirm receipt of your feedback within two business days and let you know how we will address your request.
Enforcement procedure
If you are not satisfied with our response, you can contact the competent market surveillance authority. For the accessibility of products and services under the BFSG, the Market Surveillance Body of the Federal States for the Accessibility of Products and Services (MLBF) is responsible.
Note: This statement is for information purposes. The exact responsibility and the course of any procedure are governed by the applicable statutory provisions.
Preparation of this statement
This statement was prepared on June 23, 2026. It is based on a self-evaluation against WCAG 2.1 AA / EN 301 549, supported by automated tests. It is updated for significant changes and in the course of the ongoing manual review.