Reso9+ Accessibility Statement
Last updated: June 11, 2026
Product-specific accessibility statement imported from the Reso9+ app project.
Overview
This Accessibility Statement explains how Reso9+ approaches accessibility for the Reso9+ mobile application on iOS and Android (the "App"), including U.S. accessibility readiness and EU accessibility readiness.
Reso9+ is operated by Harmo|Ny/(i)-ght Labs (also referred to in project materials as Harmonight Labs), Sweden ("Reso9+", "we", "us", or "our"). If the public developer identity changes, this Statement will be updated to match the active legal entity.
Accessibility contact: harmonight.labs@gmail.com
This Statement lists U.S. accessibility readiness before EU/EEA accessibility readiness for presentation order only. Both regions are treated as equally important accessibility readiness tracks.
Accessibility Goal
Reso9+ is designed to be usable by as many people as reasonably possible, including people who use screen readers, larger text, reduced motion settings, alternate input methods, high contrast settings, or other accessibility tools.
The App is a local-first utility and creative instrument with hardware-output features such as bright light, flashing light, sound, haptics, microphone input, motion input, and visual analysis. Some features are inherently visual, auditory, motion-based, or hardware-dependent, but the App should still provide clear controls, warnings, labels, and alternatives wherever practical.
Our working accessibility target for release-candidate work is WCAG 2.2 Level AA where it can reasonably map to a Flutter mobile app, with U.S./ADA and EU/EEA accessibility review where applicable. WCAG is a web standard, not a complete mobile-app guarantee, but W3C guidance treats WCAG as relevant to mobile and native app accessibility work.
U.S. Accessibility Readiness
For U.S. accessibility readiness, Reso9+ tracks the Americans with Disabilities Act (ADA) and related web/mobile accessibility guidance where applicable.
The App does not currently claim full ADA conformance. The current working approach is to use WCAG 2.2 Level AA as the app's practical technical baseline, while recognizing that the ADA analysis can depend on the final business model, distribution model, public-facing services, support process, and any future web or hosted services.
The U.S. accessibility goal is to provide meaningful access where reasonably possible, keep legal/support information reachable, provide an accessibility contact path, and avoid blocking users behind inaccessible authentication, gestures, documents, or support workflows.
EU Accessibility Readiness
For EU/EEA accessibility readiness, Reso9+ tracks:
- Directive (EU) 2019/882, commonly called the European Accessibility Act (EAA), where it applies to the App, store distribution, services, or commercial model;
- EN 301 549 as the practical European ICT accessibility reference where applicable;
- WCAG 2.2 Level AA as the current release-candidate technical working baseline for app UI, legal content, support content, and public legal/accessibility webpages; and
- national implementation rules in EU/EEA countries where the App is made available.
The EAA can apply to certain products and services placed on the EU market, including some services provided through websites or mobile device-based services, including mobile applications. Exact applicability can depend on the final release model, app store availability, commercial terms, user flow, company size, service category, exemptions, and national implementation rules.
Reso9+ does not currently claim full EAA or EN 301 549 conformity. Before public launch in the EU/EEA, the App should receive an accessibility pass against the release binary, the store listing, public legal/accessibility webpages, and any hosted report/support flow.
Current Accessibility Practices
Reso9+ is built to support:
- visible text labels for primary controls;
- icon tooltips where icon meaning may not be obvious;
- scrollable legal and report text areas instead of clipped fixed text;
- buttons or visible controls for important actions instead of gesture-only access;
- persistent warnings for strobe, flashing light, emergency-use limits, hearing-check limits, and health-adjacent features;
- user-controlled brightness, color, intensity, tempo, sound, haptic, and routing settings where supported;
- local-first operation without requiring an account, login, CAPTCHA, or inaccessible authentication challenge;
- no user-facing report authentication requirement;
- report messages with a 2000-character limit and a visible text box;
- local delete/reset confirmations for destructive actions where appropriate; and
- compact layouts tested on small mobile viewports.
Gestures And Alternative Controls
Reso9+ includes gestures such as swipes, taps, double taps, holds, drawer gestures, scene navigation gestures, and motion-aware Candle behavior.
Gestures should be supplemental where practical. Critical functions should remain available through visible controls, menu items, sliders, switches, buttons, or system controls. If a future feature depends on a complex gesture, motion actuation, drag action, or device shake, the feature should also provide a non-motion or non-complex alternative unless the motion itself is essential to that feature.
Light, Flash, Motion, And Sound Safety
Reso9+ includes scenes that can produce bright light, flashes, screen pulses, torch output, haptics, rhythm, tones, and other sensory output.
The App uses warnings and user controls to reduce risk, but users remain responsible for using safe settings, suitable devices, and appropriate environments.
Do not use flashing, strobe, bright light, loud sound, haptic, motion, or hearing-check features if they may be unsafe for you or people nearby. Stop immediately if you experience discomfort, pain, dizziness, eye strain, ringing, migraine symptoms, seizure warning signs, overheating, distraction, or any unsafe condition.
Known Limits
No accessibility statement can guarantee that every feature will work for every user, device, assistive technology, operating system version, or impairment.
Current practical limits include:
- some creative visual scenes are primarily visual by nature;
- some audio scenes require hearing or suitable audio equipment for their main output;
- some microphone features depend on device hardware and environment noise;
- torch, haptic, and motion features depend on platform and hardware support;
- generated share cards may need additional text context when shared outside the App;
- app store, payment, review, operating-system permission, email, Photos, and support-provider flows are partly controlled by third parties; and
- full conformance claims require manual assistive-technology testing on release devices.
- U.S./ADA and EU/EAA/EN 301 549 applicability can depend on final release facts, business status, store distribution, public web flows, backend services, and country-specific rules.
Reporting Accessibility Problems
If you have trouble accessing Reso9+, contact:
harmonight.labs@gmail.com
Please include, if you can:
- the App version;
- your device type;
- your operating system and version;
- the scene or control where the issue happened;
- the accessibility tool or setting you were using, if relevant;
- what you expected to happen; and
- what actually happened.
Do not include sensitive personal, medical, financial, password, token, account, location, or private information unless it is necessary for the request.
We may ask for more information if needed to understand or reproduce the issue. We will use accessibility reports only to respond, investigate, improve accessibility, comply with law, and protect the App and users.
Alternate Access And Support
If an accessibility barrier prevents you from using an App feature or reviewing a legal document, contact harmonight.labs@gmail.com and request help or an alternate format.
Where reasonably possible, we will try to provide information or support in a more accessible format, such as plain text, email explanation, or another reasonable method.
Ongoing Work
Accessibility is part of the RC workflow for Reso9+.
Future app changes should be checked for:
- U.S./ADA and EU/EAA/EN 301 549 implications where relevant;
- screen reader names, roles, values, and state changes;
- clear labels and instructions for controls and forms;
- non-color-only meaning;
- sufficient text and non-text contrast;
- usable target sizes and spacing;
- support for platform text scaling where practical;
- visible alternatives to complex gestures and motion actuation;
- ability to pause, stop, avoid, or control motion, flashing, sound, haptics, and timing;
- focus order and keyboard/assistive navigation where supported by the platform;
- no inaccessible authentication or account requirement; and
- no blocking modal flow that cannot be understood or dismissed with assistive technology.
Changes To This Statement
We may update this Statement as the App, accessibility work, legal requirements, or support process changes.
When changes are material, we will update the "Last updated" date and, where appropriate, include the updated Statement in the App's legal review flow.
Contact
For accessibility questions, requests, or complaints, contact:
Harmo|Ny/(i)-ght Labs / Reso9+
Sweden
Email: harmonight.labs@gmail.com