Accessibility Statement

This document is the text published at peonix.app/accessibility — it is rendered from this file, so what is reviewed here is exactly what the site serves. Questions: support@peonix.app

Last updated: October 5, 2026

Greenwind LLC is committed to making the Peonix marketing site — peonix.app's home, features, pricing and contact pages, in English, Spanish and Russian — usable by everyone, including people who use a keyboard instead of a mouse, a screen reader, a magnifier, or a browser set to reduce motion or increase contrast.

Conformance target

We target WCAG 2.1, Level AA — the standard named in the U.S. Department of Justice's own guidance on web accessibility under Title III of the ADA, and the one referenced by nearly every published court decision on the subject. This statement describes a good-faith effort measured against that standard; it is not a certification, and no self-assessment is.

Scope

This statement covers the four public marketing pages at peonix.app (home, features, pricing, contact), the sign-up page and the legal pages (privacy, terms, data sources and this statement) — it does not yet cover the signed-in Peonix application (the order board, calendar, storefront and the rest of the product a shop uses after creating an account). That is a separate, larger surface with its own review under way; this page will be updated to reflect it, or split into two, once that work is done.

A shop's public storefront comes next. The online store a shop's customers order from is the part of Peonix the public uses, so it is the first surface of that review. Until it is covered here: if a barrier stops you ordering from a shop that uses Peonix, write to support@peonix.app — we will help you place the order as soon as we can, and we treat the barrier as a defect to fix.

What we have done

• Structure a screen reader can navigate. One <h1> per page, headings that never skip a level, landmark regions (header, nav, main, footer), and a "skip to content" link that is the first thing a keyboard reaches on every page.
• Colour is never the only signal. The page you are on is marked with an underline and a coloured dot, not colour alone; every piece of body text and every button label was measured against the background actually painted behind it and reaches at least a 4.5:1 contrast ratio (3:1 for large text), the WCAG AA minimum.
• A visible focus ring on every control, reaching at least 3:1 contrast against what it lands on — not just present, but legible.
• Full keyboard operation. The menu, the language switcher, the image viewer and every link and button work from a keyboard alone, with no mouse-only interaction anywhere on the page.
• Works with motion turned off. A browser or OS set to "reduce motion" removes every decorative animation; nothing on the page depends on movement to be understood.
• Reachable pointer targets. Every button and link outside a line of running text is at least 24×24 CSS pixels, the WCAG 2.2 minimum, so a target is easy to hit on a phone.
• Works at 320px and at 400% zoom. The layout reflows to a single column with nothing cut off or requiring sideways scrolling, on every page in every supported language.
• Degrades honestly. If a stylesheet or a script fails to load, the page is still a plain, readable, correctly-sized document — nothing renders oversized or unusably broken.
• Meaningful alt text on every product screenshot, describing what the screen shows rather than restating its caption.
• No accessibility overlay. We deliberately do not use a third-party "accessibility widget." The evidence is that these widgets do not reduce legal exposure, are opposed by disability advocacy organizations and blind users themselves because they interfere with a visitor's own assistive technology, and in January 2025 the U.S. Federal Trade Commission fined the most widely used one (accessiBe) for falsely claiming its product made sites WCAG-compliant. We build the access in rather than paying to paper over it.

What we have not done yet

• No automated axe-core run. The project does not include axe-core, and we have not added a new tool for this statement. The checks behind it are our own static markup and contrast tests (run on every change) and manual measurement; the sign-up page and the legal pages were added to this statement's scope on October 5, 2026 on the basis of those same checks, not a fresh full audit. Known limits: the legal pages are long, English-only documents; the sign-up form and its bot check have not been tested with every assistive technology.
• We have not commissioned an independent third-party audit or a formal VPAT (Voluntary Product Accessibility Template). Our review so far is our own, using both automated checks and manual measurement of contrast, keyboard operation and reflow.
• We have not tested with every screen reader and browser combination in wide use — our primary testing floor is a current Chromium-based browser and VoiceOver-style assistive technology conventions.

Reporting a barrier

If any part of peonix.app is difficult to use with a keyboard, a screen reader, or any other assistive technology, tell us: support@peonix.app. A person reads it as soon as we can — there is no ticket queue and no automated triage. Tell us the page, what you were trying to do, and what happened; we will fix genuine barriers and reply to say so.