RC Spot Check: John Travoltage 1.5.0-rc.3

[jbphet]

@KatieWoe and @ariel-phet, John Travoltage 1.5.0-rc.3 is ready for RC testing. Testing on 1.5.0-rc.2 was completed, and some a11y related issues were addressed as a result. Only small changes were made since the previous rounds of testing, so I think verification of the issues listed below coupled with a quick spot check on key platforms should be sufficient.

Please document any issues in https://github.com/phetsims/john-travoltage/issues and link to this issue.

Assigning @ariel-phet for prioritization.

General RC Test

What to Test

• Two of the issues addressed by this RC are related to screen readers (but they are kind of the same issue), so some testing with screen readers will be necessary.
• One of the issues addressed by this RC was specific to Internet Explorer, so some testing on that platform will be necessary.
• The addition of sound was the primary purpose of the 1.5 release. While nothing has changed with respect to sound for this RC, it's still good to pay close attention to it.

Issues to Verify

• Jaws performance and reading alerts
• JAWS and NVDA alerts read late
• Sim won't behave properly after keyboard nav in full screen IE

These issues should have the "status:fixed-pending-testing" label. Check these issues off and change their status to fixed-awaiting-deploy if resolved. Otherwise, post a comment in the issue saying that it wasn't fixed.

Link(s)

• Simulation
• iFrame
• XHTML
• Legends of Learning Harness

---

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]

Devices to Test On (@jbphet let me know if you have any changes you want):

• Win 10 Chrome Full
• Win 10 Edge Full
• Win 10 Firefox Full

---

• Mac OS 10.14 Chrome Partial
• Mac OS 10.14 Safari Full
• Mac OS 10.14 Firefox Partial

---

• Win 8.1 IE Full
• Win 8.1 chrome Partial
• Win 7 IE Partial

---

• Mac OS 10.13 Firefox Partial
• Mac OS 10.13 Safari Partial

---

• Chrome OS Partial

---

• iOS 12 Full
• iOS 11 Partial

[KatieWoe]

QA is Done

[jbphet]

Thanks @KatieWoe and team - I will move forward with publication. Closing.