-
Notifications
You must be signed in to change notification settings - Fork 8
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
RC Test: Ratio and Proportion 1.0.0-rc.1 #601
Comments
QA is done. Jaws was more partially tested due to phetsims/ratio-and-proportion#348, but I believe @loganbraywork spent some time on it as well. |
There is no UI sound for checking or unchecking the "Enhanced Sound" option in the lower right speech bubble menu. I suggest using the standard Checkbox and UncheckBox sounds which is the sound used for the "Lock Ratio" option. |
@Ashton-Morris nice catch! After this initial publication, there will be a following publication that will move the "enhanced sound" option into the new Preferences menu Jesse is building. Let's not add sound to the current "enhanced sound" selection, but consider sound for the Preferences and Quick Menus. We might have a working version of this to demo for this Tuesday's sound meeting, and I can show you the latest then. |
All is done here, I'll note #601 (comment) in the next RC issue, and make a new RC, see phetsims/ratio-and-proportion#337 |
@terracoda, @emily-phet, @BLFiedler, @Matthew-Moore240, @jessegreenberg, @jbphet, @Ashton-Morris, ratio-and-proportion/1.0.0-rc.1 is ready for RC testing.
This is the first publication for this brand new simulation. Ratio and Proportion supports the following accessibility features:
Document issues in https://github.com/phetsims/ratio-and-proportion/issues and link to this
issue.
Assigning to @kathy-phet and @KatieWoe for prioritization.
General RC Test
What to Test
for a list of query parameters.)
spreadsheet and notify AR or AM if it not there.
there is a problem.
Issues to Verify
Although this is the first RC, there are a couple of issues to be verified from previous testing.These issues should have the "status:ready-for-qa" label. Check these issues off and close them if they are fixed.
Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue. If the label is
"status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.
Link(s)
Accessibility (a11y) RC Test
What to Test
Link(s)
Screen Readers
This sim supports screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have
all of the information you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the
a11y view before opening the simulation. Once you've done that, open the simulation and make sure alerts and
descriptions work as intended.
Platforms and Screen Readers to Be Tested
Critical Screen Reader Information
We are tracking known screen reader bugs in
this Google Document. If you find a
screen reader bug, please check it against this list.
Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.
Final Requests
issue in website to ask if PhET research page links need updating. Please assign
to @terracoda and @emily-phet.
FAQs for QA Members
There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.
How should I format my issue?
Here's a template for making issues:
Who should I assign?
We typically assign the developer who opened the issue in the QA repository.
My question isn't in here... What should I do?
You should:
The text was updated successfully, but these errors were encountered: