Changes for page Erstellung barrierefreier Inhalte
Last modified by Carina Enke on 20.02.2026
From version 19.1
edited by Carina Enke
on 20.02.2026
on 20.02.2026
Change comment:
There is no comment for this version
To version 17.1
edited by Carina Enke
on 20.02.2026
on 20.02.2026
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -33,22 +33,18 @@ 33 33 {{/column}} 34 34 {{/section}} 35 35 36 +== == 36 36 37 37 == Course-related accessibility statement == 38 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 - 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 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 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: 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. 45 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 49 50 - 51 - 52 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 53 54 54 {{panel title="Further information"}} ... ... @@ -57,10 +57,8 @@ 57 57 {{/panel}} 58 58 59 59 60 -== Tips fordesigningcontent ==56 +== How do I structure content? == 61 61 62 -=== How do I structure content? === 63 - 64 64 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. 65 65 66 66 {{info}} ... ... @@ -234,10 +234,8 @@ 234 234 * [[HTML als Auszeichnungssprache / Semantik (SELFHTML-Wiki)>>https://wiki.selfhtml.org/wiki/HTML/Tutorials/Entstehung_und_Entwicklung#HTML_als_Auszeichnungssprache||shape="rect"]] 235 235 {{/panel}} 236 236 231 +== How can texts be made easy to read? == 237 237 238 - 239 -=== How can texts be made easy to read? === 240 - 241 241 Font, font size, character and word spacing, line length and many other factors influence the readability of texts. 242 242 243 243 * Make sure to use **common fonts** (like Arial) and avoid fancy or hard-to-read ones. ... ... @@ -257,9 +257,8 @@ 257 257 {{/panel}} 258 258 259 259 252 +== How should links be set? == 260 260 261 -=== How should links be set? === 262 - 263 263 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. 264 264 265 265 {{info}} ... ... @@ -267,14 +267,13 @@ 267 267 {{/info}} 268 268 269 269 261 +== What should be considered when using media? == 270 270 271 -=== What should be considered when using media? === 272 - 273 273 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. 274 274 275 275 Here are some tips you might find useful regarding accessibility and mobile compatibility. 276 276 277 -=== =File size ====267 +=== File size === 278 278 279 279 * For photos, JPEG format should be preferred and medium to high quality should be selected depending on the image content. 280 280 * Images should not exceed a file size of 100-200kB. ... ... @@ -285,7 +285,7 @@ 285 285 Common image editing programmes and online tools can help to compress images without any visible loss of quality. 286 286 {{/info}} 287 287 288 -=== =Captions ====278 +=== Captions === 289 289 290 290 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. 291 291 ... ... @@ -300,10 +300,8 @@ 300 300 </figure> 301 301 {{/code}} 302 302 293 +=== Alternative text (alt text) === 303 303 304 - 305 -==== Alternative text (alt text) ==== 306 - 307 307 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. 308 308 309 309 **The following should be kept in mind when providing alt text for images:** ... ... @@ -317,18 +317,18 @@ 317 317 {{/info}} 318 318 319 319 320 -==== =How to store alternative text in the Tiny MCE text editor =====308 +==== How to store alternative text in the Tiny MCE text editor ==== 321 321 322 322 [[image:Texteditor-Bilder-Alternativtext.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]] 323 323 324 324 325 -==== =HTML code for alt text =====313 +==== HTML code for alt text ==== 326 326 327 327 {{code}} 328 328 <img ... alt="Der Schaum auf einem Kaffee bildet ein schreiendes Gesicht." /> 329 329 {{/code}} 330 330 331 -==== =How to mark an image as decorative =====319 +==== How to mark an image as decorative ==== 332 332 333 333 [[image:Texteditor-Bilder-dekorativ.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" height="224" width="300"]] 334 334 ... ... @@ -349,8 +349,6 @@ 349 349 * [[Five golden rules for compliant alt text>>url:https://abilitynet.org.uk/news-blogs/five-golden-rules-compliant-alt-text||shape="rect"]] 350 350 {{/panel}} 351 351 352 - 353 - 354 354 === Optimizing images for smartphones and tablets === 355 355 356 356 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. ... ... @@ -361,8 +361,6 @@ 361 361 <img src="..." style="max-width: 100%" /> 362 362 {{/code}} 363 363 364 - 365 - 366 366 === Providing alternatives for videos and audio files === 367 367 368 368 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. ... ... @@ -380,7 +380,6 @@ 380 380 {{/panel}} 381 381 382 382 383 - 384 384 == Colours & contrasts == 385 385 386 386 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"]]).