Public-sector and regulated buyers increasingly require that generated documents be readable by assistive technology. This release turns the report engine's accessibility mode on and makes its output validate as PDF/UA-1.
What changed in the output
- Tagged PDF The renderer runs with accessibility enabled and the PDF/UA mode set, so the document carries the structure tree a screen reader navigates.
- A document language The report model sets the language on the root element, English by default, which the validator demanded for text and for every image's alternate text.
- Declared metadata and alternate text A declarations block is emitted, and every external graphic carries alternate text.
- A switch in the report configuration Accessibility is a report-level option, so existing output is unchanged until a report asks for it. A test renders and checks a PDF/UA document.
Type for right-to-left scripts
- Noto Sans Arabic ships with the document service in six weights, from extra-light to black, so Arabic reports render without a font installed on the host.
Accessibility in the output is cheaper than retrofitting it in a document archive. The switch is one attribute on the report.