
On May 1, 2018, Accessibility NYC hosted a meetup entitled “LinkNYC Accessibility.” Presenters Ruth Fasoldt, Kevin Green and Emily Pease described LinkNYC, a first-of-its-kind communications network replacing over 7,500 pay phones across the five boroughs with new structures called Links. They provided a live demonstration of LinkNYC’s services and accessibility features as well as the network’s superfast free public Wi-Fi.
Here are some highlights from LinkNYC’s presentation:
- Access free superfast Gigabit Wi-Fi
- Urban design that is accessible to all communities
- Customization of the TalkBack feature
- “Call Santa” from a Link
Transcript: A11yNYC May 2018 Meetup - LinkNYC Accessibility
Welcome to the Accessibility New York event. We're excited to have you all here. Excited to have you all here. We want to thank our event hosts, Thotbot.
We graciously appreciate having a space for our events. We also have Joly MacFie streaming out on the web. We have some people on the live stream, I know participating. We also want to make sure that as we have these events, we'll be having this event the first Tuesday of every month.
And so, in general, if you have a topic that you'd be interested in either presenting or if you know someone that you think would be an interesting topic for our meetup, we try to keep it broad and diverse. Last month, we had a presentation on autism, you know, from a psychologist and author. This month, we have link NYC and talking about accessibility. Really happy to introduce the team from Lincoln NYC.
We've got if you don't know Link, I don't think you're a New Yorker. We have, actually going to have a live demonstration today. Without further ado, I'll hand over to Ruth and get started. Thanks.
We're just figuring out logistics. Okay. Thank you so much for letting us come to talk to you today. We're thrilled to be here.
We don't need to do introductions because you just did that for us. So we'll just dive right in so we can go to the next slide. If you didn't know what Link was, we work for a company called Intersection, and we're partnered with the City of New York to replace the pay phones with LinkNYC kiosks. This is a project that started years ago, actually, under Mayor Bloomberg.
He saw that there was real estate across the five boroughs, the prime real estate with the old pay phones sitting there that no one needed anymore because we were using our cell phones. And he saw a great digital divide building in our community. He started this idea and then, it moved to mayor de Blasio and they RN launched the relaunch of the pay phone and our company won it. And we are building Links.
Kiosks are about 9 feet tall, about 11 inches wide. So they're actually much skinnier than old pay phones. We're also opening up the street scapes, making more room. If you think about the old pay phones that were two or three phone banks full, that's 4 to 6 feet wide on the street, and our Links bring it down to about 11 inches.
It brings free WI FI to everyone in New York City. Also has free phone calling from the tablet, which we'll walk through in a moment. The tablet also has lots of apps you can explore in a curated way such as maps, you can access 311, you can access social services. We have the weather on there at all times.
We have a transit app so you can find when your train is coming or your bus is coming. So this is all right here across the city as part of this one LinkNYC network. You want to go to the next slide. I started by mentioning the WI FI.
So that is really the core of what the project is. Everybody, you know, can access this WI FI for free. And it is not regular WI FI, it is super fast gigabit WI FI. That's what this is supposed to demonstrate.
This WI FI is faster than anything I can even pay for in my own home. And the reason we built it this fast is because we have a contract with the city that we will be building and running this project for at least 12 to 15 years. And when internet was invented, you couldn't have imagined Netflix, right? So we wanted to build a network that was big enough and strong enough to handle all of the technology that's coming down the pike that will be here in two years, five years, ten years.
Let's see. What else do we have? What's the next slide? Okay.
So that's really an overview of what LinkNYC is. A couple other quick things that once Kevin tells you how to connect, but you connect once and you're connected always. So you connect to the WI FI and then, you can show up. You can connect at a Link in Queens by your home and go to work in downtown Manhattan or Staten Island and be connected to the link there.
It's one network. I'm going to turn it over to KEMPB. Kevin.
Thanks. I'm work on the product team on Intersection, working on Link. A lot of the products we've built I've helped define the requirements for and go through iterations. I want to keep this informal.
If you have questions, feel free to raise your hand and I'll call on you. Hopefully, we have a slide that addresses it, but if not, we can kind of live figure this out. I'll hand a mic to you or something. I think what Ruth mentioned is the most important feature of the WI FI, being able to connect once, giving your email address and never having to do it, again.
This is just one time. So if you scroll down it's really simple. The same way to sign on the for the WI FI here. You go to your settings, select the WI FI setting in the device.
This is an iPhone screenshot here. But you would select Link NYC free WI FI as the network name, and then, get prompted to this browser, a captive portal network assistant. And from here, it's really small so I'll talk through it. It just says enjoy fast, free WI FI, enter email address, continue and there's some disclaimer copy on the bottom with the privacy policy and terms and conditions and that.
If you type the email address in, if you're an iPhone user, you'll see the screens on the left, which says good news. And I can't read the rest. So I'll go over verbatim. It says, you have access to our encrypted WI FI.
To do so, you have to download a private network key. And there's two called actions. One says download and the other is skip. If you skip, you get put on our regular free WI FI.
If you download, you get to your operating system settings, which is install profile page. And what happens is a private network key actually gets installed in your operating system which then encrypts the traffic from your device to the link. It's more secure than your other normal public WI FIs that you would use. It encrypts the traffic from when you're using it.
And this is for iPhones, works on tablets, as well. And we're trying to figure out how to roll this out for Android users. If you were an Android user, you would hit connect and you would connect and you're done. And that's the one time you have to do it.
And just for folks who are here, we have how to connect, sort of, handouts. So these are on the table. There's some in braille and there's some just in large text that outline exactly what Kevin just went through on the screen. Yeah.
So our link WI FI users, we refer to them as subscribers, it's an opt in basis. We could call any New Yorker, really, a user because if you pass a link, maybe using content or ad. Technically a user, we call them subscribers. And we deployed, originally, in January 2016.
And since that date, we've gotten 3.8 million users, go through that onboarding flow I've showed you guys. So we have that's our current number right now, and it's increasing every day as we put new links in the ground. And today, this is probably behind since I updated the numbers yesterday. But we're at 1,530 active links.
And I know there's two, one up on the corner of 38 and Broadway and one on 37th and Broadway. So we'll get more into that in a second. But to jump ahead a little bit, the tablet that you see right here, I just pulled it out of the Link out of the corner over there. If you happen to walk over there, there'll be a big hole in it.
That's where this came from. But each Link has a tablet that looks like this. It runs an android operating system on it. So it's customized and runs off of AOSP.
We leveraged a screen reader. I'm sure everyone here is flash, but if not, it's a screen reader technology. We'ren O the latest version of Google's Talk Back, which is great. The voice is legible and it's really great.
So it comes fully baked with that. So I'll download the features. I'll demo that in a bit. Teaser.
Thanks, Kevin. So when we were building Link, we wanted it to be something that makes accessible to all communities and becomes a beloved part of a New York City community. If you want to go to the first slide. First and foremost, that meant we were designing the physical structure with accessibility in mind.
As Ruth mentioned, it's 9 feet tall, but designed to be very slender on the street scape. And it's very smooth on the edges. There's no impediment sticking out into the sidewalk. It blends into the city scape.
So we're proud of that kind of forward thinking urban design. But also, the tablet that Kevin referenced here is at the appropriate height of 48 inches above the sidewalk. To allow for accessibility there. We also have the two 55 inch digital displays.
They apply the messaging, we do community board announcements, weather, things like that. But it also provides the ads, of course, that fund the infrastructure for this project. Each Lynx also has beacons inside of them. So this allows us potential for collaboration with third party collaborations that can help us provide much more precise location information for those third party tools.
So it's one of those aspects that Ruth mentioned of a forward thinking feature in the structure that can help enable future technology and other things that are being built to help finding throughout the city.
Sorry, just to jump on that, I think it's a cool technology we have on Link that we haven't been leveraging to the full capability. So folks like you guys all in the room, if you have any interesting ideas or you work for a company or friends work for a company, we have beacons all across the city. That's kind of the ethos we have at the company, be a part of the community that's useful for us, people who live in New York City that haven't capitalized on the full potential yet.
Yep.
Any other thing to note, obviously, our website is well into our onboarding experience that Kevin mentioned. That's updated, as well. The tablet itself, as you can see on the photo here has 911 button. USB charging ports and headphone jack with braille and icons to indicate where those are.
The 911 button itself, as we were initially designing the structure, we worked a lot with MOPD, the mayor's office of persons with disabilities office to get good feedback. They mentioned the 911 button itself, there was a potential to have sort of accidental presses. So we added a rim around it to prevent accidentally pressing the button. But we also do have a two press system.
You press it the first time, you'll hear an audio message and a written message that will inform you that you have to press it twice, which Kevin, go ahead and do it right now.
We'll have this here so if anyone wants to play with it after, you can check it out. So, yeah, the rim is here, and the pictures don't do it justice, but the key pad here, it's the same as the old pay phones had.
Your emergency call to 911, dialing 911 in a nonemergency situation is a crime. Double tap the touch screen to cancel this call.
That was a recommended feature from the NYPD to prevent prank calls from people walking down and pressing the button.
And as you can kind of tell, it came from the speaker that's located from here. So if anytime you have headphones plugged in, it will make that announcement and show up. So that's
And the other piece, too, each tablet assembly is equipped with a hearing loop. The enabled devices can have amplified hearing that comes out of that, as well.
All real tablets do. This one, actually, doesn't. I got it from the office today.
I thought you pulled it from the street, Kevin?
The ones in the street, I left that the ones in the street do, yeah.
Yeah. So I think the most part where we've done a lot of customization is around our talkback feature that Kevin was introducing. And I think he can walk you through the demo of how we apply talkback to our specific android, very customized, operating system.
Yeah. So the biggest thing that I want to call out is with any good product, it's important that you do user testing with diverse user groupses. A majority of the features you're going to see now and I'm going to walk through with talkback came through feedback from bringing folks to our office. To understand how real people would use the tablet and use Link in general.
I'll call out certain things, little tidbits I found interesting that came from user testing that we set up. So to kind of jump in first, the way to initiate talkback is using headphones. So we actually have this nice speaker here. So I'm going to try not to do it too loud.
Just so everyone can hear what I'm kind of doing here. And see it on the screen, as well.
To enable audio accessibility, mode one and then press pound. You are now using the tablet with talkback Android Accessibility Service. To disable Talkback, unplug headphones at any time. To close this tutorial, press any key on the key pad.
That's just like a like a two minute tutorial that it runs through where the actual buttons are, where the USB Ports are at the bottom, that are actually being used right now. Charging the phone right here. Which is fun. There's another outlet if anyone wants to plug their phone in.
As it said in the prompt, if you touch anywhere on the screen twice or press any key, it just ends the prompt to start over, you just press two. So I don't know if the speaker is loud enough right now or you want me to use the mic. Tell me if it's not loud enough. Put the mic on?
Cool. I'll stop talking and let the tablet do the talking for a little bit and swipe through some features. And if you want me to do anything in particular, raise your hand and I'll try it. And just one more thing.
It's the same
Double tap the screen to continue. Resume button.
As you saw me do, it works the same as Talkback and Voiceover on your mobile phones and tablets and things. So selecting an item, you tap on it. And to read an item, I should say, you tap on it and to actually select it, you double tap anywhere on the screen. It swipes it through a few things and have you guys understand it.
Get super fast WI FI right now. Free calls in grid. Maps New York, local, weather currently clear. 74 degrees.
8:00 p.m., clear. 71 degrees. Social, map, free calls. Phone dialer.
So something I want to call with the dialer here. I'll kind of tease, again, something in a cool feature I think we have is all the feature the gestures that Talkback comes with, double tapping, and swiping to the top, and swiping left and right and all of those things, we mapped all of those gestures to the key pad. If you look up on the screen here. One on the key pad, actually, slows down talkback.
Three, speeds it up, four moves to the previous, five select and so on and so forth. This came from a direct user test we did. The user we were testing with found it really difficult to use the gestures on the touchscreen because he normally just used it on his phone and it was confusing and weird to swipe and do stuff like that. So we thought, well, the key pad's not being used on the Talkback
So there's a time out for activity.
That's something we should've set for longer. So for next time, I'll write that down. The point of the session is to end what the user's doing if someone has walked away from it. And this clears the data that's there.
If the user were search for something in maps, after that, you know, 30 second window the system just automatically clears out any search they did and closes all of the apps and starts everything fresh. I thought it was really interesting we did that. It was kind of figuring out awe new way to use a kiosk with talkbacks. We did a bunch of research with ATMs and ticket kiosks and things like that.
And none of them had done that with the key pad. So we thought it was intuitive and did this and we published on our website and things like that. We can share knowledge. When you open the dialer up, we do the shortcuts.
It's easier to type out on the key pad the user could type out here. Or use Talkback and swipe through.
9WXYZ, 7PQRS. Double tap to activate.
Anyone want to see any features in particular or anything? You sure? This is your last chance.
Home button. Double tap to activate. Double tap transit update in grid. Double tap to act violate.
Another feature we came up with from user testing was actually number eight. To initiate a phone call to the LinkNYC support team, this is a one click call that the user that we were testing with, they weren't tech savvy, so they found the interface kind of confusing, we thought this could be a good way for them to contact support or set up WI FI or something like that to get them in touch with our support team.
Yeah. And I think the tactile key pad the way to navigate the screen with the key pad was helpful for the users you were referencing, Kevin, that don't use Talkback or screen readers on their phones. Having something to touch where you press sort of one key to go up and one to go down was a lot more intuitive for them. So it was really important way to get to, you know
Your session will end soon. Double tap the screen. Resume button out of grid. Transit updates.
Double tap to activate.
Pretty straightforward. And we'll let you play with it in a second.
So just flagging one of Kevin's earlier slides. We're seeing with the 1,500 links in the ground, we're seeing about 40 talkback activations a week now. When we're done, the project will be 7,500 links like that. Okay.
When we're done, it's going to be 7,500 Links. So we are still very early on in the project and those numbers will continue to grow. As I think both Emily and Kevin were mentioning, one of the biggest things we understand about our project is we're on the streets of New York city and New York is the most diverse place in the country. The Bronx, and Brooklyn and Manhattan, those are unique on their own.
We try to get out in the community as much as we can and take feedback and make changes and help make it a part of the community. So I've presented to over 35 community boards, we meet with groups all the time. We've made changes over the past couple of years based on community feedback. As Kevin said, another example was when we first launched, we heard that the ad screens, which we should also point out pay for the whole project.
So it was referenced, but it's really important. So the two screens on the sides, the two ad screens pay for make enough money to pay for the whole project to give free WI FI, free phone calling, free Talkback to anyone that wants it. We heard that the screens were bright, so we developed an ambient light sensor so now the screens get brighter during the day and darker at night. We're trying to learn on things like that.
This is just a slide to talk about some of the groups we've talked to. In relations to accessibility, equal entry has been amazing. We're always looking to talk to new and interesting groups every day. Trying to think if there's anything else we want to mention.
Another part of the revenue aspect, we actually split the revenue with the city 50/50. They're getting more money to do other projects, as well. We're all really proud to work on the project. You're welcome to come try the tablet.
We're going to have to share that mic.
If you have a question, I'll run the mic over to you.
I want to hear more about your observations, initial design work and then your observations of the sight impaired community. Taking advantage of this. It's braille enabled, has the audio features. So the design step and what kind of feedback you're getting from the field now.
In terms of usership.
Sorry, do you mean design of the kiosk itself? Or the software that we built? Or both?
I guess, both. I'm thinking of the sight impaired user community and the engagement, you know, from the design step. And is this community actually taking advantage of it? I guess that's ultimately
I could take that one. For that community, kind of, like, Ruth was alluding to, we've kind of built off the book partnerships with some groups of these the groups, I don't know if you go back to the slide. And we try to go to events like this and hear feedback from the field. It's not as easy because it's not like a website or an app where we can easily get feedback for something.
Because a lot of our users are transient. So they kind of walk by, do something and leave. And we may never hear from that person, again. We don't know how old they were, if they're in New York, anything about that.
It's difficult to figure that out if you can imagine. To my point earlier of bringing in diverse user groups, when we deploy something new specifically, the software, because we don't really deploy changes to the hardware unless completely necessary. And Ruth or Emily's nodding her head. One of them could tell you the rules we have around changing the hardware with the city.
One of the things that we do with our development teams is we layout three or four personas and then we try to bring the people in. Whether it's through community groups like these or friends of friends or we use Craigslist a lot, as well, we'll say fill out this form and if it's, you know, an 80 year old male who is in a wheelchair or something like that or tech illiterate, whatever it is.
We'll test hard core at them. We'll have this great team that comes up with test scripts. And we have all of these questions we want to get answered. We try to define down to one or two things that can be tangible and easy to change or to understand, I should say.
So one big thing that came about all of that was the tablet that you see here today wasn't in the original design that we deployed with. It looked much more like Android when we first deployed it. But then early on in the process, we brought in folks that were lower or no vision and started testing it and found it impossible to use. So the touch radius was really small.
If anyone has an android device or a Nexus tablet, it comes with a drawer. It comes with a drawer at the bottom. And we only had four apps. It's not like when you click the drawer on your phone, a huge screen pops up, it was really just at the bottom of the screen.
And the users were feeling around and there was nothing there. Our first questions were how to make the buttons more touchable. That's why we came up with the tile framework as we refer to it where the touch radius is, you know, four or five times larger than it used to be. It was easy to quickly validate those things.
We came up with a bunch of designs. Circles, squares, pointed corners, not pointed corners, did all of the things and then constantly for weeks and weeks and weeks and brought in different kinds of users and had them test it and give us we film it and kind of have them give us their feedback and ask them questions, how they feel, if it's usable. What changes would they want? And that's where the features come from.
I hope I answered your question. And we don't only do that with this, we do with kind of all of the products that we deploy at Intersection. We've kind of created this bug of needing to be to bring in users because we do a lot of other smart city tech. And the LinkNYC team has been proponents of talking to users, right?
For when we go to talk to executives, it's much easier to say, all of the users want this thing. Rather than, two people in the room that are sitting in a conference room thought of this idea and we think it's going to work.
Right. Yeah. And just on the physical unit, from the very beginning, we talked with a lot of users, we brought in, you know, we worked closely with the mayor's office of persons with disability and somebody from the New York Public Library, so that when we went to production, we had something we felt confident in. And we're 2 1/2 years in and we feel confident in the product.
So but yeah, it's very difficult to change something once it's in the ground. You want to get it right beforehand.
You guys are more familiar than I am. But what are the rules and regulations of changing the hardware itself with the city?
One, within our contract, we will no, that's a software answer. Ignore that. The hardware outside, the outside view of the Link, we had to get it approved by the city, the design commission, anything that would be changed that would last longer than a year. So a physical change forever needs to go back to the design commission.
So we worked really hard to get it right before we went through that.
And Ruth has a really interesting job at Intersection where she has to go and get all of these things approved with the city. Changing street, furniture, even if it was the way that the way the buttons were laid out or utilizing this hole down here could take however long the city wants it to take.
One thing I will say, we did get it approved by the design commission. And two years ago, LinkNYC won a design award from the New York City Arts and Design Commission. And that's the first time that a piece of street furniture has won that award. So, yeah.
So you talked a bit about Talkback and how it works with the appliance. Were there any other kind of assistive technologies that are enabled on the device and available to people, screen magnification? Any kind of refreshable braille support for anybody with a portable device with them?
That's a great question. And I forgot that because I didn't have my notes in front of me. But yeah, we do have a few of those features that you mentioned. So down in the left hand corner, there's a settings there.
So this is where we branch off and did our own thing. We got rid of all of the settings that Android comes with and built our own. So here, we have at the top it's a brightness control so you can turn down the brightness or turn off the brightness. You can invert the colors here, and that works across the whole operation system.
And this is one thing that is wiped out after a session. It would just come back with colors. I find the directions difficult, but they're Android's stock directions. Screen magnification so you can come in and zoom in on this.
I think you said connective braille devices. We don't have support for that. Because right now, the only way to utilize the actual tablet computer is through the audio jack. And that's the only out mechanism from the computer itself.
Because the USB power down here actually just goes to a power cable. It does not touch the computer. When you plug in your phone, like Amy just did, we're not wiping out your phone and stealing data and pushing network to your device. And it's great that I have this tablet here.
I can actually show you guys that if you cared enough. I hope that answered your questions. Cool.
So is there any way for deaf people to call 911 on that is my first question? And my second question, is there video relay service for 911 or any other call purposes?
Yeah. So at this point, we've been working with the DOIT at the city. And the police department. They're getting ready to roll out text to 911.
So as they're rolling it out, we've been having multiple meetings with them so that we hope we can roll out, as well. This is a completely bespoke product. So even when they roll out, we have to do engineering and software to be able to activate at the same time. But that's what we're working towards.
So we hope that when it goes live, we'll be a part of that. And then, we also have been talking with them they have a video relay service for 311 they're started to launch, the Mayor's Office of Persons with Disability. And we've met with that group and we're working on how something like that could work. They themselves are in a bit of beta.
They have one person that answers the phone. We don't want to put it on a link and have thousands of call locations they could get overwhelmed. We're talking to them about all of those ideas.
And to kind of follow up on that, there was a 311 up here. We think it could be great to have the video relay service through 311 services. And there is, actually, a camera right here. I should have mentioned that earlier, too.
I'll mention that in a second. But there's actually a front facing camera right here, too. So we have the hardware to support it, which would be probably the biggest hurdle if we didn't. And so that's exciting.
We've been working with DOIT, but because we've shipped out so much AOSP, we have to do a lot of work to utilize some of the video calls we need to. But I'm not
I just want to clarify one thing. We provide access to 911, but 911 has to be able to answer what we're talking about, right? So 911 in New York city is building text to 911 so they could answer a text. If we had it, they can't answer it right now.
And those are two separate things. The 911 texting. And, again, because this is AOSP and an Android, it's great that we can add a text service to it. That's something that we're in development with and testing, which is pretty exciting, as well.
So we're looking to add a tech service that you can actually roll out their service that will actually be able to text them. And I don't know if we want to mention the call box tapping, you can do that
Yeah. Yeah. It's actually something that we've been hoping to reach out to the community and understand. From what we learn more about what we know.
But there's the call boxes where you can call the fire or the police and based on the tapping, either two tap or single tap, it'll call either police or fire. And come to that exact location. So that is the beauty of the kiosk is we're a static location. You know, even if you would do call and there's no, you know, voice going back and forth on the call, they still know the call is there.
911 has to end the call. They'll send someone to the location. And you know, either way. Yeah.
Yeah. So sorry, and then the in and out speaker is at the top here. So that's where you can kind of feel for a voice and also tap to let the operator know that you're there.
Sorry a follow up question. So then, for video relay service, we have to wait until the government sets up those systems instead of using the current video relay service apps that are already being used? Because this is through the city specifically? Is that right?
I'll touch on that a little bit. Sorry, to clarify on that a little bit. There's two video relay services that we want to provide. There's one, which is a 3 in 1 provided, which would provide access to city services.
So that's a service that NYPD rolled out and we want to integrate that. And two is video relay services. Currently, our app for free calling is a Vonnage telephone app. And we are looking to currently deploy a video relay service to make regular phone calls.
So not to 311. So that isn't relying on the government, that's relying on our partners and deploying them here where, you know, it doesn't require a log in because we don't want users to log in with personal data and things like that. So we're trying to figure out the logistics and path of requirements on that.
If I could ask and this is fine to do afterwards, we would love to hear feedback if the tapping system is something you had ever heard about, you know, or if that's something people talk about now. Just as an aside.
Yeah. And if you have any apps that you really like for video relay service. Because right now, we're in conversations with a handful, and we would want to know from a user's perspective what they prefer. So happy to chat after.
And just for reference, the two I think we can say is fine, Sorensen and Purple are apps we've been talking to.
And the other one was Glide. Love to hear sort of preferences from the community, as well.
Got an online question. A voice. This is from Jonathan Katz. He asked, how did you design for cognitive disability?
Both intellectual and developmental learning disabilities. And have you gotten feedback from people with cognitive disabilities?
Well, one thing specifically to dyslexia, we on the tablet, which you'll see if you come up to it, we always try to have imagery, as well as words, and minimal words because we're concerned ability multiple languages. There's a symbol for a phone. When it says maps, there's an image for the world, which is what Google maps uses.
Yeah, and to that point, we use a lot of material design assets to keep consistent with the Android look and feel and because we like their work. So you can see all of the iconography here. And all of the matching iconography is kind of small for everyone who is not as close as I am to it. But all of these icons here are custom built or something that we've that's an industry standard for iconography we've done some user outreach with that, too and tested our tablets.
Brought the tablet.
So hi, I'm very interested in the design and development of the disability functions. I'm curious of how you've divided the accessibility work. And if everyone on your team is knowledgeable about accessibility or how you've educated your team about accessibility work?
Sure, I can take that one. I'm the senior program manager for Link, I touch a lot of different parts for it. But one of the hats is the accessibility coordinator for LinkNYC. And one of the things that's important to do is to provide training every year to everyone that works on the project.
Specifically, the developers and designers and Kevin's team who he does product development, design within the software developers. The people who are actually writing the code need to be thinking about everyone when they're doing it. So we do an annual training. But in addition to that, our company Intersection and all three of us are part of this.
We do something called communities of practice. So sort of in our spare time outside of our day jobs, we get together and have a technology tech accessibility community practice. We come together once a month. We talk about sort of new technologies that are out there that we're hearing about.
Hear about other communities, we do trainings from outside speakers. So it's a way for us to make sure we're learning more things about the community.
Visually impaired of their annual I forget the name of it. Conference.
So we bring our sort of members of the team out into the communities, too, so it's not just Kevin helping to design it but people who are building it who could think of a new way to put together the Android code to solve the solution to us who doesn't write code.
And deeper than that, at our core, like, when we're coming up with requirements for a new app that we want to add or something to a website or a change to the onboarding. It's kind of at our core that requirements based around inclusive design and accessible design. We have a really strong design team who really cares about it, as well. So a lot of it is led by them.
Where, you know, I'm a product manager. So I'm not always doing the design or doing something. And then, you know, I know that if I write a requirement that that designer then designs with accessibility in mind. And that I never have to really check the colors to be compliant because I know they are.
I don't have to go double check that work because our color palates that we use in the design framework that we have is Scalable and is accessible. So we try to, kind of, merge that, then, from the development life cycle period from design to dev. So we talk about it a lot in the meetings and make sure our QA engineers understand what tools are available to them to validate that things have labels and things are color compliant and things like that.
So really, you know, I'm both the gate keeper and the gate closer in a lot of projects that we do on Link. So, you know, we don't always pass a ticket or pass a body of work if it's not accessible. So, yeah.
And even if, you know, we still also know that we don't know everything. And so, we do an audit often. So Equal Entry has been helpful to us.
And we fully understand that software isn't perfect. Especially ours. So things break and sometimes we're not perfect. But we're always open to kind of pushing new stuff.
That's one of the amazing things about having a piece of technology on the street compared to back in the day or DOT way finder. When it's in the ground, it's in the ground. But we have the ability to be agile and change and learn and improve.
Hey, I'm Matt. I'm product designer and kind of to add to that question, how does your design team structure I think this is something you asked, but just to say it, did much of the design team have experience designing successful? Or is that something that started with you?
So for the first question, we have a squad model. So I'll back up so Joly can we have a squad model for all of our development teams. Each of the development teams who work on a product or a core set of features is cross functional. That means, they have a product person, they have engineers, have QA and a designer that's dedicated to owning design for that work.
So we found out to be really successful to because it allows them to immerse themselves in the work and create the color palates they need and they know are accessible and things like that. That's the first part of the question. The second part, do we hire folks who have accessibility backgrounds? not on the product team right now, that has five or six designers and ten or so product managers just working on intersections projects dissertations around accessible technology and things.
And it was a natural fit. They weren't hired because of that, but it was something in the bag of tools. Visual, that's for you two. Me, again, sorry.
You mentioned that with the hardware design, you did a lot of research looking at kiosks around in other countries and for different purposes, that sort of thing. I'm curious as to where these findings and conclusions might be documented just so that, like, if somebody else is making a kiosk somewhere else and they want to know what you've done, how can they find that information? What kind of general patterns have you found ?
Yeah, my comment about that was more sorry, I'm making your job difficult. But my comment about that earlier was less about the design esthetic and more about the feasibility of the interface. Okay, cool. So we've never to my knowledge, we've never really
We should put a blog post together about it.
Yeah.
For the world to see.
It's true. We've kind of long said that we've it's one of those things, like, we should write a blog. You kind of never get to. But we totally should publish it on our website and make it available of our findings because what we found was that there weren't much industry standards around kiosks.
We looked at ATMs, ticket kiosks, that's both in, like, the subway and airports and but also at, like, movie theaters and things like that. It gets lost to you how many times you touch the screen at a kiosk, right? And that they're never the same. So we didn't really find any common practices.
And we kind of just picked things that we thought were useful and interesting. And that alert I forgot to tell you about was an alert that's read every time a user starts a session and doesn't do anything for seven seconds. The speaker automatically says to enable talkback, click one and then pound. So we found that some Chase ATMs were doing this.
And we thought it was catching on a few years ago to the ATM community there of banks. And we felt like that was right to kind of piggyback on to that and have that as one of the core features to enable talkback with a key code. They do a really good job of this and could learn something from that.
Just to add some context and color to that. So I work at Google and I know the material folks and they're doing a great job, but the kiosk interactions in particular I'm curious about not because of my daytime job work. But because of the work I'm doing with this gentleman right here at W3C, we're in the accessibility guidelines working group. And we're looking at how to move the guidelines forward.
So we have WICAG, it's still very solid and set in a structure that expects web browsers and web pages not having really changed since it was originally written. One of the things we're looking at is scope of accessibility guidelines and technology. And any research that you have that could inform that would be awesome.
We should definitely talk after this because that would be great. Cool. Anyone else have questions while I'm over on this side of the room?
Can we get these in the subway?
One of you guys want to take that?
That would be amazing. We have a project that is specific to replace the pay phone. So when you're dealing with New York City, you know, we have a specific agency that we have our contract with and a very specific place within the city that we're allowed to be. But we get questions like that a lot.
Can this go in a park? We would love that, but we're not with the parks department. So we're just with DOIT right now.
And Intersection, our company, does have other products that are not exactly like Link, but they're similar, they're digital kiosks in public spaces. You know the kiosks that are on the subway platforms, we wrote software that runs on those for a while. And then, we also a transit product that we've deployed in Chicago, in SEPTA, in Philly, and other places I'm obviously not on the transit team. Yeah.
But those don't actually emit WI FI. But as a subway rider, I hate transit wireless and not because I work for Link, because I think it's really bad. Yes, I would love as a user to have Link WI FI in the subway.
Other interesting tidbits. Link was started here in New York, for New Yorkers, by New Yorkers. But since then, it has taken off. And we do have Link in the UK.
We are in London and in Leeds. We'll continue to grow there. And we're bringing Link to Philadelphia to downtown Philadelphia, which has the second highest population of downtown anywhere after New York. We're excited to grow.
If you travel to either of those places, the WI FI will work instantly there, as well, and all of the same accessibility features.
And as a New Jersey resident, I have to plug that Newark is getting them, as well.
It is. Yeah. And we have one on the West Coast, I think in 2020 or 2019, I think we've announced Link LA, which is part of their expansion of transit, as well. So there's actually going to be transit products that come along with that.
You almost get your wish, but you have to go to LA.
There are some things we should've said earlier. The tablet you're looking at now is the everyday tablet. But there are special features from time to time. Also accessible.
We just finished working with participatory budgeting. If the council member chooses to set money aside to vote for things they want in the community, such as a new park or whatever it may be so you can vote for that to you could register for the general election the few weeks leading up to. You could register for health care the last few weeks it was open. We're always trying to make it useful and interesting to the people that need it.
And this large square at the top of the tablet screen over here is what we utilize for that. It's a promo area. A picture of the New York skyline, and the same directions I showed earlier. That we showed earlier for onboarding on to the WI FI.
But this is the area that we take over for many fun things that, like, Ruth is mentioning. So if you anyone here has good ideas or, again, wants to collaborate on something like that, it's always an area that we try to do something interesting. We did for the past two years, we've done a really fun Call Santa promo. We found a free service where it's just a voice mail for Santa Claus and tapping a button here and initiate a phone call and it has this fun voice mail and we get a lot of engagement out of it.
There were a few people that called on Christmas. And they didn't like what they got. Besides that, it's fine.
And that's classic New York. A 13 year old telling you they didn't get what they wanted from a street computer. So that's kind of the people that we love to work for.
Yeah.
Any other questions before Thomas cuts me off? Three, two all right. Well, thank you guys. It's been an awesome presentation and thank you, everyone, for coming out for our meetup.
Next meetup will be the first Tuesday of June. We'll be publishing that out. You can go to our page, we have a Twitter page. And the previous presentations are on YouTube.com/A11yNYC.
This presentation that was live streamed the same URL works to go back and watch it afterwards. I want to plug, again, there's instructions for setting up the private network if you're on an iOS device, I use that on my phone, and it's been awesome here around the city ever since I've set it up, I'm always on the Link WI FI and right outside my apartment, actually, doesn't have cell service, but I get connected to the WI FI automatically.
And it's like, wow.
In your apartment? Does it reach into?
I don't get yeah. I wish. But yeah, it's really great. And I think just to call that out, again, that those instructions are up here at the front.
So thanks, everyone. And feel free to come try out the Link up here and discuss a network afterwards.
Thank you. [ Applause ]
Your security is important if you have an iPhone, you should definitely do the extra two steps, three steps to install the profile. Because, you know, why not? Have some extra security in your life.
Thanks.