phetsims / friction

"Friction" is an educational simulation in HTML5, by PhET Interactive Simulations.
http://phet.colorado.edu/en/simulation/friction
GNU General Public License v3.0
4 stars 6 forks source link

(Voicing) Friction hints during interaction do not seem to fire correctly #194

Closed Matthew-Moore240 closed 3 years ago

Matthew-Moore240 commented 3 years ago

During interaction

When books are grabbed it should read Move Chemistry book down to explore friction.

When books are grabbed Hint after all atoms (actually more than half) have been evaporated. Reset sim to make more observations.

Hint Please button: Current interaction hint: Move Chemistry book down to explore friction.

Hint when the chemistry book is down but there are still lots of atoms left: Continue rubbing chemistry book to generate even more friction.

Hint after all atoms (actually more than half) have been evaporated: Reset sim to make more observations.

terracoda commented 3 years ago

@Matthew-Moore240, I am re-assigning this issue back to you. To document the interaction, you need to document the voicing separately for mouse/touch input and keyboard/gesture input.

We can discuss and then re-assign to @jessegreenberg.

Matthew-Moore240 commented 3 years ago

This was in the design doc. Is this what we are thinking?

Mouse input (w/ interactive highlights on)

Mouse over pink highlight Mouse Click: Grabbed highlight (dotted pink highlight) Object & text: Chemistry book grabbed.

Touch input

On tap (dotted pink highlight appears): Object & text: Chemistry book grabbed.

Gesture input

Alternative Input (Keyboard)

terracoda commented 3 years ago

@Matthew-Moore240, this is looking pretty good. Note that in voicing, the word "button" is never voiced, so the alternative input help, starting with "Look for grab buttons" will need some further thought.

For this sim, I think about three categories of "hint content". Only 1 & 2 are specifically "hint content" in terms of teh voicing deign. There are three kinds of hints I designed fro non-visual access via the PDOM: 1. Two general hints which are dynamic:

I see these kinds of hints as the hints that are good candidates for the Hint read-me button in the voicing design.

2. Individual interaction help text hints

This "direct interaction help text". In voicing design, direct hints on interactions are what gets turned via the checkbox in the Preferences menu.

This hint won't work for the voicing design because we don't use role names, like "button" in the voicing design. Sometimes we can use the help text straight from the PDOM design, but in this case we cannot. And often we want something shorter. That said, this interaction is a custom drag and grab, so I am not sure the best way to voice it yet.

In the first interviews with blind learners it was referred to as a slider, even though it technically not a slider. I think that is good association for a learner to make - the book moves back and forth and they use the arrow keys to move it. It kind of works like a slider. The guidance needed for alternative input on the book before it is grabbed needs to be about how to grab. Ideally you need no instructions for that, but you might.

3. Interaction guiding

I think you need to think about if you need any specific help text about the grab interaction for alternative input & custom gesture. With alternative input on the first go around words actually show up on the screen, so you want to consider what is displayed, on the second go around the words may not be there, so you want to consider that, too.

terracoda commented 3 years ago

I am unassigning myself. @Matthew-Moore240, let me know if you need anything from me.

Matthew-Moore240 commented 3 years ago

This seems fixed. Closing.