Back to GetToInbox.com

Legal

Accessibility Statement

Our commitment to making GetToInbox.com accessible to everyone.

Effective: April 1, 2026·Last Updated: April 12, 2026·GetToInbox.com · CircleVenue LLC · San Francisco, CA
01

Our Commitment

GetToInbox.com is committed to ensuring that our website and services are accessible to everyone, including people with disabilities. We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as published by the World Wide Web Consortium (W3C).

We believe that accessibility is not a feature — it is a baseline requirement. Every person who needs to understand their email deliverability posture deserves to be able to use our tools.

02

Measures We Take

Semantic HTML and ARIA. We use semantic HTML5 elements and ARIA (Accessible Rich Internet Applications) landmarks, labels, and roles to ensure screen readers can accurately interpret page structure and interactive elements.

Keyboard navigation. All interactive elements — including the domain scanner, navigation menus, modal dialogs, and form fields — are fully operable using a keyboard alone. Focus indicators are visible on all interactive elements.

Color contrast. We maintain a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text and UI components, in compliance with WCAG 2.1 Success Criterion 1.4.3.

Text alternatives. All meaningful images include descriptive alt text. Decorative images are marked with empty alt attributes so screen readers skip them.

Responsive design. The site is fully responsive and usable on screen sizes from 320px wide and above, including mobile devices and tablets.

Reduced motion. We respect the prefers-reduced-motion media query. Users who have enabled reduced motion in their operating system settings will see simplified or no animations.

Form accessibility. All form fields have associated labels. Error messages are descriptive and programmatically associated with the relevant field. Required fields are clearly indicated.

Skip navigation. A "Skip to main content" link is available at the top of every page for keyboard and screen reader users.

03

Known Limitations

We are continuously working to improve accessibility. The following limitations are known and are being actively addressed:

AreaLimitationStatus
Domain scan resultsSome complex data tables may not be fully optimized for screen reader navigationIn progress
PDF reportsDownloaded PDF reports may not be fully tagged for screen reader accessPlanned improvement
Third-party widgetsSome third-party components (e.g., payment processing) may have their own accessibility limitations outside our controlMonitoring
04

Assistive Technologies Tested

We test GetToInbox.com with the following assistive technologies:

  • Screen readers: NVDA (Windows), VoiceOver (macOS and iOS), TalkBack (Android)
  • Keyboard-only navigation: Tested across Chrome, Firefox, Safari, and Edge
  • Browser zoom: Tested at 200% zoom without loss of content or functionality
05

Feedback and Assistance

We welcome feedback on the accessibility of GetToInbox.com. If you encounter any barriers, need content in an alternative format, or require assistance using any part of our site, please contact us:

  • Email: [email protected]
  • Phone: (415) 894-9592
  • Response time: We aim to respond within 2 business days.

If you are unable to access any content or use any feature of our site, we will work with you to provide the information or service you need through an alternative means.

06

Formal Complaints

If you are not satisfied with our response to your accessibility concern, you may contact the relevant accessibility authority in your jurisdiction. In the United States, you may file a complaint with the U.S. Department of Justice Civil Rights Division.

07

Standards and Guidelines

This statement references the following standards:

Accessibility is an ongoing effort. We conduct periodic accessibility audits and address identified issues as part of our regular development cycle. Last formal accessibility review: April 2026.

Questions about this document? Contact our privacy team: