Everyone should be able to see the work.
We're building Mojizu to meet WCAG 2.1 Level AA. Accessibility isn't an afterthought — it's part of how a visual community respects its visitors.
Last updated April 17, 2026
Our commitment
We aim to conform to the Web Content Accessibility Guidelines 2.1 at Level AA. Mojizu is a visual community, but visual doesn't mean exclusive — the experience should work for everyone who wants to be part of it.
What we build for
- Keyboard navigation. Every interactive element — voting, rating, market actions, uploads, settings — is reachable and operable from the keyboard.
- Screen reader support. Semantic HTML, meaningful
alttext on every Moji, ARIA labels on role icons and navigation, and live regions for async state. - Color contrast. Body text and UI chrome meet AA contrast ratios on our light theme.
- Scalable text.Zooming to 200% doesn't break layouts or clip content.
- Reduced motion. Decorative animation (swipe peeks, bracket transitions) respects
prefers-reduced-motion. - Touch targets. Mobile targets meet the 44×44 pixel minimum for hands-on-phone use.
Known gaps
We're early. Some areas we're actively improving:
- Complete ARIA labeling on the Super Match bracket at all breakpoints.
- Alternative captions for animated elements used in battle feedback.
- Expanded screen-reader descriptions for Power Stats radar charts.
If you hit a wall, please tell us — it speeds up the fix.
Give us feedback
Email ali@sabet.com with a subject of “Accessibility feedback.” Include the page, the device and assistive tech you're on, and what went wrong. We read every message and prioritize accessibility reports.