Forum Discussion
Matching Knowledge Check changes
I noticed that the matching exercise on knowledge checks has changed format. Instead of dragging them to their match, it now makes you select a number from a drop down. When you choose a number on one of the choices it doesn't change the number on the choice you are on, but adds the number to another of the choices.
I'm either doing something wrong or it doesn't work properly. Is there are reason for the change? The previous drag and match format was easier to use.
18 Replies
Hi KyleClements1 and LucianaPiazza any update on this? The original post was 5 months ago - it's still not able to be used. Can you give us some indication of what the plan is here from the product team or get someone in the product team to confirm they are looking at this please - it's a significant issue for us and means we're using alternative software to circumnavigate the issue, instead of articulate.
Hi HEATHERDOWLI263,
I'm happy to chime in. Thanks for your patience with this issue.
Our product team is close to a solution for this, and we'll update this thread once the changes are available. Stay tuned!
That’s great news, thanks for the update!
Following!
Thanks for sharing your voice with us AngeliqueSummer! I have shared your interest with our product team. We'll be sure to share any news in this thread on future updates.
Have a great afternoon!
Can this be fixed as soon as possible please?
This is an instructional design disaster...Hello mdemulder,
I appreciate you sharing your voice with us. We do not have any updates to share at this time. I have shared your insight with the product team. We'll be sure to update this thread with any future news so all are in the loop.
Have a great afternoon!
Hi, I absolutely agree that the change/update to the matching interaction is not functional. We can't use it and have had to replace it with SL blocks, which is time-consuming and irritating. Where possible, we're just using an alternative software to build matching interactions (not articulate). Of course, improving accessibility is important, but not at the expense of functionality. The numbers make the matching activity too confusing to use, and so we're just not using it currently. The ability to turn off the numbering or have this only activated using screen readers or other assistive tech would be optimal.
Hi KyleClements1 any update on this? It's causing us big headaches and confusion :( Can you provide any info on the plan here please?
Following!
Hi KyleClements1 , I'd be up for a chat. Unfortunately the company I work for has blocked the link you've added to sign up. Is there another way to do this?
Absolutely! Feel free to send me an email at kclements@articulate.com. We'll be reaching out to schedule conversations by the end of this week.
Just following up to see how we are going with getting rid of this problematic numbering - it has been raised a while ago now and makes matching now unuseable.
Hi all, thank you for the discussion. We are exploring options to address this feedback and would appreciate the opportunity to discuss them with you. If you’re open to a quick 30-minute chat, we’ll send you a $25 gift card as a thank you.
Sign up here: https://forms.gle/dcfz4PDn8dSJCVt99
Thank you!
Oh wow, thanks PhilFoss, I didn't even know CSS Rise themes were a thing. I'll tinker with this tomorrow and hopefully be able to change the interaction back to how it used to be.
Nick, I created a theme component to improve the ui, documented here.
https://theme-360.com/theme-component/matching-quiz-customization/
I'm curious how much user testing went into this recent change to improve the accessibility, if anyone has expertise in this field please share. NickEastham-e77Our team of learning designers also agree. While I realise that this extra input option makes the interaction keyboard accessible, it also makes it confusing and pretty ugly too.
Our other issue is that we have already built 25 modules for a client, who is very happy with them, but we still have more to build. That means there will now be 2 different styles of Matching KCs across our suite of modules, which is not something that anyone wants. And we really wouldn't want to go back and republish the originals, as we prefer them to the new style.
Could there be a way to switch off the new accessible feature, please!?
Hi Lorraine,
I agree with you that this seems to be a change for the worse. Looks terrible in my work. Considering entering a SL block but that's some work.
