Show Advanced KnowledgeHide Advanced Knowledge

Language Settings in User Content

1 Initial Problem

ILIAS delivers a whole page with the language definition that is individually set by a logged on visitor. This is done in the initial html tag of the page. Screen readers speak the whole content in this language. For example, if the general settings are set to English and individual content, e. g. of a course, is in German, all German text is spoken with wrong accent and hardly to understand.

This issue refers to WCAG Success Criterion "3.1.2 Language of Parts", in Germany to the corresponding "BITV-Prüfschritt (9.)3.1.2 Anderssprachige Wörter und Abschnitte".

2 Conceptual Summary

Users can set a specific language for every part of their content whenever they need to. This includes

• the overall page item (e.g. course, excercise, content page, etc.) which is the initial user content within the content area,
• each single block of text information within the content area (e.g. plain text, tables, lists, etc.),
• special passages of text within a text block, for example when just one sentence within an English paragraph is written in German.
• (discussable: what is with other, special content like pictures and their alternative text?)

In all cases where the language is set by users, ILIAS delivers the HTML attribute "lang" with the language shortcut (de, en, fr, etc.) within the HTML tags that already mark the specific content (for example the already existing "p" or "div").

Whenever there was originally no HTML tag given for a specific part of the content, ILIAS adds the proper HTML tag and delivers the "lang" attribute as described above, for example in a "span"-tag when only one sentence within a paragraph is set to a different language.

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Wolfgang Schmidt-Sielex
• Maintainer: Killing, Alexander [alex] for ILIAS page editor
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

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

• …
• ILIAS.nrw

9 Discussion

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}.