Question Score content type to review

Submitted by ricoshae on Thu, 04/09/2026 - 23:36

Forums:

Hi,

Could you please review this content type that I have develped.

Question Score is a versatile assessment tool that allows you to create list-based questionnaires with weighted responses. Unlike standard quizzes that focus on "right" or "wrong" answers, this plugin calculates a total score based on the intensity or frequency of a user's selections (e.g., Yes, Sometimes, or No).

Key Features:

Customizable Labels: Tailor the three response options to suit your context (e.g., Always/Often/Never or Agree/Neutral/Disagree).
Weighted Scoring: Assign specific point values to each response option to weight the final result.
Dynamic Feedback: Define "Score Bands" (ranges) to trigger specific feedback messages once the user completes the questionnaire.
Quick Setup: Use the "Quick Insert" feature to paste a list of questions at once, making it easy to convert existing paper-based surveys into interactive digital activities.
Accessible Design: Built with accessibility in mind, featuring screen-reader support, keyboard navigation, and responsive layouts for mobile devices.

This plugin is ideal for self-assessments, personality indicators, risk evaluations, or any scenario where a cumulative score determines a personalized recommendation or outcome.

Developed by Chris Richter at Ricoshae.

Thanks,

Chris

H5P file:

H5P.QuestionScore-1.0.12.h5p

otacke

Fri, 04/10/2026 - 11:16

Permalink

Hi Chris!You may want to

Hi Chris!

You may want to check your content type yourself first with "How to review H5P content types" as your guide.

Had a quick look and observed this:

Your content file is invalid - did you build it by hand??? Your library folder is lacking the version number.
Some of the parameter fields are not encoded properly such that e.g. an apostrophe is rendered as '
Now that H5P supports theming, you may want to support that, too.
Using <hx> tags is somewhat problematic, because you never know in what context H5P content is rendered, so the headline hierachy may be wrong. You set <h2>, but what if the content is displayed deeper in the hierarchy under an <h4>, for instance?
Setting 800px max-width in CSS feels odd.
clip is deprecated
CSS may benefit from combining classes that are used frequently + custom CSS properties for common colors, etc.
Having a hidden "Skip to results" is not seen in any other H5P content type. And it might make more sense to add it to the DOM just once and hide it when not needed instead of rebuilding it every time the user calculates the score.
H5P core injects a "Title" field already. You add another one. Confusing for authors, and you could simple use the value from the core editor field. It's in the 3rd constructor argument that you don't use.
Building all the HTML with strings is very heavy on the eye and makes it hard to interpret. Thought about using a templating library? Or building the elements programatically?
JQuery is used, but at some point, H5P Group will get rid of it. Better not to rely on it except for where H5P still requires it.
Using the contentid for prefixing ids will break if your content type is ever used as subcontent. The ids will then be identical across subcontent instances.
For "quick insert", there's a dedicated H5P editor widget for lists, cmp. e.g. Question Set. Might make sense to use that instead for consistency.
Hardcoded strings, not translatable.
Comments should rather tell you "Why", not "What". "What" should be clear from code.
Grid might make more sense than linked flex boxes
Flex feels overused in general where it's not really required.
Aren't the h5p-question-score-option-mobile-label fields redundant to what the aria label(s) already convey(s)?
Your radio inputs have focus and focus-visible at the same time.
ES5, yeah, well.
Not following the coding style guide.