Check vs Submit: Button Text Changes Depending on Context?

Submitted by bparks on Wed, 05/07/2025 - 13:05
Forums: 
Bugs in content types

When our developers create H5P assets in H5P.com, the action button for the very same instance of an H5P asset will show the word Submit when viewed or previewed in H5P.com, but when added to our LMS (D2L Brightspace), it will show Check.

No text customizations are being applied manually, and based on what developers are reporting, it isn't always consistent; perhaps even within the same embedded instance of an asset.

Is there a way to make this consistent?

Here are two screenshots of the same asset; one in H5P (Submit), the other in D2L (Check). (Attached.)

It happens with Fill in the Blanks, Fill in the Words, and Multiple Choice.

Thanks!

Attachments: 
Image icon submit.png
Image icon check.png
Content types: 
Quiz (Question Set)
BV52's picture

BV52

Wed, 05/07/2025 - 18:55

Hi bparks,

The "Submit" and "Check" buttons will depend on how the content was inserted in the LMS and how it is viewed by the user.

If a user logs in to H5P.com they will see the "Submit" on the other hand if they access the content without logging in (in case of public contents), they will see "Check". I've attached a screenshot to show this. A content that is inserted in an LMS using the embed code will always show "Check". A content that is inserted using LTI will show "Submit" if the user is logged in but for courses that are public a user that is not logged in will see "Check".

To summarize, a content will only show "Submit" if the content is being accessed in such a way that scores will be recorded. If scores cannot be recorded the content will show "Check".

-BV

 

Attachments: 
Image icon Check and Submit.png

bparks

Wed, 05/07/2025 - 19:05

Hi BV!

This makes sense but (as you can imagine) is initially confusing to developers, who want to verify the text so that they can provide any directives to precede the interactive... I will follow up to the developer who raised the issue and get back to you with any followup questions.

Thanks!