Accessibility Statement

Wroud Foundation LLC aims to make the pixly dashboard and marketing site usable for the widest possible audience, including people who rely on assistive technology. This statement explains the standard we target, how to give us feedback if you encounter a barrier, and how to find the most recent version of this document.

§1. Our Commitment

We target the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as the standard for the pixly dashboard and marketing site. We design and build with that standard in mind, and we treat accessibility regressions and accessibility-blocking bugs as priority issues, not nice-to-haves.

This is a statement of intent and ongoing effort. It is not a certification of full conformance: parts of the Service may not yet meet every WCAG 2.1 AA success criterion, and new code occasionally introduces issues we have not yet caught. The Feedback section below is the canonical channel for telling us when that has happened.

§2. Scope of this Statement

This statement covers:

• the pixly marketing site (the landing page and the legal-document pages), and
• the pixly signed-in dashboard, where you manage Servers, Wallet, and Account settings.

It does not cover the in-game experience of Minecraft itself, mods or modpacks you choose to install on a Server, or third-party services we link to (such as Google sign-in or the underlying payment processor). Those experiences are controlled by the relevant third parties and are governed by their own accessibility statements, where they publish one.

§3. Feedback & Reporting Barriers

If you encounter an accessibility barrier on the pixly dashboard or marketing site - for example, a control that is unreachable by keyboard, content that is unreadable with a screen reader, or insufficient contrast - please tell us. Email support@pixly.gg with:

• the page or feature where you encountered the barrier (a URL or a brief description is enough);
• a description of what went wrong and, if you can, the assistive technology, browser, and operating system you were using;
• any suggestions you have for a fix.

We aim to acknowledge accessibility reports within five (5) business days and to respond substantively within ten (10) business days. We treat reports of accessibility barriers as priority bugs and prioritize them alongside our regular bug-fix workflow.

§4. Last Reviewed

This statement was last reviewed on 2026-05-16. We review it whenever we materially change the dashboard or marketing site, and at minimum once per year. When we do, we update the date above and add an entry to the version history below.