RC Spot check: Ratio and Proportion 1.0.0-rc.4

[zepumph]

@terracoda, @emily-phet, @BLFiedler, ratio-and-proportion/1.0.0-rc.4 is ready for RC testing.

This fourth RC should be a spot check.

Document issues in https://github.com/phetsims/ratio-and-proportion/issues and link to this
issue.

As always, thank you QA!

Assigning to @kathy-phet and @KatieWoe for prioritization.

General RC Test

What to Test

• From work done this release in Dev Test: waves-intro/1.0.0-dev.8 #370,please test the in-proportion sound quite a bit.

Issues to Verify

• In ratio ding sound doesn't happen when hand jumps to line ratio-and-proportion#370
• If ratio is high enough, it may be impossible to hit with a mouse ratio-and-proportion#369
• Small hop to get into ratio with keyboard nav may hit ratio twice ratio-and-proportion#354

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)

• Simulation
• iFrame
• XHTML

---

Accessibility (a11y) RC Test

What to Test

• Specific instructions can be found below.
• Make sure the a11y feature doesn't negatively affect the sim in any way.
• Test all possible forms of input.
  • Test all mouse/trackpad inputs.
  • Test all touchscreen inputs.
  • Test all keyboard navigation inputs.
  • Test all forms of input with a screen reader.
  • Test blended input using mouse/touch and keyboard.

Link(s)

• a11y View
• Simulation

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

• Windows 10 + Latest Chrome + Latest JAWS
• Windows 10 + Latest Firefox + Latest NVDA
• macOS + Safari + VoiceOver
• iOS + Safari + VoiceOver (only if specified in testing issue)

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.

---

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:

  <b>Test Device</b>

  blah

  <b>Operating System</b>

  blah

  <b>Browser</b>

  blah

  <b>Problem Description</b>

  blah

  <b>Steps to Reproduce</b>

  blah

  <b>Visuals</b>

  blah

  <details>
  <summary><b>Troubleshooting Information</b></summary>

  blah

  </details>

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:

1. Consult the QA Book.
2. Google it.
3. Ask Katie.
4. Ask a developer.
5. Google it again.
6. Cry.

---

[KatieWoe]

• Win 10 Chrome (Time = 1.5)
• Win 10 Firefox (Time = .5)
• MacOS 11 Safari (Time = .75)
• MacOS 11 Chrome (Time = )
• iPadOS (Time = .5)
• ChromeOS (Time = )

[KatieWoe]

QA is done