Skip to content

TestQuestionPool: Show Total Points in Header#11633

Open
thojou wants to merge 1 commit into
ILIAS-eLearning:release_10from
thojou:feature/10/ta-question-table-points-summary
Open

TestQuestionPool: Show Total Points in Header#11633
thojou wants to merge 1 commit into
ILIAS-eLearning:release_10from
thojou:feature/10/ta-question-table-points-summary

Conversation

@thojou
Copy link
Copy Markdown
Contributor

@thojou thojou commented Jun 1, 2026

See: https://mantis.ilias.de/view.php?id=45093

The question pool table should display the sum of all question points. The total is shown in the points column header using the translated total language string. getData() accepts optional order and range parameters so the full dataset can be loaded when calculating the total.

Hey @Annett7811, are there any accessibility concerns with adding a summary of points to the table column header?

Best Regards,
@thojou

See: https://mantis.ilias.de/view.php?id=45093

The question pool table should display the sum of all question points.
The total is shown in the points column header using the translated
`total` language string. `getData()` accepts optional order and range
parameters so the full dataset can be loaded when calculating the total.
@thojou thojou added bugfix php Pull requests that update Php code labels Jun 1, 2026
@Annett7811
Copy link
Copy Markdown

Hello @thojou,

Thank you very much for your inquiry!

From a visual standpoint, the new layout certainly offers added value, as the total score is displayed directly, eliminating the need for tedious manual calculations when integrating it into a test.

However, from the perspective of digital accessibility—and particularly when using screen readers—the situation is currently much more nuanced. Although the additional information is visually available, assistive technologies currently do not convey it in a way that makes the underlying context understandable. For example, assuming a total score of 56 and a score of 1 for a single question, the following occurs:

  • Voice output for column: “Points 56, 1, Collection Actions”
  • Voice output for cell: “Points 56, 1, Column 5 of 15”
  • Voice output row: “Column 1 of 13, checkbox, Test group, link, empty group, Single Choice group, Group 1.00, etc.”

These examples show that the relationships between the information within the table are currently difficult for screen reader users to understand. While the presentation for sighted users has been improved, conveying information via assistive technologies remains challenging.

Fundamentally, complex tables are among the more demanding components in the field of digital accessibility. Even with a technically sound implementation, usage can remain difficult for screen reader users depending on the scope and complexity of the data.

In light of this, I believe we should assess what specific accessibility goal we aim to achieve and whether the development effort required to do so is proportionate to the actual benefits. It may be possible to achieve greater improvements in the system’s accessibility elsewhere using the same resources.

Best regards
@Annett7811

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix php Pull requests that update Php code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants