Accessibility & Archiving (WCAG / PDF-A)
Compliance without technical headaches
Not merely “looks right”, but demonstrably readable, navigable and archivable.
In a traditional software project, the database, code, and output (PDF/Word) are separate islands. If you change a field, you have to make adjustments in five places. Forget one? Then you have a bug or a document that doesn't meet requirements.
The Compliance Challenge
Legislation such as WCAG (digital accessibility) and archiving requirements (PDF/A) demand technical perfection. An "approximately good" PDF file can have legal consequences or be unreadable for people with disabilities. Manual checking is an impossible task.
The Solution: Automatic Perfection
We reverse the process with Model-Driven Development. Because we generate everything from one central source, we guarantee that the output always complies with the rules.
- Always Compliant: WCAG and PDF/A standards are baked into the generator.
- No Manual Work: The computer doesn't make mistakes.
- Future-proof: Does the law change? We update the generator and all your output is up to date again.
Read more about our technical approach: From Source to Result
Our Expertise
- WCAG 2.1 / 2.2: We ensure your digital content is accessible to everyone.
- PDF/UA: Universal Accessibility in PDF documents.
- PDF/A-1a: Long-term archiving according to the strictest standards.
- Validation: Automated checks guarantee compliance.
Does your publishing pipeline use RenderX XEP?
Accessibility then requires more than a validator at the end of the process. First determine which changes are needed in the source, XSLT, XSL-FO, formatter and fonts for a controlled migration to Apache FOP.
Where does the output lose its accessibility?
Have one representative source and publication examined side by side, including the boundary of the evidence.