Accessibility

1. Our commitment

Our goal is conformance with WCAG 2.1 AA. We do not claim to be fully conformant yet; this is a process and we try to make progress in every release. When you report the barriers you encounter, we order our priorities accordingly.

2. Accessibility features available today

Reduce motion

Settings → Media and data → 'Reduce motion'. Simplifies transition and parallax animations. It also follows the 'Reduce Motion' setting in your operating system.

Text size

In the mobile app, Settings → Appearance → Text size. Your system font size setting is respected as well.

Dark theme

Dark and AMOLED themes for light-sensitive users. It can follow the system theme automatically.

Screen reader labels

Buttons and interactive elements are labelled for VoiceOver (iOS) and TalkBack (Android).

Keyboard navigation

Tab navigation and visible focus rings are supported in the web interface.

Meaningful heading structure

A proper h1→h2→h3 hierarchy and contents links on the corporate and legal pages.

Turning autoplay off

You can stop videos playing by themselves entirely (for vestibular discomfort and distraction).

Data saver

Lowers media quality and turns preloading off for low bandwidth and metered connections.

3. For users who are blind or have low vision

• Interactive elements are labelled for screen readers; icon-only buttons carry a descriptive label.
• The contrast between text and background targets a ratio of at least 4.5:1 in body text.
• Colour is not used as the sole carrier of meaning; status information is also given in text or with an icon.
• The interface does not overflow when the system font size is increased.

4. Motion sensitivity and animations

Animations can be a problem for users with a vestibular disorder. We offer two layers of protection:

• In-app setting: “Reduce motion” — it is tied to your account and applies across all of your devices.
• System setting: we also follow the “Reduce Motion” preference on iOS/Android/macOS/Windows; if either one is on, animations are simplified.
• Autoplay: you can turn off videos starting by themselves entirely.

5. For users who are deaf or hard of hearing

• Videos start muted by default; sound is turned on only at the user's request.
• The duration of a voice message is shown visually next to it.
• Notifications are also delivered visually and by vibration.

Planned: we are working on automatic captions for videos and transcription for voice messages. This feature is not available yet.

6. Support for motor skills

• Touch targets are designed to be at least 44×44 points.
• Critical actions (deleting, blocking) have a confirmation step; this prevents accidental triggering.
• All main functions are reachable with the keyboard in the web interface.
• There is no timed, mandatory interaction; no time limit is placed on reading content.

7. Known limitations

To be honest, we are not yet good enough in the following areas:

• No automatic captions: automatic captions are not yet generated for videos.
• Limited map accessibility: the map view is not fully usable with screen readers; location information should also be offered as a text alternative.
• Camera effects: the AR filter interface relies largely on visual feedback.
• Some third-party content: alternative text may not always be available for GIFs and embedded media.

We keep these items on our roadmap. If you write and tell us which of them is the most critical for you, we take that into account when setting priorities.

8. Feedback and support

If you have run into an accessibility barrier, please write to us: accessibility@aurcam.com (or support@aurcam.com).

Where possible, please include: the device and assistive technology you are using (VoiceOver, TalkBack, NVDA and the like), the screen on which you had the problem and what you expected to happen. We treat reports of this kind as a priority and we tell you the outcome.