POWER FOR EVERYONE.
Our WCAG 2.1 AA commitment: 44px targets, screen reader labels, keyboard navigation, reduced motion support, known gaps, and how to report issues.
KARL: “A movement that isn't usable by disabled comrades isn't a movement. It's a club.”
Our commitment: This site aims to meet WCAG 2.1 Level AA. Power belongs to everyone — including everyone using a screen reader, a keyboard, voice control, or a five-year-old phone on a bad connection. If something here doesn’t work for you, that’s our bug, and we want to hear about it.
WHAT WE DO
- Touch targets: interactive elements are at least 44px — big enough for thumbs, tremors, and styluses.
- Screen readers: semantic HTML, labeled controls, and ARIA attributes on navigation (menu, accordions, bottom nav) so assistive tech can parse the page.
- Keyboard navigation: every action reachable without a mouse — menus open and close on keyboard, accordions expand, focus stays visible.
- Reduced motion: we respect
prefers-reduced-motion— animations and transitions stand down when your system asks them to. - Contrast: body text and key actions are designed against WCAG AA contrast ratios on the dark theme. Red accents are never the only carrier of meaning.
- Mobile-first: the whole site is built phone-first — large text, single-column layouts, no hover-dependent interactions.
- Zoom: layouts reflow instead of breaking at 200% zoom and beyond.
KNOWN GAPS
We’re honest about where we fall short. Current known issues:
- Some older embedded widgets predate our accessibility pass and may have unlabeled controls.
- Third-party embeds (payment checkout, external media) follow their own accessibility standards, not ours.
- User-generated content — memes and images uploaded by the community — doesn’t always ship with alt text. We’re building prompts to encourage it.
We fix reported issues in priority order: blockers first, annoyances next, polish last.
REPORT AN ISSUE
Hit a barrier? Tell us exactly what happened:
- The page and what you were trying to do
- Your device, browser, and assistive tech (e.g., “VoiceOver on iPhone”)
- What you expected vs. what happened
Email mtcstw@gmail.com with the subject “Accessibility issue”. A human reads it, and accessibility reports jump the queue.
Last updated: October 11, 2026.