Fair Access Shield shield mark

Security and procurement

Fair Access Shield

Built for review before rollout.

Fair Access Shield is designed for public-facing teams that need accessibility work to move through identity, isolation, validation, evidence, procurement, and vendor review without losing the source-owned workflow, whether they publish in a hosted FAS workspace or export approved changes and proof back to WordPress, a CMS, an app, or an agency-managed release process.

Isolation and scan boundaries

  • Submitted sites run through guardrails for authority, duplicate free scans, bot traffic, and unsafe targets.
  • Private network targets, direct downloads, oversized responses, and unsupported content types are blocked before scanning.
  • Workspace crawler capacity can be separated by tier, with dedicated scan workspace expectations for large enterprise programs.

Data and retention posture

  • Signed-out public scans are designed to avoid long-term raw external-code persistence.
  • Paid workspaces preserve the source package, findings, decisions, staged edits, reruns, and proof artifacts needed for accountable work.
  • Visual edits, managed VS Code source work, AI-assisted notes, approvals, hosted release paths, existing-platform exports, and proof packages stay tied to the same route context for review.
  • Draft privacy and terms pages remain marked noindex until counsel review is complete.

Enterprise procurement packet

Teams can review plan limits, identity boundaries, billing flow, retention notes, accessibility testing scope, security headers, and vendor review context.

Evidence-ready operations

Findings can carry route, selector, WCAG reference, owner, source path, staged change, rerun result, before/after record, and proof export context.

Request security review

For procurement, vendor review, or enterprise security review, contact security@fairaccessshield.com.

Open contact paths