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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.carina
1 +XWiki.anna
Content
... ... @@ -33,29 +33,8 @@
33 33  {{/column}}
34 34  {{/section}}
35 35  
36 +== How do I structure content? ==
36 36  
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, 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.
40 -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.
41 -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:
42 - create a course-specific accessibility statement,
43 - identify potential barriers in texts, media and interactive content,
44 - provide support for the accessible design of teaching materials.
45 -
46 -
47 -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.
48 -
49 -{{panel title="Further information"}}
50 -* 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]]
51 -* 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]]
52 -{{/panel}}
53 -
54 -
55 -== Tips for designing content ==
56 -
57 -=== How do I structure content? ===
58 -
59 59  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.
60 60  
61 61  {{info}}
... ... @@ -229,11 +229,8 @@
229 229  * [[HTML als Auszeichnungssprache / Semantik (SELFHTML-Wiki)>>https://wiki.selfhtml.org/wiki/HTML/Tutorials/Entstehung_und_Entwicklung#HTML_als_Auszeichnungssprache||shape="rect"]]
230 230  {{/panel}}
231 231  
232 -(% class="wikigeneratedid" %)
211 +== How can texts be made easy to read? ==
233 233  
234 -
235 -=== How can texts be made easy to read? ===
236 -
237 237  Font, font size, character and word spacing, line length and many other factors influence the readability of texts.
238 238  
239 239  * Make sure to use **common fonts** (like Arial) and avoid fancy or hard-to-read ones.
... ... @@ -253,9 +253,8 @@
253 253  {{/panel}}
254 254  
255 255  
232 +== How should links be set? ==
256 256  
257 -=== How should links be set? ===
258 -
259 259  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.
260 260  
261 261  {{info}}
... ... @@ -263,14 +263,13 @@
263 263  {{/info}}
264 264  
265 265  
241 +== What should be considered when using media? ==
266 266  
267 -=== What should be considered when using media? ===
268 -
269 269  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.
270 270  
271 271  Here are some tips you might find useful regarding accessibility and mobile compatibility.
272 272  
273 -==== File size ====
247 +=== File size ===
274 274  
275 275  * For photos, JPEG format should be preferred and medium to high quality should be selected depending on the image content.
276 276  * Images should not exceed a file size of 100-200kB.
... ... @@ -281,7 +281,7 @@
281 281  Common image editing programmes and online tools can help to compress images without any visible loss of quality.
282 282  {{/info}}
283 283  
284 -==== Captions ====
258 +=== Captions ===
285 285  
286 286  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.
287 287  
... ... @@ -296,11 +296,8 @@
296 296  </figure>
297 297  {{/code}}
298 298  
299 -(% class="wikigeneratedid" %)
273 +=== Alternative text (alt text) ===
300 300  
301 -
302 -==== Alternative text (alt text) ====
303 -
304 304  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.
305 305  
306 306  **The following should be kept in mind when providing alt text for images:**
... ... @@ -314,18 +314,18 @@
314 314  {{/info}}
315 315  
316 316  
317 -===== How to store alternative text in the Tiny MCE text editor =====
288 +==== How to store alternative text in the Tiny MCE text editor ====
318 318  
319 319  [[image:Texteditor-Bilder-Alternativtext.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
320 320  
321 321  
322 -===== HTML code for alt text =====
293 +==== HTML code for alt text ====
323 323  
324 324  {{code}}
325 325  <img ... alt="Der Schaum auf einem Kaffee bildet ein schreiendes Gesicht." />
326 326  {{/code}}
327 327  
328 -===== How to mark an image as decorative =====
299 +==== How to mark an image as decorative ====
329 329  
330 330  [[image:Texteditor-Bilder-dekorativ.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" height="224" width="300"]]
331 331  
... ... @@ -346,9 +346,6 @@
346 346  * [[Five golden rules for compliant alt text>>url:https://abilitynet.org.uk/news-blogs/five-golden-rules-compliant-alt-text||shape="rect"]]
347 347  {{/panel}}
348 348  
349 -(% class="wikigeneratedid" %)
350 -
351 -
352 352  === Optimizing images for smartphones and tablets ===
353 353  
354 354  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.
... ... @@ -359,9 +359,6 @@
359 359   <img src="..." style="max-width: 100%" />
360 360  {{/code}}
361 361  
362 -(% class="wikigeneratedid" %)
363 -
364 -
365 365  === Providing alternatives for videos and audio files ===
366 366  
367 367  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.
... ... @@ -379,7 +379,6 @@
379 379  {{/panel}}
380 380  
381 381  
382 -
383 383  == Colours & contrasts ==
384 384  
385 385  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"]]).