Designed for more people.

DAOasis is committed to improving accessibility across its website and digital experiences, and to treating it as part of designing something well rather than as a compliance task bolted on at the end.

We are working toward the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA as our reference standard, and we are treating it as a design target rather than a badge.

Specific things, present today across the website.

The DAOasis marketing pages use scroll-driven animation, three-dimensional scenes and camera movement. For people with vestibular disorders, migraine or motion sensitivity, that kind of movement is not a stylistic preference — it can cause genuine nausea and disorientation.

Two things follow from that.

Reduced motion is respected

If your operating system is set to reduce motion, DAOasis honours it. Animations are shortened or removed, masked text appears without movement, parallax is switched off, and the paced scrolling used on the marketing pages is bypassed so that scrolling maps directly to your input. You can set this in your system accessibility settings — Reduce motion on macOS and iOS, Show animations on Windows, Remove animations on Android — and every page on this site will respect it without you telling us.

The trust pages have no scroll choreography at all

These seven pages — Privacy, Health Data, Terms, Cookies, Token Disclaimer, Accessibility and Contact — contain no pinned sections, no scroll-scrubbed animation and no three-dimensional scenes. Scrolling is ordinary browser scrolling. The only motion is a brief fade as sections come into view.

That is a deliberate decision. If you need to read a policy, you should not have to negotiate a cinematic experience to do it.

The useful half of an accessibility statement. These are known gaps.

• No formal audit has been carried out. Accessibility has been designed and checked by the team, not verified independently. Status: Independent accessibility audit to be commissioned.
• No testing with assistive technology users. Structural and keyboard testing is not the same as watching someone who relies on a screen reader every day try to use the site. That testing has not happened yet, and it is the gap we consider most significant.
• Screen reader compatibility is designed for, not certified. The site uses semantic HTML and accessible names, which is the foundation — but it has not been verified across the range of screen reader and browser combinations people actually use.
• The marketing pages' animated scenes are inherently visual. Where a scene carries meaning, the same information appears in the surrounding text — but the experience of those pages is not equivalent for everyone, and pretending otherwise would be dishonest.
• Some visual sequences are decorative rather than described. They are marked so assistive technology skips them, which avoids noise but does not convey what a sighted reader sees.
• No accessibility contact address is published yet. See section 06.

This list will get shorter. It is published in this state because a specific gap someone can hold us to is worth more than a general commitment nobody can check.

In development The DAOasis Companion App is being built and is not released.

The intention is for it to support the platform accessibility features people already rely on — the operating system's screen reader, dynamic text sizing, increased contrast, reduced motion and voice control — rather than to build a separate and inevitably worse set of its own.

That is an intention rather than a verified claim, and this page will be updated with the actual position when the app is released, including what does not work yet.

One structural point worth stating now: because DAOasis recognises participation, accessible participation matters more than it would in an app that only displays information. A quest system that can only be completed by people who move in a particular way would not be a wellness product for everyone. How participation is recognised for people with different physical capabilities is Inclusive participation design to be confirmed, and it is a product question, not only an interface one.

If any part of DAOasis is difficult or impossible for you to use, we want to know. A specific report is more useful than a general one — but send it however is easiest for you, and do not spend effort formatting it.

If you can, tell us what you were trying to do, which page or screen you were on, what happened, and what you were using — browser, device, and any assistive technology. Any of those helps; all of them is a luxury.

We aim to acknowledge accessibility reports promptly and to tell you what we intend to do about them, including when the answer is that it will take a while. A target response time is Response time commitment to be confirmed, and we would rather set one we can keep than publish one we cannot.

Parts of the DAOasis experience depend on services we do not build — app stores, health platforms, wallet providers and, in future, payment providers. Their accessibility is theirs, and we cannot fix it directly.

Where a third-party dependency creates a barrier, we will say so rather than leave you wondering whether the problem is ours, and we will raise it with the provider and look for an alternative route where one exists.

The DAOasis website itself is built with no third-party interface components at all — no embedded widgets, no chat bubbles, no consent banners, no social embeds. That is partly a performance and privacy decision, and partly an accessibility one: embedded third-party widgets are among the most reliable sources of keyboard traps and unlabelled controls on the web, and the simplest way to avoid them is not to have any.