GetMyYes

Accessibility Statement

Last reviewed: July 13, 2026

Our commitment: GetMyYes aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA across the complete appeal workflow. Accessibility is an ongoing practice, and we welcome reports of barriers.

WCAG 2.0 Level AA is also published as the international standard ISO/IEC 40500:2012. Because WCAG 2.2 Level AA includes every WCAG 2.0 Level AA success criterion, the target above covers that standard as well. Conformance here is our own substantiated claim, not a third-party certification.

Measures we take

  • Use semantic headings, landmarks, labels, instructions, and meaningful control names.
  • Support keyboard navigation, visible focus, screen-reader status announcements, text resizing, reflow, reduced motion, and high-contrast settings.
  • Maintain text and interface contrast at WCAG AA thresholds and avoid using color alone to convey meaning.
  • Test representative pages and the upload-to-purchase process with automated checks and manual keyboard, zoom, mobile, and assistive-technology reviews.
  • Review accessibility when shared components, templates, or critical workflows change.

Documents and third-party services

Your appeal packet is available as structured on-screen content and as an accessible HTML download. The PDF is an additional convenience format and may not preserve the same heading, landmark, and reading-order information. Use the on-screen packet or HTML download when you need those accessibility features.

Payment is completed on a Stripe-hosted checkout page. If any part of checkout creates an accessibility barrier, contact us for support so we can help you access the service and investigate the problem.

Compatibility and testing

We design for current versions of major browsers and commonly used screen readers, keyboard-only navigation, browser zoom up to 400%, touch input, reduced-motion preferences, and forced-colors or high-contrast modes. Automated testing is useful but cannot identify every barrier, so it is supplemented with manual review.

Known limitations

We are continuing manual testing of the complete Flutter web application with multiple browser and screen-reader combinations. We do not claim that an automated score or accessibility overlay constitutes certification. When we identify a barrier, we prioritize the upload, review, payment, and document-access workflows.

The appeal packet PDF carries document metadata but is not a tagged (PDF/UA, ISO 14289-1) document, so it does not expose a reading order to assistive technology. The same content is available as text in the app, and we will move to tagged output when our PDF toolchain supports it.

Report an accessibility problem

Email support@getmyyes.com. If you are comfortable doing so, include the page or task, what happened, and the browser or assistive technology you were using. We will work with you to provide the information or service through an accessible alternative while we address the problem.