X00-09 — PDF/UA accessibility preflight #148

Outcome

Decide whether Loop adds a PDF/UA accessibility profile family for digital deliverables.

Parent and boundary

Parent: #110. This is an expansion candidate. Produce a value case, owning module, contract sketch, and threat notes, then record go, no-go, or defer. No implementation lands from this issue. A new public PDF, schema, worker, or workflow contract needs an architect checkpoint with concrete fixtures and migration behavior.

Grounding

• The European Accessibility Act has applied since 2025-06-28; print customers often deliver a digital twin of the print file.
• Loop has no PDF/UA or tagged-structure checks.

Decision inputs

• Scope limited to machine-checkable Matterhorn Protocol conditions, with human-check conditions reported as not-inspected.
• An independent oracle (for example veraPDF's PDF/UA profiles).
• Demonstrated customer demand.
• Failure case: a PDF/UA pass is never claimed for conditions that need human judgment.

Required proof

Decision record with the value case (user, frequency, current alternative, evidence), owning module, contract sketch, fixtures or corpus plan, independent oracle where a claim is made, and risks.

Handoff

State go, no-go, or defer. On go, file bounded implementation sub-issues under the owning module parent and link them here.

Sources

Approved master roadmap §5 · Gap review of the issue suite against the approved roadmap, 2026-09-27.