1.Our commitment
We want everyone to be able to use QikTools, including people who use screen readers, keyboards, magnifiers, captions or other assistive technology. This statement covers www.qiktools.com and the tools inside it.
We also build tools that help our customers make their own pictures and videos accessible — alt text, captions, transcripts, audio description and checks — in the Accessibility Studio.
2.Conformance status
Our target is the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, the level referenced by the European standard EN 301 549. QikTools is partially conformant: some parts don’t fully meet the standard yet. They’re listed below.
This is our own assessment. We haven’t had an independent audit yet.
3.What we’ve done
- Buttons, menus, dialogs, switches and sliders are built on accessible components, with a visible focus outline for keyboard users.
- Most choice groups can be changed with the arrow keys, dialogs close with Escape, and most tools run with Ctrl or ⌘ + Enter.
- Pages declare their language and use headings, labelled form fields and navigation landmarks.
- Light and dark themes, with text colours chosen for readable contrast — we’re checking them against WCAG ratios as we go.
- Decorative animations (moving banners, floating and shimmering effects) stop when your device asks for reduced motion.
- Our video tools make captions, transcripts and audio description, and our Accessibility Studio checks videos for flashing that can trigger seizures (WCAG 2.3.1).
- AI-made pictures and videos carry an “AI-generated” label where the law requires it, and Content Credentials that anyone can check.
4.What isn’t accessible yet
- Creative editors. The Movie Director timeline, the Design Studio canvas and the image editor rely on dragging and visual editing, which aren’t fully usable with a keyboard or screen reader yet. Most actions also have buttons or fields; if you’re stuck, email us and we’ll help.
- What you make with AI. Pictures and videos made by AI don’t come with alt text or captions automatically. Add them before you publish — the Accessibility Studio does it in a few clicks.
- Motion. Not every animation follows the reduced-motion setting yet.
- Documents. Some PDFs we generate (for example exported reports) aren’t tagged for screen readers. Ask us for an accessible copy.
- Third-party pages. Checkout is run by our payment partner, and a few players and widgets come from other providers. We choose accessible partners but don’t control their pages.
We’re working through these, starting with the ones that block someone from using a tool at all.
5.Feedback and contact
If something on QikTools doesn’t work for you, or you need information in another format, email hello@qiktools.com with “Accessibility” in the subject. Tell us the page, what you were trying to do and the browser or assistive technology you use.
We aim to reply within 5 working days.
6.Enforcement
European Union. The European Accessibility Act exempts micro-enterprises providing services, and QikTools is a very small business — but we aim to meet the standard anyway. If you’re not satisfied with our response, you can contact the authority responsible for accessibility in your EU country.
India. Under the Rights of Persons with Disabilities Act, 2016, you can contact the Chief Commissioner for Persons with Disabilities, or the State Commissioner in your state.
Everywhere. You can also use our grievance procedure.
7.Technical information
QikTools relies on HTML, CSS, JavaScript and WAI-ARIA. It’s built for the latest versions of Chrome, Edge, Firefox and Safari.
This statement was prepared on 4 October 2026 by the developer, by checking pages with a keyboard, browser zoom, reduced-motion settings and automated code checks. We’ll review it at least once a year — next by October 2027 — and whenever we change the site significantly.