What we build for
lans.cloud aims at WCAG 2.1 AA as the working standard. Concretely, across the tools:
- Keyboard operability: interactive controls are real buttons and inputs, reachable and operable by keyboard; the wheel spins on Space, and Escape exits fullscreen presentation modes.
- Labels: icon-only buttons carry aria-labels (this is enforced by a lint rule in the codebase, not just good intentions), form fields have visible labels, and toggle chips expose their pressed state to assistive tech.
- Contrast and themes: light and dark themes both target readable contrast; reference tables and results use text, not color alone, to carry meaning.
- Touch targets: primary controls keep to a minimum ~44px touch size for tablets and phones.
- Motion: spin animations respect prefers-reduced-motion where configured, shortening or simplifying movement.
- Screen reader announcements: tools with random outcomes (wheels, pickers) announce results via aria-live regions.
Known limitations
Honesty beats a compliance badge: some visual tools are inherently graphical (the granny square color preview, the Minecraft circle chart), and while their data is also presented as text where possible, the visual-first experiences are not yet fully equivalent for screen reader users. Charts rendered for printing prioritize print clarity. We have not undergone a third-party WCAG audit.
Report an issue — it will actually get fixed
The site is maintained by one developer who ships accessibility fixes with the same priority as features — several current behaviors (labels, announcements) came from user reports. Use the feedback button at the bottom of any tool page, describe what blocked you (and your assistive tech if relevant), and leave an email if you'd like to hear back. Reports are typically addressed within days.