Surveys in Learning Sequence

1 Initial Problem

• Currently the Learning Sequence uses a toolbar to offer the Open survey button. This fails Success Criterion 2.4.3 Focus Order (Level A) / Prüfschritt 2.4.3a Schlüssige Reihenfolge bei der Tastaturbedienung: User will start the survey without reading the message or any intriductory text and thus miss out. 
• Currently the Suvrey opens in a new tab and users are forced to leave and then return to the pared-down environment of the learning Sequence. 

2 Conceptual Summary

• Default-Surveys and Self-Evaluation Only can be used in Learning Sequences. Types of surveys cannot be changed, thus the Learning Sequence can check for this. It rejects types Individual Feedback or 360° Feedback. 
• Learning Sequence accepts the launcher to start the survey. The survey launches in kiosk mode. 
• Initially questions are displayed. "Next" button submits answers. The "Next"-Button MUST respect the "required" status of a question. 
• The survey cannot be worked through repeatedly. One the Survey is finished participants will be presented with the Survey Results. If results are not presented a message to that effect is displayed. 

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: {Please add your name.}
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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.

• …

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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.