Accessibility Statement

Zone Scribe

Zone Scribe is committed to ensuring digital accessibility for people with disabilities. We work to improve the user experience for everyone and apply relevant accessibility standards.

Scope

This statement applies to the Zone Scribe web application at app.zonescribe.ai, including the iOS and Android mobile apps which present the web application in a webview.

Compliance status

Zone Scribe is conformant with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.

Accessibility features

Zone Scribe is designed to support:

  • Keyboard navigation — Most interactive features can be used with a keyboard, with visible focus indicators.
  • Screen reader support — We aim to use semantic HTML and ARIA where appropriate to provide meaningful announcements.
  • Accessible components — Core UI patterns are built with focus management and keyboard interactions in mind.
  • Form accessibility — We aim for inputs to have associated labels, and for validation feedback to be available to assistive technologies.
  • Colour contrast — We aim for text and interactive controls to meet WCAG AA contrast requirements.

Feedback and contact information

If you encounter accessibility barriers or have suggestions for improvement, please contact us. If possible, include the page or feature you were using, what you expected to happen, and your device/browser details.

Email: support@zonescribe.ai

Preparation and review of this statement

This statement was prepared in December 2025 based on an internal self-assessment.

Accessibility is reviewed at least annually and when major changes are released. In addition, automated accessibility checks run on every change to the application.

Testing methods used

Automated testing on every change:

  • Automated accessibility checks using axe-core (mapped to WCAG 2.2 Levels A and AA)
  • Static analysis with eslint-plugin-jsx-a11y during development

Periodic testing as part of scheduled reviews:

  • Manual screen reader testing with NVDA
  • Manual keyboard navigation testing across interactive components
  • Browser extension accessibility audits

Automated testing does not catch every issue, so it is complemented by periodic manual testing.