Gutenburg automates technical accessibility work in the generated PDF, but accessibility also depends on decisions made while the template is authored. The boundary is straightforward: the engine can automate structure and output behavior; the author must supply meaning and make visual decisions that require context.
Engine-level responsibilities
The proprietary PDF engine is responsible for creating the supported technical accessibility structure in the final PDF and for producing PDF/UA-capable output as part of generation.
Author-level responsibilities
- Choose colors and visual combinations with appropriate contrast.
- Provide meaningful alternative text for images when the image carries information.
- Provide actual text when an image contains text that should be represented verbatim.
- Write and organize content so the document communicates clearly.
- Use the Template Builder controls intentionally when accessibility metadata requires human meaning.
Template Builder exposes accessibility controls
The product tour shows explicit fields for image alternative text and actual text, as well as a document setting for embedding fonts. These controls let the author supply information that the engine then carries into the generated PDF workflow.