Accessibility

Being close means being accessible, too.

Duonook is designed to accompany everyday gestures. To do that well, it has to remain understandable, readable, and usable in different ways.

The basics

Choices you shouldn’t even notice.

When they work, they reduce effort and leave room for what you want to do.

Aa

Readable text

Clear hierarchy, checked contrast, comfortable line lengths, and content that can adapt to the screen size.

⌁

Respectful motion

Animations must not be essential, and the website respects the system preference to reduce motion.

⌨

More ways to navigate

Semantic structure, visible focus, comfortable touch targets, and full keyboard navigation on the public website.

◐

More than color alone

States and actions don’t rely on color alone: text, position, and shape help you read them.

◎

Assistive technologies

Labels and reading order are designed for VoiceOver, TalkBack, and the system’s own tools.

↻

Continuous improvement

Accessibility isn’t a box to tick at the end: it’s checked as we work and fixed whenever an obstacle comes up.

The public website

These pages use semantic HTML, a skip-to-content link, well-ordered headings, native controls, and visible focus. The layout adapts from small phones to desktop screens without requiring horizontal zoom.

The website does not depend on JavaScript for reading or navigating content. Informative images have alt text; purely decorative ones are ignored by assistive technologies.

The Duonook app

The app uses each platform’s accessibility components and provides labels, hints, and states for the main controls. Text size, contrast, theme, and motion are checked on the most important screens.

Some tactile experiences, such as opening a gift or the Fortune Cookie, must always offer an understandable action that doesn’t rely only on the gesture or the animation.

Standards and status

Our reference for the web is WCAG 2.2, Level AA. This is a design direction, not a certification claim: the website and the app will continue to be checked as they grow.

No vague promises

When a limitation is known, we prefer to describe it and fix it. Formal conformance will only be declared after a complete, documented audit.

Reporting a barrier

If something isn’t readable, reachable, or understandable, write to support@duonook.com. Tell us your device, system version, assistive technology, and the step involved; you don’t need to share private content.