NormflussDocument accessibility platform

Document type

Making contracts accessible

Long-form contracts fail accessibility on structure: no real headings, broken numbered clauses, and untagged signature blocks. The failure modes and the remediation checklist.

Contracts fail accessibility on structure rather than on text. They are long, deeply nested reference documents that a reader navigates non-linearly — jumping to a clause, following a cross-reference, checking a defined term — and every one of those movements depends on real structure the file usually lacks. A fifty-page agreement whose headings are merely bold text, whose clause numbering is visual, and whose cross-references are plain text becomes an unnavigable wall for anyone using assistive technology, which defeats the informed-consent relationship a contract is supposed to support.

Where contracts typically fail accessibility

  • Clause numbering (1, 1.1, 1.1.a) is visual formatting, not a real list structure, so a reader cannot navigate by clause or understand nesting.
  • Section headings look like headings but are just bold, larger text, so there is no heading outline to jump between — fatal in a fifty-page agreement.
  • Cross-references ('as defined in Section 4') are plain text with no link, forcing a non-visual reader to hunt linearly through the document.
  • Signature blocks, initials boxes, and schedules are untagged tables or images, so who signs what is not conveyed.
  • Defined terms in a glossary are styled by capitalisation alone, and footnotes float outside the reading order.

Remediation checklist

  • Apply a real heading hierarchy matching the contract's section structure, so the outline is navigable.
  • Encode clause numbering as nested lists so structure and depth are announced.
  • Turn cross-references and a table of contents into real links to their targets.
  • Tag signature and schedule tables properly, with headers, so obligations are clear.
  • Set title, language, and reading order; place footnotes in logical order.
  • Validate against PDF/UA and WCAG structure criteria, and keep the evidence of what was checked.

Related