Skip to main content
Accessibility

We want get that bread to work for everyone.

We're building toward WCAG 2.1 Level AA. Not perfect yet — but we're honest about it, and we fix what you tell us.

Last updated: 25 May 2026

Our commitment

get that bread aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That includes a usable experience for people using screen readers, keyboard-only navigation, voice control, browser zoom, and high-contrast modes.

We're an early-stage product. We won't pretend everything is already compliant — but we treat accessibility as a launch requirement on every new surface, and we re-audit when something regresses.

What we've done

  • Semantic HTML throughout — proper headings, landmarks, lists, and form labels.
  • Keyboard navigation across primary flows (browse, pledge, dashboard, dispute). Focus rings preserved, no outline: none without a replacement.
  • Colour contrast tested against WCAG AA targets (4.5:1 for body text, 3:1 for large text and meaningful icons) in both light and dark themes.
  • prefers-reduced-motion respected — animations and scroll-triggered effects are reduced or removed for users who request it.
  • Alt text on meaningful images; decorative imagery marked with empty alt.
  • Form fields with associated labels, error messages programmatically linked, and required fields announced.
  • Cookie banner is not a focus trap; reject-all is a peer of accept-all (no dark-pattern X-only dismissal).

Known gaps

We're actively working on:

  • Comprehensive screen-reader QA across the creator dashboard — currently spot-tested, not exhaustively audited.
  • Some embedded third-party components (chat widget, video player) inherit accessibility from the upstream vendor and may not always meet AA.
  • PDFs (campaign receipts) — we're moving toward tagged PDFs as a default.

If you hit one of these — or anything else — please tell us. Real reports beat synthetic audits every time.

Report a barrier or request an alternative format

Email hello@getthatbread.sg with:

  • The page or feature where you hit the barrier (a URL is great).
  • What you were trying to do.
  • The assistive technology you're using, if any (e.g. VoiceOver on iOS, NVDA on Windows).
  • What an alternative format would look like for you, if you're requesting one.

We respond within 2 business dayswith an acknowledgement, and follow up with a plan once we've reproduced the issue.

Standards we don't formally claim

We don't hold any third-party accessibility certification today. We don't claim WCAG 2.2 AAA, EN 301 549, or US Section 508 conformance. If you need a formal VPAT or ACR for procurement, please reach out and we'll work with you on a current-state assessment.