Accessibility Statement

This statement applies to the Nemos application for iOS, iPadOS, macOS and watchOS, the Nemos browser extension, and this website at nemosapp.com.

It is published by Taha Baalla, sole proprietor trading as Nemos (Kingdom of Morocco), and is written with reference to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the European Accessibility Act (Directive (EU) 2019/882) and EN 301 549.

Nemos is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means most of the standard is met, and some parts are not yet.

We state this deliberately rather than claiming full conformance. A claim of full conformance that a single screen contradicts is worth less than an honest one, and it is not something we are willing to assert about software this large without an independent audit. Section 5 lists what we currently know is not right.

• VoiceOver. Interactive controls carry accessible names and roles. Controls whose only content is an icon are checked automatically on every release: a build fails if any icon-only control ships without a name, which is the failure that most often leaves a screen-reader user hearing only the word “button”.
• Dynamic Type. Text scales with the size you set in iOS Settings, with per-view ceilings so that large sizes reflow rather than truncate. This is likewise enforced on every release.
• Reduce Motion. When Reduce Motion is on, animated transitions, parallax and looping motion are shortened or replaced with a cross-fade throughout the app.
• Colour contrast. Text and interface colours are checked against WCAG contrast ratios automatically on every release.
• Screen-reader-aware behaviour. Several surfaces change how they present when a screen reader is active — for example, dropping a purely visual affordance in favour of a plainly labelled control.
• Keyboard and pointer. On Mac and iPad, modal screens can be dismissed with a real navigation-bar control rather than a gesture, and interactive elements are reachable with a pointer or keyboard.
• System settings are respected, not re-implemented. Where iOS or macOS already exposes an accessibility preference, Nemos reads it instead of offering a separate in-app copy that could disagree with it.

Accessibility is checked in three ways, and we are specific about the limits of each:

• Automated checks on every release. Icon-only controls without an accessible name, missing Dynamic Type handling, and insufficient text contrast each fail the build. Automated checks catch categories of defect, not every instance of them.
• Accessibility-API testing on macOS. Interface behaviour is verified by driving the app through the platform accessibility tree — that is, through the same interface a screen reader uses — rather than by comparing screenshots.
• Manual VoiceOver passes on the main capture, library, search and settings flows.

We have not commissioned an independent third-party accessibility audit. When we do, we will publish its date and scope here.

The following are known to fall short. We list them because an accessibility statement that claims no problems is not credible:

• Accessible names are English-first. Some accessibility labels added most recently fall back to English in other languages while translations are completed, even though the visible interface is fully translated.
• Generated visual content. Images you create with Genmoji or Image Playground, and images you save from elsewhere, do not have automatic alternative text. You can add your own description in an item’s notes.
• Handwritten annotation. Drawing on a screenshot with PencilKit is inherently a fine-motor, sighted task and has no equivalent non-visual path.
• Knowledge-graph view. The graph is a visual representation. Its underlying items are all reachable through ordinary lists and search, but the graph itself is not usable without sight.
• Third-party and platform surfaces. Widgets, Live Activities, the App Store purchase sheet and Sign in with Apple are rendered by Apple. Their accessibility is Apple’s, and we cannot change it.

If any part of Nemos blocks you, tell us and we will treat it as a defect, not a suggestion.

• Email [email protected] with “Accessibility” in the subject line.
• Please say which device, which assistive technology, and which screen — it makes the difference between a fix and a guess.

We aim to acknowledge accessibility reports within 5 business days and to tell you either when a fix will ship or why it will not. If a fix will take time, we will describe a way to achieve the same thing in the meantime where one exists.

If you are in the European Union and you are not satisfied with our response, you may raise the matter with the market-surveillance or enforcement authority responsible for the European Accessibility Act in your country. If you are elsewhere, your national equality or consumer-protection body may be able to help. We would rather you came to us first, but that route exists and we will not obstruct it.

We will update this statement when the app changes materially, when a limitation above is fixed, or when a new one is found. The “Last updated” date at the top of this page always reflects the most recent revision.