Legal

Accessibility statement.

Last updated: May 11, 2026 Targets WCAG 2.1 AA Partially conformant

01Our commitment

Budday treats digital accessibility as a right, not an option. Every page of budday.app is designed to be usable by everyone, including people navigating with the keyboard alone, with voice control, with screen magnification, or with a screen reader (NVDA, VoiceOver, TalkBack).

This statement applies to the public marketing site. It will be updated before every new section ships or any major redesign, and at minimum once per year.

02Conformance level

The site is partially conformant with WCAG 2.1 Level AA (Web Content Accessibility Guidelines), which underpins both the French RGAA 4 baseline and the EU standard EN 301 549 V3.2.1. "Partially conformant" means most of the standard is met, with the exceptions listed below.

Practically, that means nearly every AA criterion is met, including colour contrast, keyboard navigation, form labels, heading structure, text alternatives for images, and honoring prefers-reduced-motion on entrance animations.

03Methodology

The audit combines three passes:

  • Automated audit: the axe-core suite runs on every page (8 main pages × 2 languages × 2 motion modes) and blocks any deploy that introduces a serious or critical violation.
  • Keyboard manual pass: every page is walked end-to-end using only the keyboard (Tab / Shift+Tab / Enter / Space / Escape / arrows). The skip-link is always the first stop and no focus trap is tolerated.
  • Screen-reader pass: a representative sample of pages is reviewed with VoiceOver (macOS Safari), NVDA (Windows Firefox), and TalkBack (Android Chrome) to verify landmark / heading / list semantics, announcement of state changes (form submitted, modal opened), and quality of text alternatives.

04Tested coverage

The audit covers every route on the site:

  • Main pages: Home, Manifesto, How it works, Pricing, Legal notice, Privacy, Terms, Cookies (8 routes × 2 languages).
  • Dynamic pages: blog index, blog articles (hubs + spokes), recipes, condition pages.
  • Interactive states: consent banner (banner + granular modal), waitlist signup form (idle / submitting / success / error states), mobile burger menu, FAQ disclosures.
  • Modes: default motion and prefers-reduced-motion: reduce.

05Known limitations

No serious or critical violation is tolerated in production. A few areas you should be aware of:

  • Embedded third-party content: analytics (Google Analytics and Microsoft Clarity, loaded only after you grant analytics consent) expose no UI surface; no cookie or script runs until you accept.
  • Untranslated dynamic routes: a handful of blog posts, recipes, and condition pages are not yet translated into the second language. The FR ↔ EN toggle redirects you to the closest available page, never a 404.
  • Entrance animations (FadeIn): during the first 200 to 600 ms after a section enters the viewport, some elements are semi-transparent. This is compliant with WCAG 2.3.3 (Animation from Interactions) and disabled entirely under prefers-reduced-motion: reduce.

06Report a defect

If you run into an accessibility defect, we want to know. Email us with as much detail as possible (the URL, what page you were on, the assistive tool you used, your browser and OS):

We commit to replying within 7 working days and to fixing any prioritised non-conformance (serious or critical) within the next 30 days.

07Appeals and recourse

If our response doesn't satisfy you, you can refer the matter to:

The audit is conducted in-house by the product team. Latest audit date: May 11, 2026. The next full audit is scheduled within 12 months or before any major redesign.