Accessibility Statement

Standard: Web Content Accessibility Guidelines (WCAG) 2.2.

Gamyata partially conforms with WCAG 2.2 Level AA. “Partially conforms” means that some parts of the content do not fully conform to the accessibility standard. We are actively closing those gaps; the latest known issues are listed in the “Limitations and Alternatives” section below.

Gamyata is designed to work with the following assistive technologies:

• NVDA 2024+ on Chrome and Firefox (Windows)
• JAWS 2024+ on Chrome and Edge (Windows)
• VoiceOver on Safari (macOS Sonoma+ and iOS 17+)
• TalkBack on Chrome (Android 13+)
• Browser zoom up to 200% with no loss of content or functionality
• Operating-system high-contrast and forced-colors modes
• Keyboard-only navigation across all primary user flows

We do not yet formally support voice-control software (Dragon NaturallySpeaking, Voice Control). Basic operability via standard input APIs is expected to work but is not part of our regression suite.

Accessibility of Gamyata relies on the following technologies to work with the combination of web browser and any assistive technologies installed on your computer:

• HTML5
• WAI-ARIA
• CSS
• JavaScript (used progressively; primary content readable without JS)

Despite our best efforts, the following accessibility issues are known to exist on the Gamyata application as of the last review date. They are tracked in our internal issue queue.

• Skip link discoverability (WCAG 2.4.1, minor): the “Skip to main content” link is present on marketing pages but not on every authenticated dashboard variant. Workaround: keyboard users can press Tab from page load and the link surfaces on focus.
• Breadcrumbs on deep pages (WCAG 2.4.8, minor): some scan-result sub-views lack a breadcrumb landmark. Workaround: the back button and primary navigation remain functional; scan IDs are encoded in URLs for direct return.
• Line-height on report tables (WCAG 1.4.8, minor): some tabular text uses a line-height below the WCAG 1.4.8 recommended 1.5×. Workaround: browser text-spacing overrides apply correctly.
• Live audio captions (WCAG 1.2.4): not applicable today; the product contains no live audio. We will revisit if/when we ship live demos.

See the live machine-readable view at /vpat for a per-criterion conformance table generated by our own engine against https://gamyata.com.

This statement was prepared on 19 April 2026 using the following approach:

• Self-evaluation via the same Gamyata engine that powers customer scans, run against our public marketing site and authenticated dashboard.
• Manual keyboard and screen-reader walk-throughs of the primary user flows (signup, scan submission, results review, billing).
• Cross-reference against EN 301 549, Section 508 Revised, and IS 17802 mappings documented in our Trust Center.

Statement methodology: self-assessment with engine-assisted evidence. We do not yet hold an external third-party audit; one is planned for the post-GA period.

We welcome feedback on the accessibility of Gamyata. If you encounter accessibility barriers, please contact us. We aim to respond within 5 business days.

When reporting an issue please include: the URL where you encountered the barrier, the assistive technology and browser you were using, and a brief description of what went wrong. Screenshots or screen recordings are welcome but not required.

Users in the European Union who are not satisfied with the response to their accessibility complaint may escalate to the relevant national enforcement body under the European Accessibility Act (Directive (EU) 2019/882). Users in the United States may file complaints under Section 508 (federal procurement) or the Americans with Disabilities Act (ADA Title II / Title III) where applicable.

Learn more about WCAG 2.2