Sample acceptance report

A migration is complete only when the evidence reconciles.

This synthetic fixture demonstrates the reporting method Romeo Apps can apply to a content-rich website migration. The figures below are illustrative, not client results or a compliance certification.

Fixture: 20 source sites to 1 target
Standard: WCAG 2.2 AA regression
Browsers: Chromium, Firefox, WebKit
Decision: Hold

1,248

source URLs inventoried

1,216

target pages matched

intentional redirects

blocking document miss

Reconciliation ledger

Every source record receives a target outcome.

Illustrative sample rows. Production evidence includes the full machine-readable ledger.
Source	Target	HTTP	Content	Metadata	Media	Result
`/publications/report-a`	`/library/report-a`	301 to 200	Matched	Matched	2/2	Pass
`/events/forum-2025`	`/events/forum-2025`	200	Matched	Review	5/5	Review
`/files/brief.pdf`	`/media/brief.pdf`	404	n/a	n/a	0/1	Block
`/task/42/about`	`/themes/biorefining`	301 to 200	Matched	Matched	3/3	Pass

A redirect passes only when the chain ends at the intended canonical target without loops, hops beyond the agreed limit, lost query behavior, or a soft 404. Documents and media are reconciled separately from pages.

Evidence contract

Automated breadth, manual judgment, explicit ownership.

Inventory

Source URL, content type, locale, status, canonical, title, description, H1, body fingerprint, media references, visibility, and owner.

Artifactsource-inventory.csv

Routing and SEO

Target mapping, redirect chain, canonical, sitemap membership, robots state, metadata preservation, and indexability exceptions.

Artifacturl-map-results.json

Content and media

Normalized text comparison, missing blocks, publication fields, downloads, image responses, alt coverage, and broken internal references.

Artifactreconciliation-ledger.csv

WCAG regression

WCAG 2.2 AA-oriented automated checks plus keyboard path, focus order, labels, landmarks, zoom/reflow, contrast, and screen-reader spot checks.

Artifactaccessibility-evidence.html

Browser and roles

Chromium, Firefox, and WebKit at agreed desktop/mobile viewports; public, editor, and member journeys tested with synthetic accounts.

Artifactjourney-matrix.json

Launch decision

Blocking defects, accepted exceptions, owners, evidence links, rollback readiness, monitoring window, and signed acceptance criteria.

Artifactlaunch-decision.md

Illustrative decision

Hold launch until the missing PDF is restored or explicitly retired.

The sample has one blocking mismatch: a source document has no working target. The report does not turn that failure into a percentage-based pass. It records the exact owner, correction, rerun, and acceptance evidence required.

Restore the target document or obtain written retirement approval.
Rerun the document ledger and internal-link crawl.
Attach the corrected response, checksum, and route result.
Change the decision only after the blocker closes.

Boundary

Evidence supports acceptance. It does not replace accountability.

This method does not promise legal certification, perfect equivalence, search ranking, or production safety from automated scans alone. The final plan names the required manual checks, client-owned decisions, protected-content access, privacy constraints, and post-launch monitoring before work begins.