Accessible Documents
Table of contents
In addition to TU Dresden websites themselves, all files (e.g. Word or PDF documents) embedded there must also be accessible for people with disabilities, effective immediately. Documents published prior to September 23, 2018, that are not required for active administrative procedures are exempt from this regulation. Although there is no requirement to subsequently design them so they are accessible for people with disabilities, it is highly recommended that you try to optimize them as well.
Of course, you will not be able to revise all affected documents right away, but you should at least make sure that newly uploaded files are accessible for people with disabilities. Gradually, you should then also try to make especially important documents accessible. Until then, all files that do not meet accessibility standards should be labeled accordingly, e.g. “Document X (PDF, not accessible).”
Creating accessible documents
The basis of an accessible document is the use of style sheets (in Word) or predefined slide layouts (in PowerPoint). It is best to use the corporate design templates of TU Dresden, as these already take into account the basic aspects of accessibility and thus relieve you of some of the work. On the Services Disability and Studies Group (AG SBS) website, you will find corresponding instructions for creating accessible PDFs from Word or PowerPoint. In addition, the Services Disability and Studies Group also regularly offers advanced training on the topic of “Creating Accessible Documents.”
Essentially, you should pay attention to the following aspects, among others. The content of your documents should always be structured by the elements provided for this purpose, i.e. in particular headings, lists and tables. In addition, for all non-text elements (e.g. images and graphics), you must provide an alternative text. Since the detailed description of images is very time-consuming, especially in visually influenced presentations, brief information about the general content is sufficient at first. However, a detailed description must be prepared at the latest in the specific case of need. In the practical guide for creating text-based alternatives for graphics (in German), you will find helpful tips for describing images for people with visual impairments. In addition, you are also welcome to contact the Services Disability and Studies Group for help.
Checking accessibility
Before you create a PDF from your source file (Word or PowerPoint), you should first check accessibility. Since Office 2010, for example, you can perform a check as follows: “File” tab – “Information”– “Check for problems” – “Check accessibility.” Only after fixing the problems in the source file should you export to a PDF, otherwise extensive post-processing will be necessary. You will also find further instructions in the already mentioned Instructions from the Services Disability and Studies Group.
The accessibility of PDF files can be checked with the help of the PAC tool. You can then use the Adobe Acrobat Pro and axesPDF QuickFix program for correction. To export from Word, it is best to use the axesPDF for Word program, as it provides the best export results and in many cases can already generate accessible PDF documents. The mentioned tools can be found on the virtual desktop of the Services Disability and Studies Group (terminal). For access, you can contact Mr. Jens Voegler (, Tel. +49 351 463 42024).
Correction of typical PDF/UA problems
The standard to be achieved for accessible PDF documents is called PDF/UA (universal accessibility). The above-mentioned tools PAC and axesPDF QuickFix check accessibility according to this standard. The following overview is intended to help you resolve any issues you may find to ensure that your document is PDF/UA compliant. Please note that many of the links provided are only available in German.
Review step |
Barrier/Issue |
Solution |
Font embedding |
Font is not embedded |
Adobe Acrobat: Preflight tool > Embed fonts |
Structure tree |
Structure element “Sect” used as base element |
Adobe Acrobat: New create root tag of type “document,” all other tags as sub-divisions thereof |
Structure tree |
Possible inappropriate use of the structural element “Figure” |
axesPDF QuickFix: Logical structure > Correct placement |
Alternative descriptions |
Note without alternative description |
axesPDF QuickFix: Extras > Fill contents entry from link annotations |
Metadata |
No PDF/UA marking |
axesPDF QuickFix: Extras > Add PDF/UA identifier |
Document settings |
“DisplayDocTitle” entry is not set |
axesPDF QuickFix: “Settings” task area > “Standards” tab |
An overview of other possible issues in PDF files and how to fix them can be found here: