Our commitment. aHasnap! is built to be usable by every student and educator, including those who rely on assistive technology. We design and ship to WCAG 2.1 Level AA as our minimum target, with the intent to clear WAVE accessibility review on every new public surface before launch.
What we do today
- Color contrast. All body text and interactive elements meet WCAG AA contrast (4.5:1 normal, 3:1 large or UI). Visible focus indicators meet 3:1 against every backdrop.
- Keyboard navigation. Every interactive element is keyboard reachable with a visible focus ring. Skip-to-main-content link is present on every page. Tab order is logical and predictable.
- Semantic HTML. Pages use proper heading hierarchy (single H1, sequential H2/H3 with no skipped levels), landmark elements (header, main, nav, footer), and ARIA labels where structure alone is not enough.
- Screen reader support. Decorative images carry aria-hidden. Meaningful images carry descriptive alt text. Icon-only buttons carry aria-label. Form fields carry visible labels associated by id.
- Mobile accessibility. Tap targets are at least 44 by 44 pixels. Mobile navigation reports its expanded or collapsed state via aria-expanded and updates its accessible name accordingly. Escape key closes the menu and restores focus.
- Reduced motion. All transitions and animations are minimized when the user has prefers-reduced-motion enabled.
- No-JavaScript fallback. Core content and navigation remain usable when JavaScript is unavailable.
What we are still working on
We treat accessibility as ongoing work, not a one-time audit. Areas under active improvement:
- Audio descriptions for in-product motion content
- Expanded screen-reader testing across NVDA, JAWS, and VoiceOver
- Multi-language interface support for non-English-speaking students and families
- High-contrast theme option for students with visual sensitivity
How to report an issue
If you encounter an accessibility barrier anywhere in aHasnap!, please tell us. We treat accessibility reports with the same priority as security reports.
Email [email protected] with:
- The page or screen where the issue occurred
- The assistive technology you were using (if any)
- What you expected to happen, and what happened instead
We will acknowledge your report within two business days and tell you how we are addressing it.
Standards we follow
- WCAG 2.1 Level AA
- WAVE Web Accessibility Evaluation Tool
- Section 508 of the U.S. Rehabilitation Act
Get in touch
For accessibility-specific issues: [email protected]. For general contact: contact us.