Accessibility
Accessibility statement
What we meet, what we do not meet yet, and how to reach us when something gets in your way — written plainly.
- Home
- Accessibility
We want inmola.com to be usable by everyone. We target WCAG 2.2 Level AA. This page is not marketing copy; it is an honest account of where we actually stand — what we do not meet is written down alongside what we do.
Last updated: 5 October 2026
What we have done so far
Page language is declared correctly in all eight languages
Screen readers choose pronunciation rules from the page language attribute. Every language used to be declared as English, so Turkish content was read with English phonetics. That is fixed, and Arabic now also receives the correct writing direction.
Skip to content link
Keyboard users can bypass the navigation — product mega-menu included — with a single key and land on the content. The content is also marked as the main landmark, so screen readers can jump straight to it.
Visible keyboard focus
Every focused element gets a thick ring. The ring appears only when navigating by keyboard or assistive technology and stays hidden for mouse use.
Motion preference respected
If you have asked your operating system to reduce motion, every scroll-triggered animation stops. You can also switch the same preference on manually from the panel.
Heading structure and image descriptions
Heading levels were reordered so none are skipped. Every image that carries information has a text description; decorative images are hidden from screen readers.
Accessibility preferences panel
The icon in the bottom left opens settings for text size, higher contrast, reduced motion, link highlighting and readable spacing. Your choices are stored on your device.
Gaps we know about
There is no point hiding these; anyone who hits one will notice anyway. Writing them down sets the right expectation and keeps us honest about following through.
- The first HTML served still carries the default language. It is corrected before the page paints, so screen readers see the right language, but we would rather fix it in the raw markup.
- Some section headings on the homepage sit one level lower than they semantically should. This is not a standard violation, but we want the structure to read more cleanly.
- Colour contrast has not been audited component by component across the whole site. The higher-contrast option in the preferences panel bridges that in the meantime.
- Third-party components such as the chat tool, the checkout step and videos embedded in articles have not been audited separately.
- We have not been through an independent accessibility audit. The assessment on this page is our own.
Frequently asked
Why do you not use an accessibility overlay?
One-click accessibility widgets bolted on top of a site are largely rejected by disabled user communities and accessibility practitioners, because they do not fix the underlying code and in some cases conflict with the visitor’s own screen reader. In 2025 the maker of one such product was penalised by the US Federal Trade Commission over the claim that its AI made websites compliant. We fix the code instead. The settings in our panel are display preferences you choose for yourself; they do not interfere with your screen reader.
Which standard do you target?
We target WCAG 2.2 Level AA. This page lists both what we believe we meet and the gaps we are knowingly leaving open, because a statement that hides its gaps is useless to the first person who runs into one.
What should I do if I hit a problem?
Write to us. Telling us the page, the browser and the assistive technology you were using makes it much faster to resolve. We treat accessibility reports as a priority and update this page as fixes land.
Report a problem
If there is something on the site you cannot reach, write to us. Naming the page, your browser and any assistive technology you use speeds up the fix.