Accessibility Statement

1. Our commitment

Cleanor Research Labs L.L.C-FZ is committed to making our apps and website usable by as many people as possible, including people with visual, hearing, motor, cognitive, or situational impairments. Accessibility is treated as a product quality attribute alongside performance, privacy, and reliability — not as a one-time checklist.

We design and develop with accessibility in mind from the earliest sketches through release. When we find a gap, we fix it in the next reasonable update rather than waiting for a large overhaul.

2. Standards we follow

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA for our website and, where applicable, for app interfaces.

On iOS we follow the Apple Human Interface Guidelines for Accessibility and build against the iOS Accessibility APIs. On Android we follow the Material Design accessibility guidance and build against Android Accessibility APIs.

These references guide how we handle color contrast, focus order, target sizes, labels, and alternatives for non-text content.

3. Accessibility on iOS

Our iOS apps are built to cooperate with iOS system accessibility features so people can use whichever combination fits them best.

Supported iOS features include VoiceOver screen reader labels on primary actions, Dynamic Type for scalable text, Bold Text, Reduce Motion for users sensitive to animation, Reduce Transparency, Increase Contrast, Smart Invert, Voice Control, Switch Control, and keyboard navigation when a hardware keyboard is attached.

Interactive controls follow the recommended minimum tap target size and expose accessibility labels, traits, and hints so assistive technologies can describe them accurately.

4. Accessibility on Android

Our Android apps are built to work with TalkBack, Switch Access, and Voice Access, and respect system settings like display size, font scale, high-contrast text, and reduced animations.

Content descriptions are provided for non-text UI elements, focus order follows a meaningful reading sequence, and color is never used as the only way to convey information.

5. Accessibility on the web

cleanor.app is built with semantic HTML, meaningful headings, and ARIA attributes only where native semantics are not enough.

The site supports full keyboard navigation, visible focus indicators, scalable text, and responsive layouts that reflow on zoom up to 200% without loss of content or functionality.

Media embedded in editorial content is expected to include text alternatives (alt text, captions, or transcripts) where content is informative rather than decorative.

6. Known limitations

No product of this scope is perfectly accessible at all times. Areas we actively monitor include complex interactive tools, third-party embeds, user-generated content, and newly shipped features that may not yet have been through a full accessibility review.

If you encounter a barrier that blocks you from using a feature, please tell us — reports from real users are the most valuable input we receive.

7. Ongoing work

Accessibility reviews are part of our release process. We run automated checks on the website, test core flows with screen readers on iOS and Android, and verify scalable text and color contrast on key surfaces before shipping.

Findings are tracked alongside other product work so fixes land in normal release cycles rather than sitting in a separate backlog.

8. Feedback and contact

If you have trouble using any part of our apps or website, or want to suggest an accessibility improvement, contact us at support@cleanor.app. Please include the device, operating system version, assistive technology in use, and a short description of what you were trying to do.

We aim to acknowledge accessibility reports within five business days and will share a timeline for a fix when one is possible.