Accessibility Statement
Our commitment to making Hone Studio accessible to all users, including people with disabilities.
Our Commitment
Hone Labs is committed to making Hone Studio accessible to all users, including people with disabilities. We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.
We believe accessibility is an ongoing practice, not a one-time checkbox. This statement describes our current accessibility features, known limitations, and remediation plans.
Current Accessibility Features
Navigation and Structure
- Skip to main content link — keyboard users can bypass navigation and jump directly to page content
- Semantic HTML landmarks — proper use of header, main, nav, and aside for screen reader navigation
- ARIA treeview — the knowledge base folder tree implements the complete WAI-ARIA treeview pattern with full arrow key navigation
- Active page indicator —
aria-current="page"on navigation links so screen readers announce the current location
Keyboard Accessibility
- Modal focus trapping — focus is trapped within open dialogs and returned to the triggering element on close
- Escape to close — all modals, drawers, and overlays can be dismissed with the Escape key
- Focus-visible indicators — visible focus rings on all interactive elements when navigating by keyboard
- Minimum 44x44px touch targets — interactive elements target a minimum 44x44px touch area per WCAG 2.5.5
Screen Reader Support
- Icon buttons labeled — all icon-only buttons have descriptive aria-label attributes
- Loading states announced — loading spinners and typing indicators use aria-live regions to announce state changes
- Toast notifications — success/info toasts use aria-live="polite", error/warning toasts use role="alert" for immediate announcement
- Decorative icons hidden — SVG icons and decorative elements are marked aria-hidden="true" to reduce screen reader noise
- Visually hidden labels — form inputs without visible labels have screen-reader-only label text
Motion and Forms
- prefers-reduced-motion support — all animations and transitions respect the operating system setting
- No auto-playing media — the platform contains no auto-playing video or audio
- Associated form labels — key forms have programmatically associated labels via htmlFor/id pairing
- Search result announcements — live regions announce search result counts as the user types
Known Limitations
We are transparent about areas where our accessibility falls short.
Level A Issues
| Issue | Description | Status |
|---|---|---|
| Missing page headings | Several module pages lack a visible <h1> | Remediated — March 2026 |
| Some form labels unassociated | Date range filters, some modals not linked via htmlFor | Remediated — March 2026 |
| Error messages not linked | Validation errors not associated via aria-describedby | Remediated — March 2026 |
| Color-only status indicators | Document status dots use color as sole differentiator | Remediated — March 2026 |
| Mobile nav focus management | Mobile drawer does not trap focus when open | Remediated — March 2026 |
Level AA Issues
| Issue | Description | Status |
|---|---|---|
| Low contrast tertiary text | Timestamps and secondary counts below 4.5:1 ratio | Remediated — March 2026 |
| Command palette focus trap | Ctrl+K palette does not trap focus | Remediated — March 2026 |
| Keyboard gaps in document list | Enter does not open document; no keyboard rename | Remediated — March 2026 |
Conformance Status
Current status: Partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that some parts of the content do not fully conform to the accessibility standard. The features listed above demonstrate intentional accessibility work, while the known limitations section documents the gaps we are actively addressing.
Accessibility Conformance Report (ACR): Completed. Our ACR based on VPAT 2.5Rev was completed in March 2026. 46 of 50 WCAG 2.1 Level AA criteria are fully supported with 0 partially supported. ACR available on request — contact accessibility@honelabs.dev.
Testing Approach
| Method | Tool/Technique | Coverage |
|---|---|---|
| Automated testing | axe-core engine in Vitest component tests + Playwright E2E (400+ tests in CI) | All major components and workflows |
| Manual keyboard testing | Tab, Shift+Tab, Enter, Space, Escape, Arrow keys | All major workflows |
| Screen reader testing | NVDA (Windows), VoiceOver (macOS) | Core navigation and key features |
| Color contrast analysis | Manual palette review | Full color palette |
| Reduced motion testing | prefers-reduced-motion: reduce | Global CSS and JS animations |
Remediation Roadmap
| Phase | Focus Area | Target |
|---|---|---|
| Phase 1 | Fix Level A issues: headings, labels, error linking, color indicators | Completed — March 2026 |
| Phase 2 | Fix Level AA issues: contrast, command palette | Completed — March 2026 |
| Phase 3 | Publish ACR (VPAT 2.5Rev), expand axe-core E2E coverage | Completed — March 2026 |
| Phase 4 | Third-party accessibility audit and remediation | Target Q4 2026 |
Dates are targets and may shift based on resource availability.
Feedback and Contact
We welcome feedback on the accessibility of Hone Studio. If you encounter an accessibility barrier or have suggestions for improvement, please contact us.
Email: accessibility@honelabs.dev
Response time: We will acknowledge your report within 2 business days and provide an initial assessment within 5 business days.
If you need information in an alternative format, or require an accommodation to use the Platform, please contact us and we will work with you to find a solution.
Technical Environment
Hone Studio is optimized for:
- Browsers: Chrome, Firefox, Safari, Edge (latest 2 major versions)
- Operating systems: Windows, macOS, ChromeOS
- Screen readers: NVDA (Windows), VoiceOver (macOS)
- Input methods: Mouse, keyboard, touch (responsive design)