darrenwashereQ: Accessibility?
Are the generated PDFs accessible? Do they feature proper tag structures, alt text, and headings, in compliance with PDF/UA standards? With the recent DOJ Rule on accessibility, this has become a vital concern for numerous organizations.
togedir
Oct 28, 2025A: Sorry for the late response 👋
Yes—MarkupGo now exposes a pdfUA option (“Enable PDF for Universal Access for optimal accessibility”). It’s off by default; you can enable it in the PDF options when generating from URL/HTML/Template/Markdown.
Important clarifications
• Enabling pdfUA improves structure for accessibility, but we do not guarantee full, audited PDF/UA compliance yet (e.g., DOJ rule requirements).
• Real-world compliance still depends on your source HTML: use proper heading hierarchy, landmarks, table semantics, and meaningful alt text on images.
• Validate outputs with an external checker (e.g., PAC/Acrobat Preflight). For strict conformance, plan a post-processing/remediation step.
Relevant limitations from our PDF engine
• Headers/footers are HTML but run with restrictions (no JS; assets not loaded; fonts must be available in the container; images must be base64; colors may require -webkit-print-color-adjust: exact).
• There’s a known issue with singlePage: true (height calculation) noted in the docs—avoid pairing that mode with accessibility-critical outputs until the fix is released.
Please check our do
https://markupgo.com/docs/api/pdf