Accessibility

Accessibility at MessyDev

Last updated: September 2026

Learning AI shouldn't depend on how you use a screen. Here's what we build in, what still needs work, and how to reach a human fast.

Our commitment

MessyDev is designed so that everyone can learn AI with Messy — including people who use screen readers, keyboards only, magnification, or reduced-motion settings.
We aim to meet WCAG 2.1 Level AA across the site and the installed app.

Keyboard navigation: every lesson, exercise, button, and menu is reachable and operable without a mouse, with a visible focus outline and a skip-to-content link at the top of every page.
Screen reader support: pages use semantic landmarks (one main region per page), labelled headings, and accessible names on icon-only buttons like the menu close, password reveal, and language picker.
Contrast: text and interface colors use a tested palette that meets WCAG AA contrast against both light and dark backgrounds.
Motion control: celebrations, the animated workshop scenes, and Messy's dock animations respect your device's 'reduce motion' setting and tone down automatically.
Voice and hearing: Messy's spoken voice is always paired with on-screen text, and captions-friendly audio is used in our videos. Voice input is optional — everything can be typed.
Text sizing: layouts reflow and scale with your browser or device text size up to 200% without losing content.
Forms: sign-in, sign-up, contact, and exercise inputs use real labels, describe their errors in text, and never rely on color alone.

Some exercise playgrounds include interactive code and prompt exercises that work best on a wider screen; on small phones we present a simplified tap-based version, but a few advanced Agent Lab simulations are still easier on tablet or desktop.
Third-party tools we teach you to connect (GitHub, Vercel, Stripe, and others) have their own accessibility, which we can't control.

If you hit a barrier anywhere in MessyDev, tell us and we'll fix it. Use the contact form on our Contact page and choose 'Something is broken', or describe the page and what you were trying to do.
We aim to respond within 2 business days and to ship accessibility fixes as priority bugs.

In the EU, under the Digital Services Act you can also report illegal content or appeal a moderation decision through the same contact form — those topics are available directly in the form.
This statement is reviewed with each major release.

Found a barrier we didn't catch? Contact us and choose "Something is broken" — accessibility fixes are priority bugs for us.