Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Alternative Input. #161

Open
pixelzoom opened this issue Oct 8, 2024 · 3 comments
Open

Add support for Alternative Input. #161

pixelzoom opened this issue Oct 8, 2024 · 3 comments

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented Oct 8, 2024

Related to #160 ... @arouinfar suggest this if we proceed with PhET-iO instrumentation, then we should consider adding support for alternative input. This sim has pickers, radio buttons, accordion boxes, and 1 combo box. There are no custom UI components or draggables. So instrumentation should be mostly a matter of deciding on focus order. (Although there may be some gotchas in the Game screen, due to its highly-dynamic implementation.)

@kathy-phet FYI.

@pixelzoom
Copy link
Contributor Author

In the above commit, I turned on alternative input and added a basic pdomOrder (everything in the play area). Next step is to design the pdomOrder.

@pixelzoom
Copy link
Contributor Author

pixelzoom commented Oct 11, 2024

At 10/10/24 iteration planning meeting, this work was put on hold.

@pixelzoom
Copy link
Contributor Author

pixelzoom commented Nov 7, 2024

In the above commit, I turned alt input off for the 1.3 release, which does not include alt input -- see #154.

To turn it back on, add "supportsInteractiveDescription": true, to package.json, then run grunt update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants