ucfopen / guess-the-phrase-materia-widget Goto Github PK

• The "Start" button at the beginning and the "Finish" button at the end both cannot be tabbed into and are not otherwise accessible from the keyboard. They should be made tab-reachable and/or the player should be able to press Enter to advance like they can between questions. Other than this, the game can be completed using the keyboard.
• The widget does not appear to be screen reader accessible at all (using Voice Over). I did not find any elements that could be tabbed into.
• The question text needs to be screen reader accessible.
• The number of available spaces and found letters should be screen reader accessible.
• The number of incorrect guesses and how many mistakes the player has left should be screen reader accessible.
• There should be an audio indication for whether the player gets a question right or wrong.
• It might be nice to add screen reader support for visual cues, like when the host changes his expression.

It's time to change the name of this widget. We recognize it's name, although a common childhood game in the US, references some pretty horrible events and imagery.

Update all hangman references and graphics to follow the new name.

We've had a request to implement audio support in Guess the Phrase, where a question can be supplemented by an audio snippet.

The custom score screen is making a request to the API for question_set_get to get qset information. This isn't a problem most of the time, because the assumption is the user is already logged in. However, there's one context where this isn't true: when visiting an assignment submission page in Canvas, the student may not be authenticated, and the API call for the qset fails, resulting in the score screen failing to load. The question information should already be baked into the widget_instance_play_scores_get request all score screens normally made, so ideally we use that instead.

As with other widgets, the idea here would be to allow instructors to create a larger set of possible questions than what is provided to a student each time they play the widget. The questions players would receive for any particular play would be a randomized selection from the question bank. For example, an instructor may create 20 individual questions in the creator, but a student would only receive 8 questions when they interact with the widget.

Got this request: https://home.cdl.ucf.edu/dredbeard/tbd_archive/request/view/113951/