Tile View improvement

1 Initial Problem

ILIAS content that is set to tile view produces double links which are successive and identical. One link is set on the tile/image itself, the other link is set on the title of the destination page which is shown below the tile. This kind of identical consecutive links interferes with the user experience, especially when you use keyboard control (tabbing).

2 Conceptual Summary

• The visual functionality of the tile view should remain as it is: click or tap either on the graphical tile or on the title that is shown below the tile.
• However, the delivered HTML and CSS needs to be improved so that there will be just one single link for the whole area of tile and title together. This may be done by one of the following (or other) suggestions, whichever is easier to achieve and doesn't produce other irritations:
  • Suggestion 1:
    • Remove the link from the tile/image.
    • Use CSS to enlarge the link area of the title text (which is seen below the tile) and place that area in front of the tile so that it is still possible to optically click or tap onto both: the tile and the text. Then the one remaining link clearly indicates its purpose and destination.
    • (This suggestion comes from a comment in a Mantis bug that dealt with a tile issue, see: https://mantis.ilias.de/view.php?id=32545#c82801)
  • Suggestion 2:
    • Remove both links from the tile and the title text below the tile.
    • Add the link to an overarching container which includes both: the tile and the title text.

3 User Interface Modifications

3.1 List of Affected Views

• Tile view of ILIAS content (e.g. courses). The visual appearance of the view is not affected.

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

The feature improves accessibility.

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: Schmidt-Sielex, Wolfgang [WSS]
• 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}.