You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sim was originally targets to support alternative input. But I get the feeling that alternative input was not really considered in the design -- I see nothing about alternative input in the design document. Consequently...
We have a very big alternative input problem: how to allow the user to manipulate the interactive (original and predict) curves. The interactive curves have no specific points that can be given focus, nothing to grab with the keyboard. And without being able to manipulate the curves, the sim is not usable with the keyboard. "Free form" manipulation of the curve will be an especially difficult problem.
Unless PhET has the resources to address this, I recommend that we defer alternative input for the first release, and address in a future release.
While we have ideas for how this could work, it is unclear how much time it will take to work out a design solution. We don't know if our idea is consistent with other sims, or if it would be expected behavior for a user interacting with the sim in this way.
We will defer this until we have more resources to dedicate to doing this well.
The sim was originally targets to support alternative input. But I get the feeling that alternative input was not really considered in the design -- I see nothing about alternative input in the design document. Consequently...
We have a very big alternative input problem: how to allow the user to manipulate the interactive (original and predict) curves. The interactive curves have no specific points that can be given focus, nothing to grab with the keyboard. And without being able to manipulate the curves, the sim is not usable with the keyboard. "Free form" manipulation of the curve will be an especially difficult problem.
Unless PhET has the resources to address this, I recommend that we defer alternative input for the first release, and address in a future release.
@veillette FYI.
The text was updated successfully, but these errors were encountered: