Skip to content

Print Accessibility β€” Proposed Requirement Inventory

Status: DRAFT FOR REVIEW β€” prose not yet written. Approve / edit IDs and scope before I write the sections. Related: Issue #2852

Notation per line: ID β€” title Β· (provisional level; provisional source-strength). Levels and strengths below are proposals to be confirmed during sourcing β€” a MUST here only survives to prose if it traces to a verified statute/regulation/claimed standard. Anything I expect to end up consensus-only is marked so now to avoid false confidence. IDs are permanent once approved; gaps in numbering are intentionally left for future insertions.


  • PRINT-LEGAL-001 β€” ADA Title II auxiliary aids & effective-communication duty for hardcopy (MUST; regulation β€” 28 CFR 35.160)
  • PRINT-LEGAL-002 β€” ADA Title III auxiliary aids duty (public accommodations) (MUST; regulation β€” 28 CFR 36.303)
  • PRINT-LEGAL-003 β€” Primary-consideration distinction: Title II honors requested format vs Title III’s flexibility (SHOULD; regulation + guidance)
  • PRINT-LEGAL-004 β€” No-surcharge rule: cannot bill the disabled person for alternate formats (MUST; regulation)
  • PRINT-LEGAL-005 β€” Undue-burden / fundamental-alteration defenses and their limits (MAY/context; regulation)
  • PRINT-LEGAL-006 β€” Section 504 reach through federal financial assistance (MUST; statute/regulation)
  • PRINT-LEGAL-007 β€” Section 508 scope ends at electronic content; hardcopy handled by 504/ADA (SHOULD; statute β€” scope note)
  • PRINT-LEGAL-008 β€” ACA Β§1557 disability provisions & effective communication (MUST; regulation β€” 45 CFR 92)
  • PRINT-LEGAL-009 β€” Β§1557 Notice of Availability of language/format assistance (MUST/verify; regulation β€” check post-litigation status of 2024 final rule)
  • PRINT-LEGAL-010 β€” 2024 DOJ Title II web rule increases (not reduces) print exposure β€” dual-regime note (SHOULD; regulation β€” analytical)
  • PRINT-LEGAL-011 β€” NAIC-model insurance policy readability / minimum-type statutes (state layer) (context; state statute β€” jurisdiction-scoped)
  • PRINT-LEGAL-012 β€” Consumer-contract conspicuousness doctrine (UCC / state) (context; statute/common law)
  • PRINT-LEGAL-013 β€” State consent-form formatting mandates, Texas specifically (context; state statute β€” verify TX)
  • PRINT-LEGAL-014 β€” CMS ABN (CMS-R-131) point-size instruction (MUST; agency guidance β€” verify current form instructions)
  • PRINT-LEGAL-015 β€” Medicare Advantage/Part D materials type-size: 42 CFR Β§Β§ 422.2267(a)(1) & 423.2267(a)(1) (MUST; regulation β€” verify current text + carve-outs)
  • PRINT-LEGAL-016 β€” FDA OTC Drug Facts type-size & format, 21 CFR 201.66 (MUST; regulation β€” verify, incl. exclusions)
  • PRINT-LEGAL-017 β€” International scope note: EN 301 549 / AODA / EAA (US-first, non-binding here) (context; standard/foreign law)
  • PRINT-LEGAL-018 β€” Disclaimer: engineering guidance, not legal advice; jurisdiction questions β†’ counsel (informational)
  • PRINT-LEGAL-019 β€” Enforcement, remedies, and penalties for inaccessible hardcopy (informational; statute + regulation + case law β€” added post-v1.0)

01 β€” Typography (PRINT-TYPO)

  • PRINT-TYPO-001 β€” Body text minimum point size (general-audience Clear Print floor) (SHOULD; consensus standard)
  • PRINT-TYPO-002 β€” Caption / secondary text minimum size (SHOULD; consensus)
  • PRINT-TYPO-003 β€” Footnote & legal-disclaimer minimum size (where not statutorily fixed) (SHOULD; consensus)
  • PRINT-TYPO-004 β€” Large-print alternate body size (APH/CCLVI spec, distinct from 001) (SHOULD; consensus standard)
  • PRINT-TYPO-005 β€” Typeface selection; what β€œsans serif” does and does not buy (SHOULD; consensus)
  • PRINT-TYPO-006 β€” Weight / stroke-contrast limits (avoid hairline & ultra-thin) (SHOULD; consensus)
  • PRINT-TYPO-007 β€” Letter-spacing / tracking floor (SHOULD; consensus)
  • PRINT-TYPO-008 β€” Word-spacing constraints (SHOULD; consensus)
  • PRINT-TYPO-009 β€” Leading (line spacing) as a ratio of point size (SHOULD; consensus)
  • PRINT-TYPO-010 β€” Measure / line length in characters (SHOULD; consensus)
  • PRINT-TYPO-011 β€” Avoid justified text & hyphenation (rag-right) (SHOULD; consensus)
  • PRINT-TYPO-012 β€” Avoid all-caps / small-caps for extended text (word-shape) (SHOULD; consensus)
  • PRINT-TYPO-013 β€” Limit italics / underline / reverse-out for body text (SHOULD; consensus)
  • PRINT-TYPO-014 β€” Text over images or tinted panels β€” legibility floor (SHOULD; consensus + contrast link)
  • PRINT-TYPO-015 β€” Orphan/widow control where it harms comprehension (not aesthetics) (MAY; consensus)

02 β€” Color, contrast, and ink (PRINT-COLOR)

  • PRINT-COLOR-001 β€” WCAG sRGB relative-luminance ratio is NOT directly valid on paper (foundational note) (SHOULD; analytical)
  • PRINT-COLOR-002 β€” Defensible print contrast target (reflectance-based) & how to state it (SHOULD; consensus/analytical)
  • PRINT-COLOR-003 β€” Grayscale / monochrome survival: every color rule needs a B&W-printer answer (MUST/SHOULD; derives from WCAG 1.4.1 intent)
  • PRINT-COLOR-004 β€” Color as sole information carrier is prohibited on paper (SHOULD; consensus, WCAG-derived)
  • PRINT-COLOR-005 β€” Colored paper stock constraints (SHOULD; consensus)
  • PRINT-COLOR-006 β€” Watermarks / background tints behind text β€” max density (SHOULD; consensus)
  • PRINT-COLOR-007 β€” Highlight / shading in tables and form fields β€” legibility after print (SHOULD; consensus)
  • PRINT-COLOR-008 β€” Ink/production variability (toner vs inkjet vs offset, dot gain) β€” design margin (SHOULD; industry practice)

03 β€” Layout and structure (PRINT-LAYOUT)

  • PRINT-LAYOUT-001 β€” Single vs multi-column and reading-order breakage on paper (SHOULD; consensus)
  • PRINT-LAYOUT-002 β€” Visual heading hierarchy that survives without tags (size/weight/space/position) (SHOULD; consensus)
  • PRINT-LAYOUT-003 β€” Whitespace & visual grouping of related content (SHOULD; consensus)
  • PRINT-LAYOUT-004 β€” Lists & visually distinct markers (SHOULD; consensus)
  • PRINT-LAYOUT-005 β€” Table header-row repetition across page breaks (SHOULD; consensus)
  • PRINT-LAYOUT-006 β€” Table row/column header association must be visually obvious (SHOULD; consensus)
  • PRINT-LAYOUT-007 β€” Tables too wide for the page β€” handling rules (SHOULD; consensus)
  • PRINT-LAYOUT-008 β€” Figures/captions as the print substitute for alt text (MUST/SHOULD; effective-communication-derived)
  • PRINT-LAYOUT-009 β€” Page numbering & β€œPage X of Y” (SHOULD; consensus)
  • PRINT-LAYOUT-010 β€” Running headers/footers β€” content & consistency (MAY; consensus)
  • PRINT-LAYOUT-011 β€” Section dividers / visual separation (MAY; consensus)
  • PRINT-LAYOUT-012 β€” Margins, gutters, binding allowance (SHOULD; consensus/production)
  • PRINT-LAYOUT-013 β€” Landscape pages in a stapled packet β€” rotation hazard (SHOULD; consensus)

04 β€” Forms (PRINT-FORM) β€” flagship

  • PRINT-FORM-001 β€” Fill-space minimum height for hand completion (SHOULD; consensus β€” verify any codified min)
  • PRINT-FORM-002 β€” Fill-space minimum width for hand completion (SHOULD; consensus)
  • PRINT-FORM-003 β€” Extra allowance for tremor / low dexterity / large handwriting (SHOULD; consensus)
  • PRINT-FORM-004 β€” Comb / boxed character-cell / gridded date fields are hostile β€” avoid (SHOULD; consensus)
  • PRINT-FORM-005 β€” Checkbox minimum physical dimensions (SHOULD; consensus β€” link to 44px/target norms)
  • PRINT-FORM-006 β€” Radio-button minimum dimensions (SHOULD; consensus)
  • PRINT-FORM-007 β€” Spacing between adjacent selectable targets (SHOULD; consensus)
  • PRINT-FORM-008 β€” Visual label-to-control relationship for check/radio (SHOULD; consensus)
  • PRINT-FORM-009 β€” Signature block line length & clear space (SHOULD; consensus)
  • PRINT-FORM-010 β€” Date block sizing (non-comb) (SHOULD; consensus)
  • PRINT-FORM-011 β€” Signature line not adjacent to dense fine print (consent validity) (SHOULD; consensus + legal)
  • PRINT-FORM-012 β€” Label placement/proximity (above vs beside) & wrap/column/page-break behavior (SHOULD; consensus)
  • PRINT-FORM-013 β€” Instructions & format hints appear BEFORE the field, never after (SHOULD; consensus)
  • PRINT-FORM-014 β€” Required-field indication not reliant on color alone (SHOULD; WCAG-derived)
  • PRINT-FORM-015 β€” Required-field indication not reliant on asterisk-only or top-of-form legend on multi-page forms (SHOULD; consensus)
  • PRINT-FORM-016 β€” Validation/error messages have no print analogue β†’ must be static instructional text (SHOULD; analytical)
  • PRINT-FORM-017 β€” Tooltips / placeholder / field descriptions don’t print β€” enumerate lost metadata + visual substitute (SHOULD; analytical)
  • PRINT-FORM-018 β€” Reading/completion order on paper vs AcroForm tab order divergence (SHOULD; consensus)
  • PRINT-FORM-019 β€” Page breaks inside a field group / question-answer pair (SHOULD; consensus)
  • PRINT-FORM-020 β€” Duplex hazards: reverse-side fields missed, show-through, signature on the back (SHOULD; consensus/production)
  • PRINT-FORM-021 β€” Detachable / return sections, tear-off strips, mail-back panels (MAY; consensus)
  • PRINT-FORM-022 β€” Alternate-format request notice ON the form (content/placement/size) (MUST/SHOULD; effective-communication-derived)
  • PRINT-FORM-023 β€” docxβ†’AcroForm marker-insertion: field-geometry validation before emitting a widget (SHOULD; our-implementation rule)
  • PRINT-FORM-024 β€” docxβ†’AcroForm: refuse/flag conditions (sub-minimum geometry, comb, color-only required) (SHOULD; our-implementation rule)

05 β€” Substrate and production (PRINT-SUBSTRATE)

  • PRINT-SUBSTRATE-001 β€” Paper weight / opacity threshold to control show-through (SHOULD; industry practice)
  • PRINT-SUBSTRATE-002 β€” Finish: matte vs gloss & glare for low-vision readers (SHOULD; consensus)
  • PRINT-SUBSTRATE-003 β€” Paper color & brightness (SHOULD; consensus)
  • PRINT-SUBSTRATE-004 β€” Duplex rules for readability & fidelity (SHOULD; consensus)
  • PRINT-SUBSTRATE-005 β€” Stapling / binding / hole-punch encroachment on the text block (SHOULD; production)
  • PRINT-SUBSTRATE-006 β€” Booklet imposition & reading-order impact (SHOULD; production)
  • PRINT-SUBSTRATE-007 β€” Letter/A4 page-size scaling trap (SHOULD; production)
  • PRINT-SUBSTRATE-008 β€” Print-at-100%: shrink-to-fit / fit-to-printable invalidates point-size rules β€” HARD requirement + resistance measures (MUST-for-our-output; analytical/our-rule)
  • PRINT-SUBSTRATE-009 β€” N-up / multi-up scaling caution (SHOULD; production)
  • PRINT-SUBSTRATE-010 β€” Bleed & safe areas (MAY; production)

06 β€” Alternate formats (PRINT-ALT)

  • PRINT-ALT-001 β€” Large-print production spec: size/typeface/leading/measure/page-size (SHOULD; consensus standard β€” APH)
  • PRINT-ALT-002 β€” Reflow vs enlargement; photocopy-enlargement does NOT conform (SHOULD; consensus)
  • PRINT-ALT-003 β€” Braille: contracted vs uncontracted, embossing standards, triggers (context; consensus standard)
  • PRINT-ALT-004 β€” Tactile-graphics problem (images β†’ touch) (context; consensus)
  • PRINT-ALT-005 β€” Audio & structured audio alternates (context; consensus)
  • PRINT-ALT-006 β€” Electronic alternates as auxiliary aid & their limits (SHOULD; regulation-derived)
  • PRINT-ALT-007 β€” Qualified readers as an auxiliary aid (context; regulation)
  • PRINT-ALT-008 β€” β€œTimely manner” turnaround expectations (SHOULD; regulation-derived)
  • PRINT-ALT-009 β€” Request-notice text: required content, placement, no-surcharge (MUST/SHOULD; regulation-derived)
  • PRINT-ALT-010 β€” Recommended default request-notice string our products can emit (SHOULD; our-implementation)

07 β€” Plain language (PRINT-LANG)

  • PRINT-LANG-001 β€” Reading-level target & honest measurement (Flesch-Kincaid limits) (SHOULD; consensus/guidance)
  • PRINT-LANG-002 β€” Sentence & paragraph length (SHOULD; consensus)
  • PRINT-LANG-003 β€” Terminology, abbreviations, first-use expansion (SHOULD; consensus)
  • PRINT-LANG-004 β€” Numbers, dates, units formatting (SHOULD; consensus)
  • PRINT-LANG-005 β€” Instructions written as imperatives (SHOULD; consensus)
  • PRINT-LANG-006 β€” Cognitive accessibility is disproportionately a print problem (no zoom/read-aloud/lookup) (SHOULD; analytical)

08 β€” Digital-to-print fidelity (PRINT-FIDELITY)

  • PRINT-FIDELITY-001 β€” Affordanceβ†’print-fate inventory table (survives/lost/degraded + required visual compensation) (SHOULD; analytical β€” the core table)
  • PRINT-FIDELITY-002 β€” Print-safe profile: combined-conformance constraint set (MUST-for-our-output; our-rule)
  • PRINT-FIDELITY-003 β€” Two-regime conflict resolution rule (documented, not left to implementer) (SHOULD; our-rule)
  • PRINT-FIDELITY-004 β€” URL/hyperlink handling: when/how to surface destinations on paper (SHOULD; consensus)
  • PRINT-FIDELITY-005 β€” Long-description handling on paper (charts/complex images) (SHOULD; effective-communication-derived)
  • PRINT-FIDELITY-006 β€” MathML β†’ print (visual equation + no spoken-math on paper) (SHOULD; analytical)

09 β€” Validation (PRINT-VALID)

  • PRINT-VALID-001 β€” Bucket taxonomy: automatable / assistable / human-only (informational/framework)
  • PRINT-VALID-002 β€” Automatable measurement methods & units (point size, geometry, contrast, margins, measure, page-size) (SHOULD; our-rule)
  • PRINT-VALID-003 β€” Assistable checks: tool flags candidates for human judgment (SHOULD; our-rule)
  • PRINT-VALID-004 β€” Human-only checks (hand-fill usability, real-lighting glare, comprehension) (SHOULD; our-rule)
  • PRINT-VALID-005 β€” Physical-print verification procedure (what to print, on what, what to check) (SHOULD; our-rule)
  • PRINT-VALID-006 β€” Audit-tooling extensibility map: what our pipeline can/can’t cover structurally (informational; our-rule)

Open questions for review

  1. Scope/positioning (per the strategy discussion): build as internal print-safe guardrail + KB, or also stand up sellable print-compliance validation? Affects how much PRINT-VALID tooling detail I write.
  2. Should state-law entries (LEGAL-011..013) stay in scope for a US-first v1, or move to a separate appendix to keep the core defensible and lean?
  3. Braille/audio (ALT-003..005): full requirements, or scope to β€œwhen triggered + hand off to specialist vendor” pointers? We don’t produce these today.
  4. Any IDs you want renamed/removed now β€” they’re permanent after approval.