Accessibility statement

Last updated: 2026-05-19
Effective date: 2026-05-19
Customer-facing URL: https://qortara.com/legal/accessibility

MythologIQ Labs LLC is committed to making the Qortara service ("Service") and the qortara.com website usable by as many people as possible, including people with disabilities. This statement describes our current accessibility posture, the standards we target, the gaps we are aware of, and how to reach us with feedback.

1. Standard we target

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the World Wide Web Consortium (W3C). Where WCAG 2.2 success criteria can be adopted without regression, we adopt them.

We do not claim certified conformance. The Service is in active pre-launch development, and any conformance statement reflects best-effort progress at the date of this document.

2. Current state

2.1 What works reasonably well

  • semantic HTML throughout the marketing site and dashboard;
  • keyboard navigation for primary flows on the marketing site;
  • visible focus indicators on interactive controls;
  • text content that meets WCAG AA contrast ratios for body copy;
  • ARIA labels on navigation landmarks and primary form controls;
  • text-resize support up to 200% without loss of content or function;
  • responsive layout that works on common screen sizes including mobile.

2.2 Known gaps

We acknowledge the following gaps and are tracking them for remediation. We will close them on a best-effort schedule.

  • Some dashboard data tables and visualizations have incomplete keyboard support and screen-reader semantics. Use the API or JSON export as an alternative path while we close the gap.
  • Some long-running operations rely on visual progress indicators that have limited screen-reader announcements.
  • Color is occasionally used as the sole channel for status (for example, trust-score color coding). We are layering iconography and text alternatives.
  • Automated accessibility testing is not yet integrated into our CI pipeline. We rely on manual review during development.
  • We have not engaged a third-party accessibility audit. Pursuing one is on the roadmap.

If you encounter an issue not listed here, please let us know (see §5).

3. How we test

  • manual keyboard navigation review of primary flows during development;
  • screen-reader spot checks against NVDA on Windows and VoiceOver on macOS and iOS;
  • contrast and structural review using browser developer tools;
  • review of color usage against contrast and color-blind palettes.

We do not yet conduct user research with people with disabilities. We welcome inbound feedback while we build that program.

4. Assistive technology

The Service is designed to work with current versions of mainstream assistive technologies, including:

  • screen readers: NVDA, JAWS, VoiceOver, TalkBack;
  • voice-control: Dragon NaturallySpeaking, Voice Control (macOS/iOS), Voice Access (Android);
  • screen magnification and OS-level zoom.

If you find a specific incompatibility, we want to hear about it.

5. Feedback and remediation requests

Tell us about accessibility issues, request an alternative format for content, or ask for help completing a task on the Service.

  • Email: accessibility@qortara.com
  • Subject line suggestion: "Accessibility — [brief description]"
  • Response target: best-effort acknowledgement within 5 business days

If you are unable to complete a task on the Service because of an accessibility barrier, contact accessibility@qortara.com and we will work with you to find an alternative path while we remediate.

6. Legal note

This statement is provided in good faith and does not constitute a warranty or guarantee of conformance with any specific standard or law. Accessibility is an ongoing process, and the state of the Service will change over time.

7. Contact

  • Accessibility: accessibility@qortara.com
  • General support: support@qortara.com
  • Legal: legal@qortara.com