Keyboard-only navigation
Every interactive element — every dropzone, every button, every dropdown — is reachable with Tab and operable with Enter or Space. There's a global Cmd/Ctrl+K command palette for power users.
Accessibility
SnapToolz aims to meet WCAG 2.1 Level AA. We're not perfect — here's what works today, what doesn't, and how to flag anything we missed.
Last updated: May 30, 2026
What works today
Visible focus indicators
Whatever element has keyboard focus has a clearly visible 2px ring. We never disable this without replacing it with something equally clear.
Screen-reader-friendly markup
Every page uses semantic HTML (h1/h2 hierarchy, nav, main, footer, lists). Icons that aren't text are marked aria-hidden so they're not announced. Decorative content has aria-hidden, interactive controls have aria-labels.
Reduced-motion support
If your OS reports prefers-reduced-motion: reduce, animations are cut to ~10ms. The site stops moving and stays still.
Standards we follow
- WCAG 2.1 Level AA target — colour contrast, keyboard operability, semantic structure
- ARIA Authoring Practices for the command palette, dialogs, and dropdown menus (built on Radix UI primitives, which encode the patterns)
- HTML Living Standard for landmarks, headings, and form labels
- Section 508 compatibility for the most common patterns — the architecture aligns even though we're not formally certified
Known gaps
Honesty: these are the rough edges we're aware of. Listed publicly rather than buried because that's how accessibility work actually improves.
- Some PDF tools render thumbnails with limited alt text — useful for sighted users, less so for screen readers. We're improving this.
- Drag-and-drop reordering inside the PDF Organize and Merge tools doesn't yet have keyboard equivalents. There's a fallback file-list view planned.
- OCR's progress indicator uses live-region announcements that may be too verbose on some screen-reader configurations.
- On very small viewports (< 360px wide), some category pills wrap awkwardly. The layout still works but isn't visually polished.
Reporting an issue
If you hit something that blocks you, please write directly. The more context you can share — the tool URL, your browser, your assistive tech, and what you expected to happen — the faster we can fix it.
Email hellojaggaro@gmail.comWe aim to respond to accessibility reports within 2 business days and ship fixes within 2 weeks of confirming the issue.