Statutory forms with accessibility and retention duties
A statutory form has to be correct, reachable by everyone, and provable years after it was published.
Accessibility is a duty, not a backlog item
Accessible names, reading order and tagging are validated on every revision, so a form cannot quietly regress between publications.
Retention needs the record, not the file
What was published, when, in which release, approved by whom — exported as files plus NDJSON whenever your retention process needs it.
Language variants are part of the form
Font subsets are checked against the characters a form can actually render, which is how a Welsh or Gaelic variant gets caught before print rather than after.
Start with an estate assessment
Point YakForms at a copy of your repository. You get an inventory, a dependency graph and a validation report for the whole estate — before you commit to anything.