Skip to content
This repository has been archived by the owner on May 24, 2022. It is now read-only.

Meeting10.18.2017

Charles LaPierre edited this page Oct 18, 2017 · 1 revision

Drag and Drop 10/18/17

Present:

Charles, Jason S, Jason W, Richard, Sina, Jesse

Agenda

The document classifying drag and drop interactions is here: Google Doc

and the spreadsheet is available at

Google Spreadsheet

The more detailed analysis published on the wiki is at

Wiki on Analysis

Discussion

Priority to contribute to last call D&D interactions and filling out that table.

Jesse: I added a few examples from Phet, we can talk about it if we want, some examples could be consolidated.

row 16 - added Ex: difficult play with object in 2d the object can mutate and then the position or any part of the object can change when dropped.

ballon can pick up charges and different charges can move around while dragging and then when you drop it it can interact with the other.

Sina: speed matter?

Jesse: no

Sina: path followed matter?

Jesse: I suppose, I don't see it as applying, the ballon can move anywhere in the 2D plane.

Sina: imagine a chess board wool in the bottom corner, vs. top left is marble. So path does matter here because we encounter different things in the path. Imagine dragging the file to a folder the path here doesn't matter.

Jesse: Row17 Drag. objects on 1D line. Ex: two masses next to eachother closer and farther away changes forces as distance changes, you can also increase the mass. the drage and drop is changing their separating. web-slider using arrow keys page/updown home/end to min/max. tricky there is 1D line the position of mass then the distance the 2nd can only move upto the original image (Intermediate difficulty)

Sina: absolute position for both and limit the movement 1-10 and mass one is at 2 and the other at 6 then the first can move between 1 and 5 where the other can move from 3 to 10

Sina: you can also increase the mass that can be done with some other control / slider

Jesse: Yes,

JasonW. You need to make sure they are labelled corrected.

Charles: Intermediate?

Jesse: interaction of the two can change that is why.

Jesse: Row 18-Difficult: two objects you can rub them together and speed matters and path matters. Two books can be rubbed together so friction can change and so does the heat. depending on where you drop the book onto the other book and only if you rub quickly.

Jason: Path really doesn't matter except the destination doesn't it.

Sina: the path doesn't matter the cadence of the repetition

You pick something up you rub it friction goes up you drop it and the head drops.

Sina: Pick it up and you are extending the drag. Path matters speed matters.

Jesse: made accessible with aria role WASD and arrow keys to move in a 2D area, keyboard access, idea is with aria roles should work.

Sina: moving it up/down vs. left right

Jesse: but you have to be near the book or nothing happens

Jason: you have path that matter, the destination doesn't matter. Both path and velocity are significant and 2D and could be 1D.

Sina: if I rub it at 2 rubs per second, the temp would go.

Sina: we care about Temp T, and Intensity of 5 / 10 and the fall in temp would drop off and sonification could be very useful here.

Jason: In this seneario destination does not matter but it could if you drop the book in water vs. on stone etc...

Couple variations around this examples are some interesting possibilities: How to handle needs to carry out the interaction (fine motor control) to adjust the rubbing speed, maybe the timing of it. you can automate the pickup/dropoff if dest doesn't matter.

Sina: if dest matters. you could have a dropdown that says after rubbing ends drop book on marble, vs. On the book, or on a table. Then you can re-run sim with different vigor

Jason: we want to have some guidance to when its appropriate to use D&D metaphor vs. when not to use that even if its the obvious choice. In this case it might be best not to use the megaphor.

Jesse: general case ballon and path matters and speed could matter there too. If we have an accessible solution where path and speed matter.

Jason: you can play the balloons against eachother and the forces could interact

Charles could set the speed right away and soon as you pick up the book it could start shaking at that speed if we needed to and then you drag over the book then the temp would start rising.

Sina: Alexa version "Rub a book at speed x over target y and deposit on cold marble."

Jason: you could specify every motion in speech commands but thats impractical, give the parameters to carry out for you vs. carry out manually which would then have the D&D.

Richard: what are you trying to teach here. More and more friction gets hotter and hotter. if I am to teach a blind kids I would say take your two hands and rub them together to see this in real life.

Sina: if astroid speed, path matters in specific case menu driven but in the generic case the concept of friction making the D&D case accessible.

Jason: path matters that the geometry matters and not proximity of objects. Drawing applications, where speed and geometry matters.

Sina: car going along a park strip spikes direction matters and speed # of punctures would result.

Jason: 2D road doesn't have to be 1D. how to make this universally designed. you can have large # of destinations then you are introducing that level of complexity. if you combine all of those then we don't have completely obvious solutions.

Charles: large # of destinations, speed and path matters in the sense that geometry traced by the path

Richard: I would like to ask questions. they might work a lot better on a tablet with a touch screen have you considered that?

Jesse: Yes keyboard interaction was #1, but we are interested in SR accessibility JAWS/NVDA

Richard with moving your finger across the screen, could work here as well. Touch screens are very popular now for VI students, and more laptops have touch screens.

Jesse: I agree so thanks.

Jason: that get complicated on screen readers that intercept a lot of touch events. I don't know how they interact with touch and ARIA roles etc.

Richard: It wouldn't have to be a web app but could be a more native app.

Jesse: goal of this spreadsheet was to get info and then disseminate that information and then ask the community for more examples and ask their feedback.

Jason: Yes, along with the accessibility document that I created, and design guidance could ultimately come out of this and give general guidance. but we haven't yet decided yet the deliverables. if we find a good example that we can construct we can do that. So far that we are finding some good examples. We can find cases for most of these already and if there are gaps we can build a solution and then create guidelines on best practices around these.

Charles: Then we will show these cases on our DIAGRAM Center code repo, and I can envision a webinar showcasing these various examples and best practices once we feel we are ready to do so.

Next Meeting Friday Nov 3rd at 11AM Pacific / 2PM Eastern

Clone this wiki locally