Feature Wiki

Information about planned and released features

Tabs

Render Accessible PDFs

1 Initial Problem

PDFs generated of ILIAS objects are not accessible: Unfortunately they do not inherit semantic information (Headline etc.) and they do include a lot of special characters that are not displayed but only presented to the screenreader (think $%   _$"...).

2 Conceptual Summary

The PDFs rendered in ILIAS need to carry over the semantic information from the style. 
The PDFs must not include wiered special characters. 
The PDFs must carry over alt-texts.

3 User Interface Modifications

3.1 List of Affected Views

  • PDF of Wiki 
  • PDF of Learning Module
  • PDF of Course Member List

3.2 User Interface Details

None

3.3 New User Interface Concepts

None.

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Privacy Information

No personal data will need to be stored or processed to implement this feature. 

6 Security Implications

We do not see any special security relevant changes.

7 Contact

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

9 Discussion

Schmidt-Sielex, Wolfgang [WSS] 2023-07-20: Feature has been discussed by a sub-group of SIG accessibility and pushed to 'suggested for 10'.
Some PDF functions in ILIAS have already been changed to browser generated PDF (responsibility for accessibility is then no longer in ILIAS), but some content is still rendered in ILIAS functions. If the PDF creation stays within ILIAS this request needs a detailed concept and takes time to make sure ILIAS produces an accessible output. See e.g. BITV criteria 11.8.3: "Erhaltung von Barrierefreiheitsinformationen bei Transformation". Wherever we keep a transformation tool within ILIAS to create a PDF file from HTML content we must transfer all accessibility related structures and information of the web content to the PDF (e.g. structure of headings, alt-texts, accessible table structures, aria-labels and so on). Additionally we need to ensure that all general PDF properties regarding accessibility will be implemented in the transformation process.

10 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

  • {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.

Last edited: 20. Jul 2023, 11:28, Schmidt-Sielex, Wolfgang [WSS]