Gutenburg uses a proprietary PDF generation engine to create the technical PDF structure required for accessible output while the document is generated inside Salesforce. The engine is the foundation for Gutenburg’s PDF/UA-1 and PDF/UA-2 output capabilities and for automating accessibility work that would otherwise require downstream PDF remediation.
Accessibility is split between the engine and the template
The PDF engine handles the machine-level document-generation work that must exist in the final PDF. The template author controls meaning-dependent choices that software cannot reliably infer, such as whether visual contrast is appropriate and whether alternative text accurately describes an image.
Supported accessible output
- PDF/UA-1 compliant output
- PDF/UA-2 compliant output
- WCAG 2.1 AA-oriented document workflows
- Accessibility features exposed directly in Template Builder, including image alternative text, actual text, font embedding, and preview/testing controls
Release accessibility QA
Generated output is checked against five independent third-party accessibility checking tools with each Gutenburg release. The documented examples include Adobe tooling and octopdf.com. A VPAT is available upon request for organizations evaluating Gutenburg.
Accessibility without an external rendering service
Gutenburg performs document generation inside Salesforce rather than sending customer data to a separate document-rendering service. The same native architecture used for security and data residency also applies to accessible document generation.