Skip to Content
Last modified by Carina Enke on 20.02.2026
From version 16.1
edited by Anna Paul-Hasenfuss
on 19.06.2025
Change comment: There is no comment for this version
To version 19.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,8 +33,34 @@
33 33  {{/column}}
34 34  {{/section}}
35 35  
36 -== How do I structure content? ==
37 37  
37 +== Course-related accessibility statement ==
38 +
39 +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.
40 +
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 +
43 +
44 +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:
45 +
46 +* create a course-specific accessibility statement,
47 +* identify potential barriers in texts, media and interactive content,
48 +* provide support for the accessible design of teaching materials.
49 +
50 +
51 +
52 +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.
53 +
54 +{{panel title="Further information"}}
55 +* 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]]
56 +* 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]]
57 +{{/panel}}
58 +
59 +
60 +== Tips for designing content ==
61 +
62 +=== How do I structure content? ===
63 +
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.
39 39  
40 40  {{info}}
... ... @@ -208,8 +208,10 @@
208 208  * [[HTML als Auszeichnungssprache / Semantik (SELFHTML-Wiki)>>https://wiki.selfhtml.org/wiki/HTML/Tutorials/Entstehung_und_Entwicklung#HTML_als_Auszeichnungssprache||shape="rect"]]
209 209  {{/panel}}
210 210  
211 -== How can texts be made easy to read? ==
212 212  
238 +
239 +=== How can texts be made easy to read? ===
240 +
213 213  Font, font size, character and word spacing, line length and many other factors influence the readability of texts.
214 214  
215 215  * Make sure to use **common fonts** (like Arial) and avoid fancy or hard-to-read ones.
... ... @@ -229,8 +229,9 @@
229 229  {{/panel}}
230 230  
231 231  
232 -== How should links be set? ==
233 233  
261 +=== How should links be set? ===
262 +
234 234  Links need meaningful titles and should describe the purpose or destination of the link. Ambiguous link texts such as ‘more’, “here” or ‘read more’ should be avoided. Relevant information about the format or size of a file (e.g. for a download link) should also be included in the linked text.
235 235  
236 236  {{info}}
... ... @@ -238,13 +238,14 @@
238 238  {{/info}}
239 239  
240 240  
241 -== What should be considered when using media? ==
242 242  
271 +=== What should be considered when using media? ===
272 +
243 243  When using media, consider not only storage consumption and loading times, but also its accessibility on the go, e.g. on a smartphone with a poor internet connection. Ensure that information is always available via a second channel, such as text.
244 244  
245 245  Here are some tips you might find useful regarding accessibility and mobile compatibility.
246 246  
247 -=== File size ===
277 +==== File size ====
248 248  
249 249  * For photos, JPEG format should be preferred and medium to high quality should be selected depending on the image content.
250 250  * Images should not exceed a file size of 100-200kB.
... ... @@ -255,7 +255,7 @@
255 255  Common image editing programmes and online tools can help to compress images without any visible loss of quality.
256 256  {{/info}}
257 257  
258 -=== Captions ===
288 +==== Captions ====
259 259  
260 260  Captions or titles provide additional information about images. A title is necessary if important information about the image needs to be conveyed. Unlike image descriptions (alternative text), titles are also accessible to sighted users.
261 261  
... ... @@ -270,8 +270,10 @@
270 270  </figure>
271 271  {{/code}}
272 272  
273 -=== Alternative text (alt text) ===
274 274  
304 +
305 +==== Alternative text (alt text) ====
306 +
275 275  You should always provide alternative text for images that are relevant to the content of a page. Alt text is read out by screen readers and, therefore, accessible to blind people. Even if the images on the page are disabled or cannot be loaded due to a slow internet connection, the information can still be conveyed despite the missing image.
276 276  
277 277  **The following should be kept in mind when providing alt text for images:**
... ... @@ -285,18 +285,18 @@
285 285  {{/info}}
286 286  
287 287  
288 -==== How to store alternative text in the Tiny MCE text editor ====
320 +===== How to store alternative text in the Tiny MCE text editor =====
289 289  
290 290  [[image:Texteditor-Bilder-Alternativtext.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
291 291  
292 292  
293 -==== HTML code for alt text ====
325 +===== HTML code for alt text =====
294 294  
295 295  {{code}}
296 296  <img ... alt="Der Schaum auf einem Kaffee bildet ein schreiendes Gesicht." />
297 297  {{/code}}
298 298  
299 -==== How to mark an image as decorative ====
331 +===== How to mark an image as decorative =====
300 300  
301 301  [[image:Texteditor-Bilder-dekorativ.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" height="224" width="300"]]
302 302  
... ... @@ -317,6 +317,8 @@
317 317  * [[Five golden rules for compliant alt text>>url:https://abilitynet.org.uk/news-blogs/five-golden-rules-compliant-alt-text||shape="rect"]]
318 318  {{/panel}}
319 319  
352 +
353 +
320 320  === Optimizing images for smartphones and tablets ===
321 321  
322 322  For images to be displayed in full on small-screen devices and without users having to scroll horizontally, the maximum width in HTML should be limited to 100%. This ensures that the image is only displayed in the selected size until it is wider than the available space on the screen.
... ... @@ -327,6 +327,8 @@
327 327   <img src="..." style="max-width: 100%" />
328 328  {{/code}}
329 329  
364 +
365 +
330 330  === Providing alternatives for videos and audio files ===
331 331  
332 332  When using media, make sure to always offer the info in an alternative format. In addition to image descriptions (alternative text) for images, think about pure audio content (e.g. podcasts) and video content with images and sound.
... ... @@ -344,6 +344,7 @@
344 344  {{/panel}}
345 345  
346 346  
383 +
347 347  == Colours & contrasts ==
348 348  
349 349  When selecting colours, make sure there is **sufficient contrast between the background and text colours.** Black on white generally offers the best **contrast ratio**, which should be at least** 4.5:1 **([[WCAG 2.1 - Contrast>>url:https://www.w3.org/TR/WCAG21/#contrast-minimum||shape="rect"]]).