Skip to main content
Accessibility

A platform built to be used by everyone.

Beedy is designed and developed to follow WCAG 2.2 AA guidelines so everyone — regardless of ability — can browse pros, book services and manage their account without friction.

Last updated: 12 May 2026

Our commitment

Accessibility is a core product principle at Beedy. We treat it like any other quality requirement: it's baked into our design system, reviewed before every release, and audited by an independent third party every 12 months.

When something doesn't work well for assistive technologies — or just for a customer who happens to use the platform differently — we treat it as a bug worth fixing fast.

Standard followed

Beedy targets WCAG 2.2 Level AA conformance, which is the de facto standard for compliance with Title III of the Americans with Disabilities Act (42 U.S.C. §§ 12181–12189) for places of public accommodation. We also align with Section 508 of the Rehabilitation Act (29 U.S.C. § 794d) where federal-procurement nexus applies. Internal audits run on every major release; the latest external audit was conducted in March 2026.

Visual accessibility

For users who rely on screen readers, magnification, custom colors or simply struggle with low contrast.

What we've shipped

  • High color contrast: All text, icons and interactive elements meet at least the WCAG AA contrast ratio (4.5:1 for body text, 3:1 for large text and graphics).

  • Alt text on every image: Each photo, illustration and decorative icon has an appropriate alt attribute (or aria-hidden when purely decorative) so screen readers convey the right context.

  • Resizable text and zoom-friendly layouts: The interface stays usable up to 200% browser zoom; respecting your OS font-size preference works the same on web and mobile.

Auditory accessibility

For deaf or hard-of-hearing users — and for anyone who prefers reading over listening.

What we've shipped

  • Captions on every video: Help-center tutorials and marketing videos ship with synced captions in every supported language.

  • Transcripts: Audio-only content (e.g. podcasts) is paired with a full text transcript next to the player.

  • No audio-only critical info: Notifications and important alerts never rely on sound alone — there is always a visual or textual equivalent.

Motor accessibility

For users navigating with a keyboard, switch device or voice control.

What we've shipped

  • Full keyboard navigation: Every interactive element is reachable via Tab and operable via Enter/Space. Skip-to-content links jump past the header.

  • Clear focus indicators: A visible focus ring (or high-contrast outline) appears on every focused element — never relying on color alone.

  • Generous touch targets: Buttons and inputs are at least 44×44 px on mobile, meeting Apple HIG and WCAG 2.5.5 (target size) recommendations.

Cognitive accessibility

Clarity helps everyone — but it's essential for users with dyslexia, ADHD, anxiety, or anyone in a stressful moment.

What we've shipped

  • Plain language: Copy is written in straightforward sentences. Legal pages and help articles avoid jargon and explain technical terms inline.

  • Consistent layout: Navigation, terminology and visual hierarchy stay consistent across the platform so muscle memory works.

  • No surprise actions: Destructive actions (delete account, cancel booking) always require a confirmation step and clearly describe the consequence.

Known limitations

We aim for full WCAG 2.2 AA conformance but a few areas remain in progress. We list them publicly so you know exactly what to expect and how to work around them.

In-progress items

Some third-party embeds (legacy map provider, certain payment iframes) are not yet fully accessible to screen readers. We are migrating these dependencies over the next two releases.

Feedback & support

Run into an accessibility issue? We'd love to hear about it — every report ends up on our backlog with a target turnaround of 7 days for AA-level bugs. We acknowledge every email within 2 business days.

Accessibility team

accessibility@beedy.app

Frequently Asked Questions (FAQ)

More accessibility questions? Reach out to our team.

Spotted an accessibility issue? Tell us.

We treat accessibility bugs the same way as any other — they go straight to the engineering backlog. Drop us a line and we'll work with you to find a fix.