Legal
Accessibility statement
How accessible alloymc.dev and its sites are, what we test against (WCAG 2.2 level AA), what isn't there yet, and how to tell us about barriers.
We want everyone to be able to use AlloyMC, including people who use a screen reader, a keyboard instead of a mouse, magnification, or who are sensitive to motion. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
What this covers
alloymc.dev, launcher.alloymc.dev, api.alloymc.dev, legal.alloymc.dev and the emails AlloyMC sends. The Alloy launcher itself is a desktop app and isn't covered yet; see Known gaps.
Status
Partially conformant with WCAG 2.2 level AA: most of the content meets the standard, and the exceptions are listed below. We say "partially" until people who rely on assistive technology have tested the sites with us, not only our own checks.
What we do
- Keyboard. Everything works without a mouse, in a logical order, with a visible focus ring that's never hidden behind other content (WCAG 2.4.7, 2.4.11). A "Skip to content" link comes first on every page.
- Contrast. Text meets at least 4.5:1 against its background, large text and interface parts at least 3:1 (1.4.3, 1.4.11).
- Motion. Animations explain what's happening (a button pressing in, a section arriving). If your system asks for reduced motion, movement is switched off and only colour changes remain. Nothing flashes.
- Structure. Real headings, landmarks, lists and tables, labelled forms, and text alternatives for images that carry meaning. Each page has one main heading and a descriptive title.
- Reflow and zoom. Pages work at 320 pixels wide and at 400% zoom without scrolling sideways, except wide tables, which scroll on their own (1.4.10).
- Targets. Buttons and links are at least 24 by 24 pixels or spaced so they're easy to hit (2.5.8).
- Signing in. No puzzles or CAPTCHAs. Password managers and pasting work everywhere, and "Continue with Google" is there if typing passwords is hard (3.3.8). Forms keep what you typed when something needs fixing (3.3.7), and errors say what to do.
- Help in the same place. Every page ends with the same footer with contact, legal and help links (3.2.6).
- Plain language. We write short sentences and explain technical terms.
- Emails are real text, not images, with a plain-text version alongside.
How we test
- Automated checks with axe-core against the WCAG 2.2 A and AA rules on every page type, at desktop and phone widths.
- Tabbing through every page and control, and checking that each one shows focus and reacts to pointer and keyboard.
- Checking pages with reduced motion turned on, and at 320 pixels wide.
Testing with screen readers (NVDA, VoiceOver) is next, and we'll update this statement with what we find.
Known gaps
- The Alloy launcher (the desktop app) hasn't been audited yet. Keyboard use works in most places; screen reader support is incomplete. This is planned for after Alloy 0.3.
- Videos showing Alloy have no speech. Each has a text description of what it shows, but no audio description.
- Pages run by others that AlloyMC links to or uses, like GitHub (downloads), Google (sign-in) and Microsoft (Minecraft sign-in), are outside our control.
Tell us about barriers
If something on AlloyMC doesn't work for you, write to contact@elchi.dev or open an issue. Say which page and what got in the way. We answer within 5 working days, and if we can't fix it quickly we'll get you the content another way.
If our answer doesn't help and you live in the EU, you can contact the authority responsible for accessibility in your country.
This statement was prepared on 31 October 2026 and is reviewed whenever the sites change significantly.