Accessibility statement

Fair Access Shield commits to WCAG 2.2 Level AA conformance across this public site and the authenticated product, as our active baseline. Where a surface is still being remediated, we say so on this page rather than overclaiming.

WCAG is the floor; usable journeys are the target. Our product and our own site checks look for real task blockers, not only passing scanner rows.

• The same accessibility workflow can run in a hosted FAS workspace or support an existing WordPress, CMS, app, or agency release path without breaking route, source, and proof continuity.
• Route and journey review covers forms, navigation, dialogs, responsive layouts, repeated templates, live authoring output, and source-linked fixes.
• Findings should explain the user impact, route, selector, owner, WCAG reference, staged change, rerun result, and before/after proof.
• When a stricter pattern makes the site clearer, easier to use, or more resilient, we try to beat the minimum bar instead of stopping at it.
• Help-first operations include donated scan credits, gifted review capacity, and scoped assignments where supported contributors, including disabled creators and trained reviewers, can take workforce-ready page copy, app content, alt text, proof summary, and export-ready handoff work with human approval.

We don’t pretend the marketing site is perfect — that would be a worse signal than naming the gaps:

• Some third-party embedded surfaces (Stripe Checkout, Google sign-in) are governed by their vendors’ own accessibility programs. We pick vendors with strong track records, but we don’t control their DOM.
• Marketing imagery may use stock photography; we audit it for color-only meaning and add alternative text but cannot retake third-party photos.
• This statement itself is updated when a regression is found or a new criterion is adopted, not on a fixed schedule. The date below is the last time it was reviewed.