Trust center · Accessibility
Accessibility statement
miniailabs.in aims to conform to WCAG 2.2 at level AA. This statement says how we test, what we have and have not checked yet, the limits we know about, and how to tell us when something gets in your way.
| Criterion | How we check | Last run | Result |
|---|---|---|---|
| Text and control contrast | Every colour token measured with the WCAG relative-luminance formula, in the dark and the light theme | 17 Oct 2026 | Body, caption and state colours at 4.5:1 or more on every surface; form-control borders at 3:1 or more |
| Automated scan | axe-core through Playwright on every page type, failing on any serious or critical issue | Scheduled: pre-launch audit | Results and date published here after the run |
| Keyboard-only use | Tab, Shift+Tab, Enter, Space and Escape through navigation, menus, forms, FAQs and the chat | Scheduled: pre-launch audit | Results and date published here after the run |
| Screen readers | NVDA with Chrome on Windows and VoiceOver with Safari on iOS, on a page of each type, the contact form and the chat | Scheduled: pre-launch audit | Results and date published here after the run |
| Reduced motion | Reduce-motion setting on: 3D scenes and loops must show a still image and nothing may depend on animation | Scheduled: pre-launch audit | Results and date published here after the run |
| Zoom and reflow | Browser zoom to 200% and a 320 px wide viewport without sideways scrolling or lost content | Scheduled: pre-launch audit | Results and date published here after the run |
| Video and animation | Captions or a transcript on every informative video; decorative loops muted with a pause control | Scheduled: pre-launch audit | Results and date published here after the run |
Detail
The details
Our commitment
Everyone should be able to read about our services, compare plans, use the free tools, talk to the assistant and contact us, whether they use a keyboard, a screen reader, voice control, magnification or no pointer at all. We treat a barrier as a bug, and we would rather hear about one than have someone quietly leave.
Standard and scope
Our target is WCAG 2.2 level AA, the W3C recommendation. We say “aims to conform” because a full audit has not yet been completed and published on this page, and we will not claim conformance until it has.
This statement covers the public pages of miniailabs.in: services, solutions, platform, work, pricing, the trust center, contact, the free tools and the chat assistant. Older blog posts written before the current design are in scope but have not all been reviewed yet. The booking page is our own and in scope; third-party services we link to, such as Google Meet for the call itself, follow their own accessibility statements, and the internal admin area is out of scope.
How the site is built for it
- One main heading per page, headings in order, and landmarks with a skip link to the main content.
- A visible focus ring on every link, button and field, which is never removed without a replacement.
- A visible label for every form field, with errors written out in text and tied to the field.
- Touch targets of at least 44 by 44 pixels for buttons, links and controls.
- Colour never carries meaning on its own: status pills pair a dot with a word, and errors pair an icon with a message.
- Headings, text and calls to action are in the page’s HTML and readable before any animation or script runs.
- 3D scenes and animated diagrams are decorative: the same information is written next to them, and a reduce-motion setting replaces them with a still image.
- Animation loops pause when off screen, and every loop that runs longer than five seconds has a pause button.
Known limits
- The call itself runs on Google Meet, which follows Google’s own accessibility support. If the booking calendar or Meet does not work with your assistive technology, email us and we will arrange a time and a way to talk that suits you.
- The 3D scenes are visual only. We describe what they show in text, but a screen-reader user does not get the visual experience itself.
- Some older blog posts may lack descriptive headings or image descriptions. We fix them as each post is reviewed.
- The chat assistant’s fixed replies, such as the handoff message and its qualification questions, are in English only. Answers written by the model follow your language.
- Findings from the first full audit, with their dates, will be added to this list.
Tell us about a barrier
Email hello@miniailabs.in with “Accessibility” in the subject line. Tell us the page, what you were trying to do and, if you are happy to, the browser and assistive technology you use. We reply by email, and if a fix will take time we help you get the information or service another way in the meantime. You can also use the contact form, or the chat’s option to talk to a person.
How this statement is kept current
We update this statement after each audit and whenever a significant part of the site changes. The checklist above shows when each check last ran, and a barrier reported to us is added to the known limits until it is fixed.
Sources
- Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab) · W3C · accessed
FAQ
Frequently asked questions
Does miniailabs.in conform to WCAG 2.2 AA?
We aim to, and the site is designed and built to that standard, but we have not yet completed and published a full audit, so we do not claim conformance. The checklist on this page shows which checks have run and when; the rest are scheduled for the pre-launch audit and will be dated here.
Can I use the whole site with a keyboard?
That is the intent: every menu, form, FAQ and the chat assistant should work with Tab, Shift+Tab, Enter, Space and Escape, with a visible focus ring showing where you are. If you get stuck anywhere, even once, please tell us which page and which control, because a keyboard trap is one of the first things we fix.
Can I stop the animations on the site?
Yes. Turn on the reduce-motion setting in your operating system and the site replaces 3D scenes and loops with still images and removes movement from transitions. Without that setting, looping animations stop when they scroll out of view, and you can pause them with the pause control while they play.
Are the chat widgets and voice flows you build for clients accessible?
When a widget is ours to build, we hold it to the same WCAG 2.2 AA target and test it the same way, and the proposal says so. Channels we connect to, such as WhatsApp or a phone line, follow the provider’s own accessibility features, so we design the conversation itself to be clear, short and easy to repeat.
Is there another way to reach you if the forms do not work for me?
Yes. Email hello@miniailabs.in directly, with as much or as little detail as you like, and we reply by email. If the booking calendar is the problem, say when suits you and we will arrange the call without it.
Questions about this page
Questions about accessibility on this site, or on a system we might build for you, go to hello@miniailabs.in with “Accessibility” in the subject line.
Next step
Have a workflow in mind? Let’s scope it together.
Book a free 30-minute strategy call. Bring one process you want to automate and we will talk through scope, integrations and a sensible first step.
Free 30-minute call · no commitment