Upgrade KDS to 5.10.0 and use readonly choice controls in the choice interaction editor

[AlexVelezLl]

Summary

• Upgrades kolibri-design-system from 5.9.0 to 5.10.0.
• In the QTI choice interaction editor, the correct-answer radios and checkboxes shown in view mode are now readonly instead of disabled, using the new KDS readonly prop.

References

• KDS readonly support: Add readonly mode to KCheckbox and KRadioButtonGroup kolibri-design-system#1347
• KDS issue: Add readonly mode to KCheckbox, KRadioButton and KRadioButtonGroup kolibri-design-system#1342

Reviewer guidance

• Open an exercise with QTI single-select and multi-select questions and view a question in view mode with answers shown. The correct-answer controls should look enabled, be reachable by keyboard, and ignore clicks.
• In edit mode, marking correct answers should work as before.
• The view-mode test that checked for disabled radios now checks that radios and checkboxes are readonly: enabled, aria-readonly, and the selection is unchanged after a click or a native radio change. The full Jest suite passes locally.

AI usage

I used Claude Code to bump KDS, replace disabled with the new readonly API in the choice interaction editor following the KDS 5.10.0 changelog, update the view-mode tests, and run the full Jest suite.

🤖 Generated with Claude Code

[rtibblesbot]

🟡 Waiting for changes

Last updated: 2026-10-14 17:17 UTC

[rtibblesbot]

PR #6317: no blocking issues. The disabled → readonly swap matches KDS 5.10.0. Clicks and keys leave answers unchanged. No sync changes are sent.

• Commits pushed after 90f953a were not reviewed.
• CI pending.
• Manual QA passed: single- and multi-select view mode, edit → view round trips, and KDS 5.10.0 checkbox/radio/theme regressions elsewhere in Studio.
• Axe found nothing new on the choice controls.
• Not verified: server persistence of the multi-select edit (QA stack Redis failed).
• Not verified: real screen-reader output for aria-readonly.
• Suggestions and a nitpick inline.

---

Written by rtibblesbot, an LLM-based coding agent.

[rtibblesbot]

PR #6317: 1 of 3 prior findings resolved; 2 still open.

CI passing. Manual QA did not run, so the UI is unverified.

• suggestion (open thread on Editor.vue:91): arrow keys still move focus across questions in view mode. No radio has a name. Chromium therefore treats every view-mode radio on the panel as one native group. Reply, fix, or file a follow-up.
• nitpick (open thread on Editor.spec.js:436): the new test at :453 throws instead of failing clearly when no answer is correct. Add the -1 assertion suggested inline.

Prior-finding status

RESOLVED — contentcuration/contentcuration/frontend/shared/views/QTIEditor/interactions/choice/Editor.vue:182 — onToggleCorrect has no view-mode guard
UNADDRESSED — contentcuration/contentcuration/frontend/shared/views/QTIEditor/interactions/choice/Editor.vue:91 — Arrow keys move focus across questions in view mode
UNADDRESSED — contentcuration/contentcuration/frontend/shared/views/QTIEditor/interactions/choice/tests/Editor.spec.js:436 — Test throws instead of failing clearly without a correct answer

---

Written by rtibblesbot, an LLM-based coding agent.

[rtibblesbot]

PR #6317: no new findings. 3 of 4 prior findings are resolved. The arrow-key focus finding is deferred to KDS#1334. CI passes. Manual QA found no regressions.

Prior-finding status

RESOLVED — contentcuration/contentcuration/frontend/shared/views/QTIEditor/interactions/choice/Editor.vue:182 — onToggleCorrect has no view-mode guard
ACKNOWLEDGED — contentcuration/contentcuration/frontend/shared/views/QTIEditor/interactions/choice/Editor.vue:91 — arrow keys move focus across questions in view mode (KDS#1334)
RESOLVED — contentcuration/contentcuration/frontend/shared/views/QTIEditor/interactions/choice/tests/Editor.spec.js — radio click test throws when fixture has no correct answer
RESOLVED — contentcuration/contentcuration/frontend/shared/views/QTIEditor/interactions/choice/tests/Editor.spec.js — native change test throws when fixture has no correct answer

---

Written by rtibblesbot, an LLM-based coding agent.

[rtibbles]

Code changes make sense, local QA checks out.

[rtibblesbot]

Quick check on rtibblesbot's review of this PR: react 👍 helpful · 😕 mixed · 👎 not helpful. Reply with anything specific.