# data[].attributes.body
had no problem changing answers. Used green button.

# data[].attributes.body
Selected AC with no problem.

# data[].attributes.body
Struggled at first, prior to reading stem, then read the stem and knew what to do. No struggles after that.

# data[].attributes.body
Had no problem changing answers. used green button.

# data[].attributes.body
Selected AC with no problem.

# data[].attributes.body
Changed his ACs with no problem, and did so in multiple ways across activities. For GO 1, used the Change AC button.
For GO 2, used Drag-Out and Select New AC (changed 3 times).
For GO 4, used the Change AC button again.

# data[].attributes.body
Had no problem changing answers. Used green buttons.

# data[].attributes.body
Had no problem changing answers. Dragged her previous answer back to change it.

# data[].attributes.body
S2 G3
Student selected her answer with no problem.  she tried to click the AC a couple of times (and the AC's audio button) before dragging (likely would have been solved with sticky click which was not enabled)

# data[].attributes.body
No issues with interaction.

# data[].attributes.body
Used the Drawer Toggle unprompted and with no trouble. "Can I go back to the passage?" He asked, as he clicked the button without hesitation

# data[].attributes.body
Had no problem navigating to and from the passage reader.

# data[].attributes.body
No issues with interaction.

# data[].attributes.body
No issues with interaction.

# data[].attributes.body
S2, G3

Struggled slightly with this interaction she tried clicking the AC's in the passage but it didn't respond, she then said " I don't get what to do now," she said. "See, there's nothing down here," as she traced her cursor over the bottom area of the activity panel ( where AC's had been for the previous MC activity). Finally she pressed down hard on the trackpad to select an answer on the answer choices (by tapping)

# data[].attributes.body
For GO #2, he tried to click the "x" in the right hand corner to get back to the text. Found the arrow later, suggested the arrow should be a different color.

# data[].attributes.body
Was more or less able to articulate the layout of information in the charts. Grasped the relationship between the Dropzone and the ACs in both MC and DD activities.

# data[].attributes.body
No issues with interaction. Green button each time. Called the UI the "redo button".

# data[].attributes.body
No issues with interaction. No prompting needed. Drug initial AC out of box before selecting another AC.

# data[].attributes.body
had no problem navigating to and from the passage reader.

# data[].attributes.body
changed answer without any issues, used green button

# data[].attributes.body
had no problem navigating to and from the passage reader.

# data[].attributes.body
Selected ACs with no issues.

# data[].attributes.body
had no problem navigating to and from the passage reader, did this one time unprompted as well.

# data[].attributes.body
S2 G3,

Used the toggle button successfully to navigate to the passage reader. He tried clicking before it was activiated (when the stem was still reading), but seemingly knew what the function of the button

# data[].attributes.body
No prompting, found it immediately on his own. Said "Oh! You can't see it! (referring to the text)." Then immediately found the button.

# data[].attributes.body
Selected ACs with no issues.

# data[].attributes.body
Student was initially unsure what to drag in. Seemed like he clicked accidentally but then he figured out what to do. Successfully changed his answer unprompted.

# data[].attributes.body
Changed ACs without issue. Consistently used the Change AC button across activities.

# data[].attributes.body
Mumbled, "Wait, where's the...." when item first loaded, didn't see the answer choices at first. Clicked audio button next to "Foolproof" in GO. Reread stem. Moused over "?" box. Finally got it. Reread the passage text and tried answering, got it right.

# data[].attributes.body
Read the stem, then said "Wait. Do you think you can go back to the text?" but before he finished his sentence, he found the button.

# data[].attributes.body
S3 demonstrated mild confusion because he tried to click the Toggle Button before the STEM finished auto-reading, at which point it is ghosted and non-interactive. But he tried again and recovered quickly.

# data[].attributes.body
Understood it fully. Pointed to every part of the GO and identified what it is "That's the cause. That's the effect." while pointing to them on screen. Then showed us how you drag an AC into the box.

# data[].attributes.body
S3 was able to articulate the relationships of elements in the chart. Grasped and demonstrated understanding of connection between Dropzone and ACs.

# data[].attributes.body
S2, G3
The student understood the elements on the screen and recognized that what to do. immediately understood to place AC's into dropzone in order to complete the activity

# data[].attributes.body
Initially tried to click her answer, then dragged it in successfully.

# data[].attributes.body
Had no problems.

# data[].attributes.body
The student understood elements. 100% clear explanation of purpose and functionality.

# data[].attributes.body
Had no problems.

# data[].attributes.body
Had no problems, dragged it each time.

# data[].attributes.body
Understood it fully. Pointed on screen while saying "Drag it up into there."

# data[].attributes.body
Had no problems, dragged it each time.

# data[].attributes.body
Did not like that when he clicked the arrow, he was sent right to the GO. Really didn't like that the voice started reading the question right away.

# data[].attributes.body
He had selected an answer at first and struggled to find his way back to the text. Clicked the HELP and PAUSE buttons in the progress bar and the iReady bar X UI and clicked the text on the far left. Then we said that he had to remove his AC, he found it pretty quickly.

# data[].attributes.body
Had basic understanding, Understood she needed to pull in an answer choice.

# data[].attributes.body
Had basic understanding, Understood she needed to pull in an answer choice.

# data[].attributes.body
Got it! Easy (He dragged didn't use Undo button.)