Effective date: August 18, 2025
Next review: February 18, 2026 (or upon material change)
Applies to: hyvery.com websites, documentation, trust/status pages, and the Hyvery SaaS web and mobile apps (collectively, the “Services”).
Hyvery is committed to providing an accessible experience for all users, including people with disabilities. We are working to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and to apply accessibility‑by‑design throughout our product and content lifecycle.
Conformance status: Based on internal testing and third‑party scans, our goal is conformance with WCAG 2.1 AA. Some areas are still being improved; see Known Issues & Roadmap below.
Design & UX: Inclusive design reviews; color‑contrast checks; keyboard flows defined in UX specs.
Engineering: Semantic HTML, proper headings/landmarks, labeled form controls, ARIA only where needed, visible focus states, skip links, responsive layout, and reduced‑motion support.
Media: Captions and transcripts for videos; descriptive alt text for images; accessible PDFs or alternate HTML.
Testing: Automated audits (axe, Lighthouse), manual keyboard testing, screen reader checks (NVDA, JAWS, VoiceOver), and cross‑browser/OS testing.
Content: Plain‑language style, meaningful link text, consistent navigation, error prevention and recovery.
Governance: Accessibility owner (see Contact & Accommodations), training for designers/engineers, and accessibility acceptance criteria in our definition of done.
Browsers: Latest two versions of Chrome, Edge, Firefox, and Safari.
Operating systems: Current macOS, Windows, iOS, and Android.
Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS/iOS).
Zoom & reflow: Up to 200% browser zoom without loss of content or functionality.
Input methods: Full keyboard navigation; pointer; touch. We aim to avoid keyboard traps and ensure logical tab order.
We continually improve and track progress. Current items under remediation include:
Color contrast exceptions on a few legacy marketing components (target: Q4 2025).
Form error messages lacking programmatic associations in some admin dialogs (target: Q4 2025).
Non‑text content missing descriptive alt text in a small number of older help articles (target: rolling fix).
If you encounter an issue not listed here, please let us know (see below).
Some integrations or embedded third‑party widgets (e.g., maps, video players, analytics notices) are outside of Hyvery’s direct control and may not fully meet WCAG. We work with vendors to improve accessibility and provide alternative access where feasible.
If you need an accommodation to access our Services or documentation, or to report an accessibility issue, please contact us:
Email (preferred): accessibility@hyvery.com
Alternate email: support@hyvery.com
Phone (toll‑free): 1‑833‑HYVERY‑0
Mail: Hyvery, Inc., 4004 Sunburst View Cir., Kissimmee, FL 34746 USA
What to include: page or feature name, description of the issue, assistive technology used (if any), and your contact details.
Response time: We typically respond within 2 business days. For urgent access needs, please call the toll‑free number above. We will provide information in an alternative format (e.g., accessible HTML, tagged PDF) upon request.
We welcome relay calls (e.g., 711) and will communicate in your preferred format when feasible.
If you believe we have not addressed your concern, reply to our email thread with “Accessibility Escalation” in the subject line to reach our Accessibility Owner. We will review and follow up with next steps and timelines.
We review this statement at least biannually, incorporate user feedback, and update our accessibility backlog and training accordingly. As WCAG 2.2 becomes broadly supported, we will extend our target to WCAG 2.2 AA.