Skip to main content

Accessibility Statement

FounderForge is a one-person product studio. This page is our honest account of how accessible this website currently is: the standard we are aiming at, what we have actually fixed and how we checked it, and what still fails.

Last reviewed: . This date is fixed to that review, not to the moment you loaded the page.

Conformance status

We aim for WCAG 2.2 Level AA. Right now the site is partially conformant with it. Some content does not yet fully meet the standard, and the barriers are listed plainly below rather than hidden behind a blanket conformance claim.

We deliberately do not publish a conformance score, a percentage, or a certificate. None of those exist for this site, and an inaccurate accessibility statement is worse than no statement at all, because it is a trust claim aimed at exactly the people a barrier excludes.

What we have fixed, and how it was verified

Each item below was checked against the code that ships, and the file it lives in is named so the claim can be disproved.

  • Text contrast meets AA

    Secondary and body text is #A3A3A3 on the #0A0A0A background, a measured 7.85:1 ratio, above the 4.5:1 AA floor for normal text. A separate #737373 token is used only for boundaries that identify a control, where the 3:1 non-text rule applies. Earlier in this project the same #737373 was used for body text at 4.18:1, which failed.

    app/globals.css:126,132

  • Visible keyboard focus on every element

    A 2px accent outline with a 2px offset is applied through a guaranteed focus-visible rule that no component utility can silently remove. The accent clears 3:1 against both the page and card backgrounds.

    app/globals.css:218-223

  • Skip link and consistent landmarks

    The first focusable element in every document is "Skip to main content", and every public route renders its content inside a main landmark with the shared header and footer outside it, so keyboard users can reach the page content in one Tab.

    app/layout.tsx:167-172

  • Browser zoom is not blocked

    The viewport declares user-scalable with a 5x maximum scale, and the type scale is declared in rem, so browser and operating-system text sizing applies. We have not yet verified that every page reflows cleanly at 200% zoom, so see the limitations below.

    app/layout.tsx:131-137

  • Analytics respect your cookie choice

    A consent banner appears on a first visit. Rejecting or dismissing it stores essential-only consent, and the product-analytics and Google Analytics code is not initialized until analytics consent is present. Measured on a first visit before consenting, the only cookie set is Cloudflare's __cf_bm; no PostHog ph_* cookies are written.

    lib/cookie-manager.ts, components/analytics-provider.tsx, components/ui/cookie-banner.tsx

  • Motion can be reduced

    A prefers-reduced-motion reset suppresses CSS animations and transitions and disables smooth scrolling, and every animated component sits inside one configuration that honours the same user preference. Infinite looping animations were removed, because CSS cannot stop them once they are running in JavaScript.

    app/globals.css:301-315, components/providers.tsx:12

  • The interactive demos are keyboard-operable

    Demo tours bind Escape to close and Arrow keys to move forwards and back; the travel-planner combobox implements Arrow, Home, End, Enter and Escape; task toggles expose a checkbox role with a checked state, and filter buttons expose a pressed state. State changes inside the demos are announced through status regions.

    components/seamless-performance/ECommerceTour.tsx:158-175, components/anticipatory-design/DestinationInput.tsx, components/microinteraction-guide/TaskItem.tsx

  • Controls are labelled and sized for touch

    The shared button component gives every button it renders a minimum 44x44px target, which exceeds the 24px WCAG 2.2 AA target-size minimum. Icon-only controls in the consent UI, the header, and the demos carry explicit accessible names, and the demo text inputs have a real associated label plus described hints and errors. We have not verified labelling exhaustively on every page, so a missing label is possible.

    components/button.tsx:34-36, components/microinteraction-guide/TaskInput.tsx, components/ui/cookie-banner.tsx

  • A single declared language and theme

    The document declares lang="en" and a dark colour scheme, so assistive technology reads the page in the right language and native form controls, scrollbars and selection colours match the dark theme instead of flashing white.

    app/layout.tsx:145, app/globals.css:118

  • Some of this is checked automatically

    A browser test walks the keyboard through the first 30 focusable controls and fails if any of them shows no visible focus ring, probes every visible text element against the AA contrast thresholds (3:1 for large text, 4.5:1 otherwise), asserts exactly one top-level heading with no skipped levels, and checks that these routes do not scroll sideways at a 320px viewport.

    tests/e2e/ui-ux.spec.ts

Known limitations

These are the barriers we know about and have not closed yet.

  • No third-party audit

    This statement comes from our own review of the source code, measured contrast ratios, and keyboard traversal. No external accessibility audit has been performed, no conformance score has been issued, and no auditor has certified this site. Treat every claim here as self-assessed.

  • Announcements are inconsistent outside the demos

    The interactive demos announce state changes, but there is no site-wide live-region convention. Elsewhere in the product, a message that appears or changes after the page loads may not be announced by a screen reader.

  • Demo cues were reviewed, not exhaustively tested

    The interactive demos reveal their explanation highlights on hover and on focus, and their tours run on the keyboard. But a demo renders a long run of simulated controls — product cards, song rows, filter buttons — and there is no skip control inside a demo, so a keyboard visitor may have to Tab through all of them before reaching the next real section of the page. We have not verified every cue in every widget one by one.

  • Text enlargement beyond default size is untested

    Zoom is allowed and the type scale is relative, and a 320px-wide reflow check runs automatically on these routes. But nothing here has been walked through at 200% browser zoom or with an operating-system large-text setting, and the interactive demos have not been checked at either. We do not claim SC 1.4.4 (Resize Text) conformance.

  • Dark-only, with no contrast control

    There is exactly one theme. There is no light theme, no high-contrast mode, and no in-page contrast or colour control of any kind; the dark palette is a deliberate brand decision. If you need a light background, reduced glare, or your own colour scheme, you currently have to rely on a browser extension or OS override, which we have not tested against this site.

  • Third-party widgets are outside our control

    The booking widget opens inside a third-party Cal.com popup, and parts of the analytics stack are third-party code. We can report a barrier to those vendors, but we cannot fix or guarantee their interface.

  • Automated checks cover colour and structure, not people

    The tests we run can measure a contrast ratio, a focus ring, a heading outline, and a 320px overflow. They cannot hear what a screen reader says, so they do not verify that labels, roles, and announcements actually make sense read aloud, and they do not exercise assistive technology at all. An older accessibility spec in the same suite has checks named "contrast" that only assert an element is visible, so passing our tests narrows the risk rather than proving conformance.

  • Assistive technology has not been used systematically

    No defined matrix of screen readers, browsers, and braille output has been walked through this site. The keyboard and colour work was checked without assistive technology, so a barrier that only appears when a reader speaks the page is entirely possible. If the setup you rely on hits one, that is a real bug and we want to hear about it.

How this statement was produced

Method: a review of the shipped source for the structures this page claims (landmarks, focus handling, colour tokens, consent gating, keyboard bindings), measured colour-contrast ratios for the text tokens, manual keyboard traversal of the main routes and the interactive demos, and an automated browser suite that re-measures contrast, focus indicators, heading structure, and 320px reflow on every content route. There is no screen-reader testing with a human assistant and no external audit.

Scope: this website and its interactive demos. It covers the pages we control. It does not cover third-party interfaces we embed, and it is not a formal audit.

Cadence: reviewed again when a change affects accessibility, and on request. When the review date above is older than six months, assume the site may already have drifted from what is written here.

Report a barrier or request content another way

If anything on this site is hard for you to use, tell us. Send the page address, what you were trying to do, and the browser plus assistive technology you were using. If you need information from this site in a different format, ask for that the same way and we will provide it.

founderforgedxb@gmail.com

This is a one-person studio, so we do not publish a response-time guarantee we cannot keep. We read every accessibility report, we will confirm it reached us, and barriers that fail WCAG 2.2 AA get fixed as part of the next relevant change to that area.

If you are not satisfied with our response

You can contact us again by the email above and escalate to us directly. Depending on where you live, a national accessibility complaints scheme or your equality regulator may be able to review a report we have not acted on.