Add Crosswalk and Pedestrian Signal to Interactive Tutorial?

[jonfroehlich]

Now that we have Crosswalk and Pedestrian Signal label types, we should discuss adding them to the interactive tutorial. Interestingly (and thankfully), these things do show up in our tutorial scenes!

Here's the annotated deck. I may have missed some things.
ProjectSidewalk_Tutorial_PedestrianAndCrosswalksAnnotated.pptx

[misaugstad]

Some notes from a 1:1 meeting with @jonfroehlich:

• Start with user panned to the left a bit more so that they can't see the signal on the right and we don't have to deal with it 😉
• On the corner with 2 ramps, we'll probably let them know that they should label everything, but that we're going to label those 2 ramps and the pedestrian signal (and maybe even that following crosswalk?) for them to speed things up.
• The flow in the beginning is probably...
  1. Label first curb ramp
  2. Label first crosswalk
  3. Pan
  4. Zoom
  5. Label second curb ramp
  6. Label first missing curb ramp
  7. Label first pedestrian signal
  8. Zoom out
• The last curb ramp that they label is probably important to have them continue to label because it's not on a corner
• Outside of what we've generally landed on here, I'm going to play test a little bit to figure out what works to label or skip. It might be hard to tell what the flow is going to be like without actually putting some of those steps in. For example, should we have them label the second crosswalk..?

[misaugstad]

@jonfroehlich @devonsnyder @yeisenberg I have finished a draft of the text in the tutorial that includes crosswalks and pedestrian signals! I removed a few of the curb ramp labels in the middle, and excluded some of the pedestrian signal and crosswalk labels as well to speed things up a bit. The tutorial is still longer than it used to be.

I'm hoping for some input on the text! We can continue to iterate once it's live, but I'd like to at least have one round of text revisions before I send the text off to translators and get the first draft up on our test servers. Below I'm including anything that changed in a significant way. I'm including the text below the images in case you want to copy/paste for editing.

Now let's label the painted crosswalk. <span class="bold">Click the "Crosswalk" button</span>.

Great! Now <span class="bold">click beneath the flashing yellow arrow</span> to label the crosswalk.

Now you can rate the quality of the crosswalk where 1 is passable and 5 is not passable for a wheelchair user. Because the surface is smooth and the paint isn't fading, <span class="bold">let’s rate it as 1, passable.</span>

Uh-oh, you should rate this crosswalk as 1, passable. The surface looks smooth and the paint isn't fading. <span class="bold">Let’s click "1" to set its quality.</span>

On the pole you can see a light telling pedestrians that they can cross the street. <span class="bold">Click the "Pedestrian" Signal button</span> to label it.

Now let's label it by <span class="bold">clicking beneath the flashing yellow arrow</span>. You can see the light higher up on the pole, but we ask you to add your label at the bottom of the pole because it gives us a more accurate location.

Oops! Your label is too far away. For tall objects like poles, we ask you to add labels at the base of the pole. This gives us more accurate location info! <span class="bold">Hover over the label and click the delete icon</span>.

There seems to be a painted crosswalk here as well. First, <span class="bold">click on the "Crosswalk" button</span>.

Let's label it by placing your label near the center of the crosswalk. <span class="bold">Click below the flashing arrow</span> to add your label.

Oops! Your label is too far away. Try adding your label at the center of the crosswalk. <span class="bold">Hover over the label and click the delete icon</span>.

To help speed things up, we are labeling these two curb ramps, this crosswalk, and this pedestrian signal for you. In the future, you should label all of these yourself!

We shouldn't forget the pedestrian signal! <span class="bold">Click the "Pedestrian Signal" button</span> to label it.

<span class="bold">Click at the base of the pole</span> to label this pedestrian signal.

Now you can look for more issues at this location. In this case, notice how there is a crosswalk with pedestrian signals but <span class="bold">no curb ramps</span> at either end.

In the future, you will need to add all of these labels yourself. But we want to get you started on actual missions, so let’s <span class="bold">finish this tutorial!</span>

[jonfroehlich]

This looks so awesome (and I can tell how much diligence and work it took!).

I think we should try to have bolded words in each popup, so just double check that you have that (seems to be missing on a few).

For this one (and one more instance), let's bold "your label is too far away":

But overall, I think this is really close to shippable and then once on test, we can do another round of feedback?

[devonsnyder]

Great job Mikey and team! My only feedback would be to adjust the language of "wheelchair user" if possible to something like "assistive device user" or "someone using an assistive device". Or that could be introduced later once when we've added some language about assistive devices to the labeling guide on the site. I know that makes it a bit more clunky, but it would help make sure raters are also considering how crosswalk conditions impact folks who are using walkers and canes.

…

On Thu, Aug 31, 2023 at 7:58 PM Jon Froehlich ***@***.***> wrote: This looks so awesome (and I can tell how much diligence and work it took!). I think we should try to have *bolded* words in each popup, so just double check that you have that (seems to be missing on a few). For this one (and one more instance), let's bold "your label is too far away": [image: image] <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F1621749%2F264823432-5c0968a0-b214-4c89-8b77-7b55f79e163d.png&data=05%7C01%7Cdsnyde8%40groute.uic.edu%7Cfab89bde3e46458a0f3308dbaa8680b0%7Ce202cd477a564baa99e3e3b71a7c77dd%7C0%7C0%7C638291266887704804%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=o3%2BO6X0kfPAiv4KuImLTc%2FRsRGRCqtC9MtjgYQXRyNk%3D&reserved=0> But overall, I think this is really close to shippable and then once on test, we can do another round of feedback? — Reply to this email directly, view it on GitHub <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FProjectSidewalk%2FSidewalkWebpage%2Fissues%2F2846%23issuecomment-1701965599&data=05%7C01%7Cdsnyde8%40groute.uic.edu%7Cfab89bde3e46458a0f3308dbaa8680b0%7Ce202cd477a564baa99e3e3b71a7c77dd%7C0%7C0%7C638291266887704804%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r%2FE%2B8UI58QV4wcr8q4dynIsLiCJKpKEqOfaZ8n%2FarRQ%3D&reserved=0>, or unsubscribe <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA5OCRMYLNCN6MCNLY4NUNK3XYEXJ3ANCNFSM5SNG25WQ&data=05%7C01%7Cdsnyde8%40groute.uic.edu%7Cfab89bde3e46458a0f3308dbaa8680b0%7Ce202cd477a564baa99e3e3b71a7c77dd%7C0%7C0%7C638291266887704804%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Bj3R6Z3v2BpZo%2BzlJxaHVdtl6WcKiXOYXWkIxJ9iidI%3D&reserved=0> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Devon Snyder *(she/her/they/them)* Project Coordinator Department of Disability and Human Development UIC College of Applied Health Sciences UIC, Master of Urban Planning & Policy '22 ***@***.*** | 425-443-0301

[jonfroehlich]

Great point @devonsnyder. I think this brings up a larger issues about how we frame the problem of sidewalk accessibility labeling: is it generally for anyone who might benefit from an accessible and safe sidewalk (children, people who are blind or low vision, wheelchair users, others who use an assistive aid) or is it specifically for wheelchair users.

I think we've been shifting to the former but haven't yet really made this specific in our UI and framing to the user.

[yeisenberg]

Great work Mikey, looks awesome. some quick feedback:
Agree with the discussion for making it as a larger user group of people with disabilities vs. wheelchair users only
For the ped signal, is there a pop-up with how to fill it out? I know I’m annoying about this, but would still like to advocate for there being a scale on this and having a tag for it having an audio signal (I know I need to get you supporting material for that). I think it is important for blind/low vision group…

[jonfroehlich]

Agree with the discussion for making it as a larger user group of people with disabilities vs. wheelchair users only

Sure, I agree too. But it's not clear how to operationalize this. And it seems like an issue that pervades beyond just the tutorial to nearly all aspects of the tool.

Re: pedestrian labeling
I think that makes sense but I also think that labeling things like audio signal is towards one of the most difficult things we have in Project Sidewalk (and is also fairly US centric). Not saying we shouldn't add it but just pointing to how important it will be to create good training materials

Finally, given the divergence of discussion here, I might offer that we should figure out: (1) what needs to be done right now to ship the new tutorial; (2) what things we know we want to do longer term.

[misaugstad]

I think we should try to have bolded words in each popup, so just double check that you have that (seems to be missing on a few).

Can do!

For this one (and one more instance), let's bold "your label is too far away":

Sounds good!

For the ped signal, is there a pop-up with how to fill it out? I know I’m annoying about this, but would still like to advocate for there being a scale on this and having a tag for it having an audio signal (I know I need to get you supporting material for that). I think it is important for blind/low vision group…

As of now, none of our tags would apply to these pedestrian signals, so I skipped that part and am just closing the context menu and pushing them forward after they label the signal. I figured that if we add tags that would apply, we would update the tutorial at that time!

adjust the language of "wheelchair user" if possible to something like "assistive device user" or "someone using an assistive device".

I had just copied over language from another part of the tutorial 😁 The tutorial may be the best time to introduce this term to users, so maybe it's worth putting it in with a tooltip now since I'm already working on the tutorial?

[yeisenberg]

Got you, thanks for the explanation for that Ped signal Mikey and sounds good to move forwward to complete the task and than adjust once we have more info. I'll follow-up with more info - re possible ways to easily code audible signal precense...thanks