Skip to main contentYeeHaul

Accessibility

YeeHaul is for everyone. That is not a line in a policy document. It is how we build.

We design for people with disabilities because our product does not work if it does not work for everyone who needs a dumpster. If something on this site gets in your way, that is our problem to fix — not yours to work around.


Where We Stand

We target the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standard. If we missed something, tell us and we will fix it.


Known Limitations

Some parts of YeeHaul rely on third-party tools we do not build or control:

  • Authentication is handled by Clerk. Their components follow accessibility best practices, but we cannot guarantee they meet every WCAG 2.1 AA requirement at all times.
  • Payments are processed through Stripe. Stripe maintains its own accessibility standards for checkout and payment elements.

If you run into a barrier in either of those experiences, tell us anyway. We will raise it with the provider and find a workaround in the meantime.


What We Are Doing About It

We are actively working to improve accessibility across the site. That means:

  • Auditing existing pages for keyboard navigation, screen reader support, color contrast, and focus management
  • Building new features with accessibility as a requirement, not an afterthought
  • Fixing reported issues as they come in — not adding them to a backlog to sit

There is no six-month roadmap here. When something is broken, we fix it.


Tell Us What Is Not Working

If you hit a barrier on this site, we want to hear about it.

Email: a11y@yeehaul.app

Tell us what page you were on, what you were trying to do, and what got in the way. We will respond within two business days, and we will give you a straight answer about what we are going to do about it.

No ticket number. No runaround. A person reads that inbox.


Browser and Assistive Technology Support

YeeHaul is built for modern browsers and tested with common assistive technologies:

  • Browsers: Chrome, Firefox, Safari, Edge (current and one prior version)
  • Screen readers: VoiceOver (macOS/iOS), NVDA (Windows), TalkBack (Android)

If you are using a supported browser and screen reader combination and something does not work, that is a bug. Report it.


How We Test

We use a combination of automated and manual testing:

  • Automated: Linting and CI checks catch structural issues — missing alt text, empty links, low contrast ratios
  • Manual: Keyboard-only navigation, screen reader walkthroughs, and real-device testing on every major release

Automated tools catch roughly 30% of accessibility issues. We do not rely on them alone.


Last Updated: March 29, 2026