Skip to Content
Last modified by Carina Enke on 20.02.2026
From version 15.1
edited by Anna Paul-Hasenfuss
on 19.06.2025
Change comment: There is no comment for this version
To version 17.1
edited by Carina Enke
on 20.02.2026
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.anna
1 +XWiki.carina
Content
... ... @@ -33,6 +33,26 @@
33 33  {{/column}}
34 34  {{/section}}
35 35  
36 +== ==
37 +
38 +== Course-related accessibility statement ==
39 +
40 +Public bodies, including state universities and schools, are legally obliged to produce an accessibility statement for their digital offerings. This statement describes the extent to which accessibility requirements are met and, where applicable, identifies areas that are not accessible. Further information can be found on the official website for the accessibility statement for web and app applications of the Federal Government, accessible via the link https:~/~/www.barrierefreiheit-dienstekonsolidierung.bund.de/Webs/PB/DE/ barrierefreie_it/uebergreifende-anforderungen-web-und-app/erklaerung-zur-barrierefreiheit/erklaerung-zur-barrierefreiheit-node.html.
41 +A declaration at the software level covers the functions of the learning platform, but not the content of individual courses. However, since an OPAL course consists mainly of learning materials for which the course coordinators are responsible, it makes sense to provide a course-related accessibility statement.
42 +To make it easier for teachers to create such a statement, TU Dresden provides the LMS Check Generator for accessibility. The tool enables course administrators to:
43 + create a course-specific accessibility statement,
44 + identify potential barriers in texts, media and interactive content,
45 + provide support for the accessible design of teaching materials.
46 +
47 +
48 +The tool guides you step by step through the creation of the declaration. The person responsible selects the course modules used in the course and then receives a checklist for the content. The generated declaration is provided as an accessible HTML file and can be embedded in the course as a page using the ‘Single Page’ course module. This means that the declaration is directly available in the course and easy for learners to find.
49 +
50 +{{panel title="Further information"}}
51 +* LMS Check Generator tool for accessibility from TU Dresden: [[https:~~/~~/lms-check.inf.tu-dresden.de/checklist?lang=en>>url:https://lms-check.inf.tu-dresden.de/checklist?lang=en]]
52 +* Federal government information on accessibility declarations for web and app applications: [[https:~~/~~/www.barrierefreiheit-dienstekonsolidierung.bund.de/Webs/PB/DE/barrierefreie_it>>https://www.barrierefreiheit-dienstekonsolidierung.bund.de/Webs/PB/DE/barrierefreie_it/uebergreifende-anforderungen-web-und-app/erklaerung-zur-barrierefreiheit/erklaerung-zur-barrierefreiheit-node.html]]
53 +{{/panel}}
54 +
55 +
36 36  == How do I structure content? ==
37 37  
38 38  When structuring texts on websites or in documents, it makes sense to use books or articles as a guideline. The headlines, bulleted lists, table of contents and visual highlighting used there help to improve readability, skimming or scanning with the eyes, and, therefore, make it easier to find relevant information quickly. These elements also help users to find their way around the site. In addition to visual structuring through design, technically correct structuring by means of suitable HTML elements is also necessary. This is particularly relevant for accessibility, as screen readers and other assistive technologies transmit information based on HTML code and provide various functions.
... ... @@ -136,10 +136,14 @@
136 136  
137 137  In the Tiny MCE text editor, you can activate the table caption in the **table properties**. When you do this, some text will appear above the table, which you can change to match your content.
138 138  
159 +===== =====
160 +
139 139  ===== **How to activate table captions in the Tiny MCE text editor** =====
140 140  
141 141  [[image:Texteditor-Tabellen-Beschriftung_de.png||alt="Beschriftung für Tabellen aktivieren im Dialog Tabelleneigenschaften im Texteditor (Screenshot)" data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
142 142  
165 +===== =====
166 +
143 143  ===== **HTML code for captions** =====
144 144  
145 145  {{code language="html" layout="LINENUMBERS"}}
... ... @@ -201,7 +201,7 @@
201 201  
202 202  {{panel title="Further information"}}
203 203  * [[Steps towards an inclusive communication design (legibility.info)>>url:https://www.leserlich.info/||shape="rect"]]
204 -* [[HTML als Auszeichnungssprache / Semantik (SELFHTML-Wiki)>>url:https://wiki.selfhtml.org/wiki/HTML/Tutorials/HTML5/Entstehung_und_Entwicklung#HTML_als_Auszeichnungssprache||shape="rect"]]
228 +* [[HTML als Auszeichnungssprache / Semantik (SELFHTML-Wiki)>>https://wiki.selfhtml.org/wiki/HTML/Tutorials/Entstehung_und_Entwicklung#HTML_als_Auszeichnungssprache||shape="rect"]]
205 205  {{/panel}}
206 206  
207 207  == How can texts be made easy to read? ==
... ... @@ -286,7 +286,7 @@
286 286  [[image:Texteditor-Bilder-Alternativtext.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
287 287  
288 288  
289 -==== HTML code for alternative text ====
313 +==== HTML code for alt text ====
290 290  
291 291  {{code}}
292 292  <img ... alt="Der Schaum auf einem Kaffee bildet ein schreiendes Gesicht." />