Dev Test: Friction 1.6.0-dev.28

[zepumph]

Dev Test

Please let me know when this is ready to test and I will get you a fresh dev version for Friction

Simulation links

• github repository for issues
• phet top level directory
• sim: all_phet.html
• phet-io wrapper index

Test Matrix

Please include (non-screen reader) a11y testing in these records if applicable.

• Latest macOS, Safari (Time = 2.25hrs)
• Windows 10, Chrome (Time = )
• Windows 10/11, Firefox (Time = 2)
• Latest iOS, Safari (Time 2.5)
• Windows 11, Chrome (Time =2.10 )

If PhET-iO is being tested:

• Latest macOS, Safari (Time = 2.5hrs)
• Windows 10, Chrome (Time = 1)
• Windows 11, Firefox (Time = 2.5)
• Latest iOS, Safari (Time = )
• Windows 11, Chrome (Time = 1.5)

If screen readers are being tested (This includes PhET-iO Testing as well as the base sim):

• Win 10/11 Chrome + Jaws (Time = 2)
• Win 10/11 Firefox + NVDA (Time = 1hr)
• MacOS Safari + VO (Time = 1.25hr)
• iPadOS Mobile VO (Time = 1hr)

Features included

• PhET-iO
• Alternative Input
• UI Sound
• Sonification
• Description
• Voicing

(fun!)

Focus and Special Instructions

This simulation is one of the first to be published with PhET-iO instrumentation and full description and voicing
implementations (if not the first). There is a lot that may be weird in that intersection space, but it would awesome to
know about all of it. With that in mind, please test the following items, and feel free to be creative with
description/voicing/sound features as they pertain to this PhET-iO sim.

• Test "launched" studio customized sims with a screen reader.
• Test "launched" studio customized sims with voicing and interactive highlights.
• In the state wrapper, make sure that while setting state, there isn't unexpected content (sound/voicing etc).
• Let me know if you have any questions!
• Audio ducking support has been added in Add support for "ducking", i.e. reducing output levels so that other things can be better heard tambo#172, so please test behavior when sound and voicing are both on to see if balance or back-and-forth are awkward in any cases. Please report any issues there.

---

For QA...

General features

What to Test

• Click every single button.
• If there is sound, make sure it works.
• Make sure you can't lose anything.
• Play with the sim normally.
• Try to break the sim.
• Try to include browser version numbers
• If there is a console available, check for errors and include them in the Problem Description.
• Run through the string tests on at least one platform, especially if it is about to go to rc.
• Check the Game Up harness on one platform.

---

PhET-iO features

What to Test

• Make sure that public files do not have password protection. Use a private browser for this.
• Make sure that private files do have password protection. Use a private browser for this.
• Make sure standalone sim is working properly.
• Make sure the wrapper index is working properly.
• Make sure each wrapper is working properly.
• Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
• For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
  sure the simulation loads without crashing or throwing errors.

---

Accessibility features

What to Test

• Specific instructions can be found above.

• Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is a list of features that may be supported in this test:

  • Alternative Input
  • Interactive Description
  • Sound and Sonification
  • Pan and Zoom
  • Mobile Description
  • Voicing

• Test all possible forms of input.

  • Test all mouse/trackpad inputs.
  • Test all touchscreen inputs.
  • Test all keyboard navigation inputs (if applicable).
  • Test all forms of input with a screen reader (if applicable).

Screen Readers

This sim may support 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.

---

[zepumph]

I was told by KP that we are ready to test, so I made 1.6.0-dev.27.

[zepumph]

I updated the dev version to dev.28 to include audio ducking between voicing and sound from phetsims/tambo#172.

[Nancy-Salpepi]

Since we were asked to test launched studio customizations with a screen reader I wanted to point out phetsims/friction#286 (comment). This issue is currently closed and wasn't sure if it should be reopened.

[Nancy-Salpepi]

When testing with NVDA, exiting a dialog (using esc or when focus is on the 'x') causes the first sentences of the sim description to be uttered--"Friction is an interactive sim. It changes as you play with it. It has a play area and a control." Is that normal or should I make an issue?

[zepumph]

I think an issue would be good to confirm

[KatieWoe]

Calling QA here

[zepumph]

Excellent. Thanks all. See RC in #886