
Lessons on broadening engagement in accessibility innovation
Raquel Ronzone of the Howe Innovation Center says the center is an ecosystem support organization situated within Perkins School for the Blind, the first and oldest School for the Blind in the country.
Their goal is to create a more accessible world by connecting the disability and innovation communities. A key part of this is broadening this community by showing where and how everyone, regardless of their role or their sector, has a role in advancing accessibility.
Transcript: Lessons on Broadening Engagement in Accessibility Innovation - Raquel Ronzone
Hi, folks. Tonight we're gonna be talking about broadening engagement in accessibility innovation. Thank you all for being here. Thank you to our event organizers, and more.
My name is Raquel Ronzone, and I focus on partnerships and Disability Tech at the Howe Innovation Center at Perkins School for the Blind, based outside of Boston. As a visual description, I'm a mixed Filipina woman with short black curly hair and today I'm wearing a black blazer, a very bright orange college shirt, and black trousers. So what is the Howe Innovation Center? We are an ecosystem support organization about two years old, situated within a nearly 200-year-old organization.
Perkins School for the Blind, the first and the oldest School for the Blind in the country. Our goal is to create a more accessible world, by connecting the disability and the innovation communities. And a key part of this is broadening this community, showing where and how everyone, regardless of their role, their sector, has a role in advancing accessibility. This includes people who will new to accessibility.
People like myself. Who, before joining Perkins about three years ago, didn't work in the disability space, despite having a personal connection to Perkins' mission. I was born with retinopathy of prematurity, as a result of being born four months premature. That means my retinas didn't develop typically.
I've had about 10 eye surgeries, I wear glasses, contacts, have situational help, and in doing this, I want to bring more people into this conversation and show where and how they can get involved. So when we talk about a Disability Tech innovation ecosystem, what do we mean? We can think about it as one centered around people with disabilities and their allies. And around them are all ecosystem stakeholders.
That includes startups, academia, researchers, investors, corporates, test beds, governments, and more. Overall, we want to ensure that better co-designed products make it to market. Products that meet the real world accessibility needs of the disability community. So how do we do it?
Tonight, as part of our conversation on broadening engagement, we're gonna share three ways that we at the Howe Innovation Center have found success in broadening this community. So first is by reaching technologists. Stepping beyond the accessibility space to talk to the people who are building tech, informing and advising on tech policy. That includes people who are doing it currently, as well as preprofessionals.
Students from grade school, high school, college, and more. So how do we do it? First, we deliver programming that solves entrepreneurs' problems. So, for example, we at the Howe Innovation Center recently partnered with Mass Challenge, one of the world's largest startup accelerators, headquartered in Boston.
We featured a Disability Tech carve-out among their cohort of over 100 startups. Additionally, we offered human-centered design training to all 120 startups in their cohort, because we know that accessibility is important to embed across sectors. So we wanted to reach people who are building med tech, fintech, and more, and show them that accessibility matters. Next is a project that we're undertaking called Pilot with Perkins, to understand our own innovation needs.
And to figure out how do we matchmake with corporates and startups working in that space. So, for example, we're taking stock of our 3D printing needs on campus. Where and how can 3D printing and other forms of tactile information unlock accessibility for our students? And then how do we engage corporates and startups to staff that need?
Additionally, we're learning to speak the investor language through our research. Our first publication was a whitepaper, focused on the Disability Tech landscape. In it, we based our analysis on work from McKinsey and company, and found to date 2,500 Disability Tech companies worldwide. We organized this information by where the companies are.
Their country or their state. Their end user community. Who is the community being served by this. Whether it's the auditory, visual, mobility, or neurocognitive communities, or multiple communities.
The technology used, whether it's AI, robotics, or more. Additionally, we want to get in front of the tech community where they are. At tech conferences and events. So to that end, we've had the pleasure of going to TechCrunch, CES, the Move Mobility Conference about transportation, and more.
And finally, we've had success in engaging local and online communities. By the tech that they used, like AI, through which we found the Boston generative AI community Meetup and its 4,500 members, many of whom anecdotally have never thought about accessibility and thought about how AI can unlock accessibility for people with disabilities. We've also had luck in finding communities through grounding tech principles, like responsible tech or humane or ethical tech. And through that, we found the All Tech is Human community on Slack.
And it's 11,000 members. All of this brings us to our first lesson learned: Own being the so-called "lone wolf" in accessibility. Because you're reaching new audiences.
Additionally, we also want to reach cultural organizations. Why? Because we know that disability is part of the human experience. And these cultural organizations offer a touchpoint, an opportunity, to engage people in this.
So how do we reach them? We engage with universities and schools, like project-based collaborations, semesterlong collaborations. For example, we recently partnered with a consulting group at Tufts University, based outside of Boston. We took an existing -- their existing discipline, business, marketing expertise, and we applied a disability lens on top of it, based on our query.
What is the national landscape analysis for adaptive furniture? And after a semester, they came back to us with a specific number. And now we know what that need is and how to meet it. On the next slide, we'll talk more about our collaboration with Olin College of Engineering, a group of computer science students who collaborated with us on accessible data presentation.
Additionally, we've had success in engaging libraries, museums, makerspaces. We seek out participation opportunities on panels, and we encourage others in this space to do so as well. Submit disability focused media for book talks and film club nights and more. We know firsthand that cultural organizations matter.
We're engaged in a partnership with the Museum of Science to inform their content and programming on disability. To that end, we've had two events to date. One focused on the disproportionate effect of climate change on people with disabilities, an opportunity to engage the STEM community, who might not have considered this before. And more recently, an event focused on the intersection of democracy and disability, and how people with disabilities can and should be able to participate in democratic systems.
An opportunity to engage tech policy people and government members. It brings us to our second lesson learned: Whatever the opportunity, the answer is accessibility.
For more on our Olin College collaboration...
On screen is a representation of the data collaboration that we did with Olin College of Engineering. We aim to present this data in multiple formats. So there's a map one can access by chart, table, linked through the data, as well as downloading this information. We've also taken stock of Disability Tech companies globally, in addition to by state.
California is leading, with Massachusetts as number two.
Again, the opportunity to engage in this information by pie chart, as well as download this information, engage with it by tables, and more.
Following this example, you'll see a sonification. [sound going up in pitch] The use of sound to represent growth in tech companies over time.
[sound going up and down] Disability Tech companies per year with a spike in 2017. And again, at twice the speed.
It's opportunities like this that we take, to take a layer of accessibility and disability experience, which we know well, and use it as an opportunity to engage with college students, who might not have ever considered accessibility previously, but are very well versed in computer science and more. Thank you. That's perfect. Which brings us to our last takeaway.
First, solve their needs. First. And then solve yours. We know in doing this work that our value as a partner comes from solving other people's problems.
And removing their friction points. And in doing so, we deliver on our goals, in addition to delivering on theirs. So how do we do this? We recommend you prepare others to pitch.
Make your case to them. And help them make the case to their higher-ups, their collaborators, their colleagues. Prep them with pitch decks, talking points, briefs, and more. And back it up with data.
Illustrate the value of your work and collaboration. For example, in our partnership with the Museum of Science, we of course know that more disability focused programming matters. And for the Museum, it matters that they get more and new attendees. Through this partnership, we can do both.
Finally, listen and respond. As a result of our broadening and deepening engagement with stakeholders across the ecosystem, we uniquely understand their pain points. And we're uniquely equipped to solve them. So we at the Howe Innovation Center are really excited to share that we're building two things: One is a user testing pool to streamline testing among the disability and the innovation community.
And next is a Slack community, to connect all of the global members of the Disability Tech ecosystem, creating a centralized place where they can share news, updates, job opportunities, job asks, mentorship offers, and more.
If anything that we talked about tonight resonates with you, we invite you to join our community. On screen is a QR code to join the Howe Innovation Center. Thank you. [applause] What helps to get people... Get more people on board with accessible innovation?
It's a good question and one that we face every day. I would say, to that end, we recommend making it tangible and speaking people's language. And I can share two examples. One that we learned and one that I learned along the way.
So one is... I speak to a lot of students. Grade school students, high school students, college students. And every time I speak to them, I take a baseline question.
I ask everyone in the room: Who has proximity to disability, whether their own or a loved one's. Who has experience or context for accessibility? And the third question: Who has ever used Disability Tech? And in the course of my presentations, and the course of speaking to them, when I unpack what that means, what each of these terms mean, disability, accessibility, and Disability Tech, which we define as any products and services that advance accessibility, it changes the conversation.
When I ask them, as a follow-up question: Who has ever used a text message? Who has ever used touch screens? These are innovations that came from the Deaf and hard of hearing community. And the mobility community.
Respectively. So touch screens -- that foundational technology that sits behind everything that we use today, came from a grad student who had carpal tunnel syndrome and needed to complete his thesis. So that made it real for them. So after one such presentation, when I talked about this, students who had said that they had no experience in accessibility, no proximity to disability, came up to me and said: We are student athletes.
And now of course we know what accessibility means. Because when we got injured, we had to go to the one dorm on campus that was accessible. And we had to explain to our professors why we needed extra time to get on campus. And as a way of making it tangible sort of in a meta way for their professors, they said: Come, professor.
Come take this journey with me. As I go from my dorm to your classroom. And you will understand why I need this extra time. So I would recommend making it tangible and speaking people's languages.
To try to find a touch point and a common point to make it real for them.
So just to give a little background, I try to make dev tools for people with disabilities myself. A bunch of things. And [inaudible] tools. I'm trying to actually get into more rooms and more classrooms and different places in order to like... Spread the idea of making adaptive devices.
What's a good method, do you think, of actually getting in contact with people and getting into rooms and things of that nature? Good question. I'm happy to talk more personally after this. I would say broadly there's a bottom-up and a top-down strategy.
So bottom-up would be: The people who are very much aligned and know that there's a need. That would be families and parents of people with disabilities. Teachers. Related support providers.
And more. That's the bottom level. Sort of topdown would be school administrators. The decision makers.
People who might have budgets and funding to control. People who might be able to make this decision that would affect a mass amount of people. I think the particulars would depend on what your production capabilities are. What you're interested in.
For context, we have an assistive device center at Perkins. And I'm happy to talk more about our thoughts there. Which include the question about scaling. So it currently serves Perkins students.
We make 2,000 adaptive devices for 1,200 Perkins students per year. And we're thinking about: What does that look like on a national market. So I'm happy to chat more.
What does it mean to talk about a disability tech innovation ecosystem? Think about it as one centered around people with disabilities and their allies. And around them are all ecosystem stakeholders.
That includes startups, academia, researchers, investors, corporates, test beds, governments, and more. In short, the innovation center wants to ensure that better co-designed products make it to market. Products that meet the real-world accessibility needs of the disability community.
Building the disability tech innovation ecosystem
They do these three ways. First, they go beyond the accessibility space to reach technologists, the people who are building tech as well as informing and advising on tech policy. To attract this group, the center creates programs that solve entrepreneurs’ problems.
For example, the center partnered with Mass Challenge, one of the world’s largest startup accelerators. They featured a disability tech carve-out among their cohort of over 100 startups. Additionally, they offered human-centered design training to all 120 startups in the cohort, because accessibility is important to embed across sectors.
Second, they’re doing a project called Pilot with Perkins to understand their own innovation needs. They also figure out how to pair with corporations and startups working in that space. As an example, Perkins took stock of their 3D printing needs on campus. Where and how can 3D printing and other forms of tactile information unlock accessibility for their students? Then, they explore how to engage corporations and startups to staff those needs.
They’re also focused on the end-user community. Who is the community being served by this? Whether it’s the auditory, visual, mobility, or neurocognitive communities, or multiple communities. The technology used, whether it’s AI, robotics, or more. Additionally, they want to meet the tech community where they are, such as tech conferences and events.
They’ve had success in engaging local and online communities with the tech that they used, like AI. They found a local generative AI community Meetup with thousands of 500 members, many of whom anecdotally have never thought about accessibility and how AI can unlock accessibility for people with disabilities. The center found communities through grounding tech principles, like responsible tech or humane or ethical tech.
The first lesson learned in connecting with these three groups is to lean into being the lone wolf in accessibility. It means you’re reaching new audiences.
Getting the most out of the collaboration
They also want to reach cultural organizations because disability is part of the human experience. Cultural organizations offer a touchpoint, an opportunity, to engage people in this. They connect with cultural organizations by working with universities and schools on project-based collaborations.
For instance, they partnered with a consulting group at Tufts University. They took an existing discipline at the university, such as business and marketing, and applied a disability lens on top of it. What is the national landscape analysis for adaptive furniture? And after a semester, the university came back to Perkins with a specific number. And now they know what that need is and how to meet it.
They’ve also collaborated with a group of computer science students at Olin College of Engineering on accessible data presentation. The data is available in multiple formats. They’ve taken stock of disability tech companies by country and state in the US.
It’s opportunities like this that Perkins takes the layer of accessibility and disability experience, which they know well, and use it as an opportunity to engage with college students. The students might not have ever considered accessibility while bringing their talents to computer science. The second lesson learned is that, whatever the opportunity, the answer is accessibility.
Additionally, the center is connected with libraries, museums, and makerspaces. They search for participation opportunities on panels and submit disability-focused media for book talks and film club nights, and more.
Perkins has a partnership with the Museum of Science to inform their content and programming on disability. To that end, they’ve held two events. One focused on the disproportionate effect of climate change on people with disabilities, an opportunity to engage the STEM community, who might not have considered this before.
The other event focused on the intersection of democracy and disability, and how people with disabilities can and should be able to participate in democratic systems. It was an opportunity to engage tech policy people and government members.
Expanding the community engagement
Perkins’ value as a partner comes from solving other people’s problems and removing their friction points. And in doing so, they deliver on their goals while delivering on their partners’ goals. Thus, the third takeaway is to solve their needs first, then solve yours.
Howe accomplishes this by preparing others to do the pitch. Make the case to them and help them make their case to their higher-ups, collaborators, and colleagues. Equip them with your pitch decks, talking points, and briefs. And show the value of your work and collaboration through the data.
For example, in Howe’s partnership with the Museum of Science, the museum wanted to get more new attendees while Howe wanted more disability focused programming. Through the partnership, they can accomplish both. Another key lesson is to give more than you get when it comes to partnerships.
It’s also key to listen and respond. As a result of their broadening and deepening engagement with stakeholders across the ecosystem, they understand their pain points and can solve them.
As a result, the Howe Innovation Center is building a user testing pool to streamline testing among the disability and innovation community. They’re also developing a Slack community to connect all the global members of the disability tech ecosystem, creating a centralized place where they can share news, updates, job opportunities, job asks, mentorship offers, and more.
Audio engineering by people who are deaf and hard of hearing
Keita Ohshiro is a lecturer at the New Jersey Institute of Technology who is a PhD student focused on accessibility and technology. Keita is doing research on audio engineering by deaf and hard of hearing individuals.
Transcript: Audio Engineering by People who are deaf and Hard of Hearing - Keita Ohshiro
My name is Keita Ohshiro. I'm a lecturer at the New Jersey Institute of Technology. Where I teach courses like user experience design or data analysis or programming. And then I'm also a PhD student there.
So I do research. On accessibility and technology. And today, I'd like to talk about my research on audio engineering by deaf and hard of hearing individuals. So before diving into the topic, I want to briefly share some background information.
I focus on people who are deaf and hard of hearing. Often abbreviated as dHH. By convention, in my research field, there are three common identifications. The term "hard of hearing" usually refers to a lighter degree of hearing loss, whereas deaf is lowercase d, refers to more severe hearing loss.
And the term Deaf with a capital D refers to a cultural identity. They often speak Sign Language as their native language. And today's talk covers deaf with a lowercase d and hard of hearing individuals. So dHH with a lowercase d. But I also understand and respect that some people feel uncomfortable with this lowercase d/uppercase D differentiation.
And personal identification varies. And personal identification -- there's no definitive definition. With that in mind, please allow me to follow the convention common in my research field for today's talk. Okay.
Then... Talk about audio engineering. Audio engineering involves recording, manipulating, and reproducing sound for music, podcasts, TV, radio, whatever. The typical workflow is recording is to capture the instruments, speech, et cetera.
And then you import the audio tracks into your computer and do editing. People use software called digital audio workstations. I call it "DAW", to perform audio engineering tasks. In editing, you try to make multiple audio tracks sound good as a whole.
And then the final goal is to produce the best sounding artistic product. So it's not just a procedure, but rather more creative and artistic work. Like... Two engineers can produce very different results from the exact same tracks.
This page shows the screenshot of a DAW. There are a bunch of rows. Each row shows one audio track, and its waveform, which is a visual representation of sound. For example, in podcasting, one row can be the audio track for an interviewer, and another row for an interviewee, another row for background music, and so on.
And then audio engineers do tasks like balancing track volumes, timings, stereo placement, equalization, inserting sound effects, and so on. Okay. Let's turn to the main topic: How dHH individuals do audio engineering. To explore this, I conducted interviews with 12dHH audio engineers.
8 working in music and 4 in podcasting. And I wanted to share some of the key findings. Many of my participants describe the persistent insecurities, due to their hearing. As one participant said: My ears can be a little deceptive.
Also, it took extra time and effort for them to conduct audio engineering. I had a participant who became deaf during their career. They said: If I didn't have the hearing loss, it would have taken half the time at least. Because I could trust what I was hearing.
In addition, some participants lack an innate understanding of certain sound concepts. For example, a participant born with a single sided deafness said: I can't ever really experience stereo sound, the same way that people with two ears can. So... What's their workaround?
One of the main workarounds is visual editing. To better perceive sound, they leverage visuals within a DAW. For instance, take a look at these waveform snapshots on the left. The top one is someone laughing.
And you can tell that visually, without listening. Because of this fishbone shape. And then the bottom one you can visually tell... There is a plosive sound, like a "p" or "t" sound, because you see that big spike at the start.
In editing, you can trim it down, so it doesn't blast your listeners. On the right, there's a stereo field view, a half circle with a lot of dots inside. So you can see how sound spreads, left and right. And these are just a few examples, but these visuals give deaf and hard of hearing audio engineers more confidence about what's going on with the sound, and helps them save their hearing energy.
Since they tend to get tired easily when listening. Of course, visuals can only take you so far. As one participant said: I can depend on my eyes and the graphic readout only so much. And another participant said: You do end up with a complicated guessing game.
So you can't see every nuance of sound. At the last resort, participants turn to their hearing friends. They ask peers to give feedback to ensure the quality of work. Pretty much every audio engineer does this.
But DHH audio engineers rely more on it. That said, asking for help isn't always easy. You have to learn how to be open and better at asking for help. And it can feel uncomfortable to keep asking for help, too often, too much.
You might need someone who understands audio engineering better, to get the higher quality feedback. Or... Plus sometimes you want to be independent, as a creator, without being influenced by others too much. So regarding the use of technology, it turns out that dHH audio engineers use almost the same technology as hearing audio engineers.
Like DAWs and plugins. One exception is the hearing devices. Like hearing aids or cochlear implants. Which can introduce its own set of frustrations.
For example, about hearing aids -- since most hearing aids are designed and adjusted for speech, rather than music, that contains a broader range of sound, they are often simply not good for music or audio engineering purposes. And finding an audiologist who is comfortable adjusting the settings for musical work is another challenge. Because it requires the right equipment in the lab and also the expertise. Another thing is how they learn and grow as an audio engineer.
Based on the research so far, I did notice a difference between the music and podcast engineers. All 8 participants in music came through formal education, such as degrees in music technology, whereas the 4 podcasters learned audio engineering and podcasting by themselves, through trial and error. They often developed their own ways of doing audio engineering. Sometimes not optimal, yet it somehow works for them.
And they felt that it's too much hustle to try out new tools or workflows. As they spend so many hours of learning and trial and error, and that might limit the opportunities for them to expand their skills.
So that's pretty much where my results stand right now. Basically to understand the current state of accessibility. And one of my future directions is to think about how we can use AI for this. For example, sound design tasks in podcasting, like imagine you're making a drama podcast, and you want to insert a footstep sound.
It seems simple, but actually you've got to think about a lot of factors, like sneakers or heels, wood floor or tile, walking and running. But each of these details totally changes the appropriate choice of sound. And those subtle cues can be tough to catch for dHH engineers, sometimes. So what if we can develop an AI tool that can describe those subtle nuances of the sound, and help them select and insert the sound appropriate for the scenes.
I'm thinking about those kinds of things. Okay. And this is my last slide. Before I go, I'd love to share one last thing.
Christine Sun Kim. She's a Deaf artist. Has an amazing show at the Whitney Museum right now. So if you are around this area, you definitely want to check this out.
Thank you very much.
In audio engineering, you need to use a lot of plugins, generally. Right? And these can be extremely helpful for the types of use cases you're describing. So, for example, for clicks and pops, just extraneous bad sounds, you could have something that automates those things away.
But if you're doing podcasts, or dialogue editing, it becomes very difficult. Right? And so I was curious. I just looked this up.
Since I haven't done audio engineering in some years. I wasn't sure. There's something called AudioShake, which creates clean, timestamped lyric transcriptions with high accuracy. And syncs and aligns that, the transcript, with the audio.
Right? So for some of your use cases, that would be incredibly invaluable, because otherwise, you wouldn't be able to edit the dialogue naturally. Right? Yeah.
Yeah. That sounds awesome. I have never used that. And I don't think... I don't remember if my participants mentioned that specific plugin.
And one interesting thing the people in the podcasting field -- I think because of the nature of the medium, because it's a new kind of technology, it's kind of a YouTube thing. You make your own YouTube... Content. Other individual amateur creators.
Many podcasting people do that kind of thing. So for them, finding the right technologies, finding how to use the plugin, how to use the technologies also is a big challenge. They don't know how to use it. There are big gaps.
The technology is there, or maybe almost there. But you know... You just don't have a chance to use it. Or you don't feel super comfortable trying out those things.
But rather than stick to the old... Some technologies... Some ways that are not super helpful -- some people even don't use automation of noise reduction. Which is to some extent a very basic tool.
But people just prefer to find the noise just by themselves, exploring all the recordings and trying to find these tiny things. And just delete them. Those kinds of things. By hand.
And some people do that. So... Yeah. The technology is there.
But how to use the technologies... They're complicated things. But yes. Going back to that plugin -- I think it's very nice.
And I would love to use that.
How audio engineering works
Audio engineering involves recording, manipulating, and reproducing sound for music, podcasts, TV, radio, and so on. The typical workflow is recording is to capture the instruments and speech. Then, you import the audio tracks into your computer for editing. People use software called digital audio workstations (DAW) for audio engineering tasks.
In editing, you try to make multiple audio tracks sound good. The final goal is to produce the best-sounding artistic product. It’s not just a procedure. It’s more creative and artistic work. Two engineers can produce very different results from the exact same tracks.
Audio engineers also do tasks like balancing track volumes, timings, stereo placement, equalization, inserting sound effects, and so on.
Background on deaf and hard of hearing participants
How do deaf and hard of hearing individuals do audio engineering? To explore this, Keita interviewed 12 deaf and hard of hearing audio engineers. Eight participants work in music and four in podcasting.
Many of the participants describe persistent insecurities due to their hearing. As one participant said, “My ears can be a little deceptive.” They also said it took extra time and effort for them to do audio engineering. One participant became deaf during their career. They said, “If I didn’t have the hearing loss, it would have taken half the time at least. Because I could trust what I was hearing.”
In addition, some participants lack an innate understanding of certain sound concepts. For example, a participant born with a single-sided deafness said, “I can’t ever really experience stereo sound, the same way that people with two ears can.” What’s their workaround? One of the main workarounds is visual editing.
To better perceive sound, they leverage visuals within a DAW. For instance, looking at waveforms, you can tell that visually that someone is laughing because of a fishbone shape. Another waveform shows an explosive sound like a “P” or “T” because of the big spike at the start. In editing, you can trim it down, so the explosive sound doesn’t blast your listeners.
These visuals give deaf and hard of hearing audio engineers more confidence about what’s going on with the sound. It helps them save their hearing energy because they tend to get tired easily when listening. Of course, visuals can only take you so far. As one participant said, “I can depend on my eyes and the graphic readout only so much.”
And another participant said, “You do end up with a complicated guessing game.” Therefore, it’s not possible to see every nuance of sound. As a last resort, participants turn to their hearing friends. They ask peers to give feedback to ensure the quality of work. Most audio engineers do this. But deaf and hard of hearing audio engineers rely more on it.
That said, asking for help isn’t always easy. It can feel uncomfortable to keep asking for help, too often, too much. You might need someone who understands audio engineering better to get higher-quality feedback. Plus, sometimes you want to be independent, as a creator, without being influenced by others too much.
Audio engineering technology and future research
Regarding the use of technology, it turns out that deaf and hard of hearing audio engineers use almost the same technology as hearing audio engineers. Like DAWs and plugins.
One exception is the hearing devices, like hearing aids or cochlear implants. These can introduce their own set of frustrations. For example, most hearing aids are designed and adjusted for speech, rather than music, which contains a broader range of sound. They are often simply not good for music or audio engineering purposes. And finding an audiologist who is comfortable adjusting the settings for musical work is another challenge. It requires the right equipment in the lab and expertise.
Another thing is how they learn and grow as an audio engineer. Based on the research, I noticed a difference between the music and podcast engineers. All eight participants in music came through formal education, such as degrees in music technology.
The four podcasters learned audio engineering and podcasting by themselves through trial and error. They often developed their own ways of doing audio engineering. Sometimes not optimal, yet it somehow works for them.
They felt that it’s too much of a hassle to try out new tools or workflows as they spend so many hours learning and trial and error. That might limit the opportunities for them to expand their skills.
That’s where Keita’s results currently stand. The first task is to understand the current state of accessibility. And one of Keita’s future directions is to think about how to use AI for this. For example, adding sound design tasks in podcasting. Imagine you’re making a drama podcast, and you want to insert a footstep sound.
It seems simple, but you’ve got to think about a lot of factors, like sneakers or heels, wood floor or tile, and walking or running. Each of these factors changes the appropriate choice of sound. Those subtle cues can sometimes be tough for deaf and hard of hearing audio engineers to catch.
What if there’s an AI tool that can describe those subtle nuances of the sound, and help them select and insert the sound appropriate for the scenes?
Access in action: Promoting inclusion and creativity
Indira Ardolic describes Tech Kids Unlimited as a non-profit organization that provides educational opportunities for neurodivergent students ages 10 to 24. They started off doing tech workshops about animation, digital art, game design, and web development. At some point, they spotted a huge gap in the growing community in the lack of gaining or sustaining employment.
Transcript: Access in Action: Promoting Inclusion and Creativity at Tech Kids Unlimited - Indira Ardolic
My name is Indira. And I run Tech Kids Unlimited. Our mission statement is on the screen. And I'll tell you briefly about what we do.
So we're a non-profit organization that teaches technology to neurodiverse youth ages 10 to 24. And I've been with Tech Kids for a long time, so I can say we started off as doing tech workshops about animation, digital art, game design, web dev, and we saw as our community was growing that there was this huge gap. And the gap is in the workforce. A lot of autistic people aren't employed or struggle to gain employment.
To sustain employment. And although there's a demonstrated interest in technology, there's just not enough support for that. So that's kind of where we're going and what we want to bring to the table. I started as a counselor.
Just a little bit about me and my background. Because it's like... Who is this person? It's me, Indira.
I have been there since 2015. I was like... At NYU, studying, and Beth, the Executive Director, walked up to me, and we just had a conversation about the organization. And since then, I've been working as a part of it in some capacity.
I was a counselor, and then I was, like, actually I really love this. I love teaching youth. I love showing them the freedom of creative expression, and through my involvement with young neurodiverse people, I've been able to share the joy, and we're making a collage about Sonic the Hedgehog, and now you know how to use Photoshop. And that's like... You know, I've met children who don't speak.
They either choose not to, or they struggle with that in some capacity. And it's like... You get to know more about them, through providing these tools. So Tech Kids Unlimited provides educational opportunities for students with autism spectrum disorder and ADHD.
We have weekend and afterschool courses, and weeklong summer workshops. Afterschool career pathway, holiday programs. We again expanded into work-based learning, and the tech skill workshops have been a core of what we do for a long time. Like I mentioned.
And our mission, a bit more about that. We want to address the gaps in accessible experiences with technology. We want to inspire neurodiverse students. And we want to teach computational thinking and tech skills in a nurturing and supportive individualized community.
Does anyone know someone who is neurodiverse or identifies as neurodivergent at all? Nice. Yeah. So... For those who cannot see the audience, that is most of the room, actually.
Which is pretty awesome. So here's a list of what some of our community members may identify with or experience. It's not comprehensive. But a lot of things kind of go hand in hand here.
And we offer virtual and in-person programs. Our virtual programs are great, because we see people from all over the United States. And our in-person programs are also great, because people get to hang out and play video games on their Switch that they bring together. And we work out of the Ability Lab at NYU Tandon, we have social workers in each classroom, a high counselor to student ratio, financial that's available and also some free programs.
Now, I talked about what we do in a general sense. But I want to think about what access looks like in practice. And I have this video to show you. [VIDEO PLAYS - MULTIPLE SPEAKERS] [What is Neurodiversity?]
Neurodiversity means that some people's brains are actually different from others. It means that everyone's brain works differently. That my strengths are also my differences. That there's a spectrum of people who learn or gather information differently.
That can also mean that we have quirky and unique abilities, you could say. Neurotypical people think differently than we do. [When I think about neurodiversity,] I think about how creative people can be. How much I love my special interests.
How I can see the world in a unique way. And how we solve problems in different ways. One thing I wish people knew about autism is that it's not a curse. That we deserve to be treated with respect.
It doesn't make you any less "normal". It's something that makes us all unique. You might think autistic people can't find a way to make friends. But, in fact, I have my own way of doing that, and it's just fine.
People think I can't communicate well, but I find my own ways. Autism helped me gain confidence in life. Autism isn't a curse - it's what makes people special. You might think that people who are neurodiverse can't live by themselves, can't communicate well with others, and can't stand up for each other.
But, in fact, we can.
Our tools that we teach can also be used for storytelling. Because anything can be a medium for storytelling. And narrative. So in the top left, we have a game design workshop.
There was tabletop games and digital games. And this card game workshop allowed the students to express their interests about pirates, and it was pirate-based. We also provide opportunities for feedback and just getting to know how people feel with what lessons we're teaching, if they want to do more of it. Because that's also an important thing.
Just engaging the youth, the students. And just like... We want to have fun. We're also learning.
But at the same time, it's like... We want you to use these tools because you want to use them and because they're gonna benefit you in some way. Right? So on the bottom left, you'll see on the digital art programs -- we also like to use a lot of web-based software that is accessible, so when they go home -- you don't need to buy an expensive subscription that essentially is...
That's a barrier, financial barrier. So we believe in transferable skills amongst tools. And these videos... I'm just gonna talk over.
One example of working with the community -- Marilyn the Chef is this lovely nutritionist on the left who came in to talk about nutrition and the power of choices. Like if you're at a bodega, you can get the candy bar or you can get the orange. And which one is healthier for you. And we invited her in, because we have students with ADHD that would just eat a lot of cookies for lunch.
As one does. I used to do that. But then they would just crash. And get, like, just start napping on the table.
And it's like... You need to make informed choices about your health. And you need to know... You know, at least know what's going on with your body and how this could change, if you want that to change.
And then on the right, we know our students love karaoke. So I had some artists, and I was like... Hey. They have this fun project where they do karaoke, where they switch out the words with datasets.
So it's combining AI, tech, and also karaoke. And it was super fun. And that's a tech social. So we also have opportunities for people to connect in that capacity.
Digital agency is one of our programs where we partner our interns with clients, and they do client projects. So one of the things on the left is the Museum of Moving Image has this event called Marvels of Media, where they center autistic and neurodivergent creators. And our digital agency got to present games this year and last year, which is really great. And so that's been a really great partnership.
It's also just a way of celebrating all the hard work that everyone is doing. And we get to hang out together. A bunch of the staff came this year. It was really fun.
And on the right, it just demonstrates -- digital agency is a virtual program. So when we get to celebrate it in person, that's cool too. Because people who haven't met each other see each other in real life. And it's like... You're taller than I thought you would be.
For example. Is something I might say to somebody. Because... For those who can't see, I'm short.
And so access, just finally, is a practice. Not a check box. It's something that we have to keep doing and finding ways of doing, ways of applying it. And it lives in every part of our ecosystem at Tech Kids, but also just this ecosystem.
The curriculum, the media, and the mentorship. And when we make space for neurodiverse creativity, we all benefit. Some space that you can make for neurodiverse creativity -- we actually have an exhibition of student work, if you want to come and check it out. This is the RSVP QR code.
And that's it, actually. That's all I have. So I'm just gonna leave the QR code up.
How do you involve neurodiverse youth in shaping the way Tech Kids Unlimited shares their stories? That's a great question. So... We actually have a Neurodiversity Advisory Council, which is made up of community members from Tech Kids Unlimited.
And we essentially have a group of community members who are like... I like this program. Or even deciding which workshops we're going to have. Having ideas of what they want us to share on social media, or volunteering to create things that they want to be shared on social media.
And so just really... One student in particular was super involved, and he was like... I love this guest speaker! I want them to come and guest speak for us in this program too.
And so we were like... Yeah. We'll make that happen. So yeah.
It's just really about nourishing that self-efficacy, and more opportunities for people to engage with what they're a part of. You know? Calling people in. Nothing about us without us.
Not to like... That term might be... I don't think it's a cliche. I think it's a good term for a reason.
So we definitely practice that.
The organization has weekend and afterschool courses, weeklong summer workshops, an afterschool career pathway, and holiday programs. They expanded into work-based learning. The tech skill workshops have been a core part of their work. Their mission is to address the gaps in accessible experiences with technology. They want to teach computational thinking and tech skills in a nurturing and supportive individualized community.
They offer virtual and in-person programs. Their virtual programs bring in people from all over the United States. The in-person programs allow them to hang out and play video games that they bring together. They work out of the Ability Lab at NYU Tandon with social workers in each classroom. The program has a high counselor-to-student ratio, as well as financial aid and many free programs in Career Ladder.
The TKU model uses a combination of universal design for learning, social emotional learning (SEL), connected learning, design thinking, and project-based learning. This model allows them to enjoy the programs, gain new skills, and make friends.
Access is a practice, not a check box. It’s something that they must keep doing, finding ways of doing, and ways of applying it. It lives in every part of the ecosystem at Tech Kids, including curriculum, media, and mentorship. When everyone makes space for neurodiverse creativity, everyone benefits.
Using AI to build bookmarklets for accessibility testing
Damian Sian is a design accessibility program manager in the design organization within Adobe. Damian had an epiphany that he doesn’t rely on automated testing tools from companies that don’t do the work he does.
Transcript: Using AI to build Bookmarklets for Accessibility Testing - Damian Sian
Good evening, everyone. My name is Damian Sian. I work at Adobe, as Thomas mentioned. I am a design accessibility program manager.
And I work in the design organization within Adobe. Specifically I work in the product equity team. And further specifically, I work in a specialization, and a strategic focus, of practice transformation. One layer down from that, I also -- how I achieved that practice transformation is through enablement and training.
So that's my specialty and focus. Spencer Schultz Johnson is the manager of our group, and my peers are Danny Burr, Julianna Rowsell, and Noelle Fall. And I'm here to talk about creating customizable accessibility tools with artificial intelligence. I'm gonna frame that conversation in a recent training I was building for Adobe.com.
And the group of people I was training were content authors and copy writers. And during this effort of building the training, I kind of had my epiphany, that I don't want to rely on the automated testing tools from companies that don't do the work that I do. And I hope to share that epiphany with you and have you have your own epiphany today. We'll see.
So this is how I start a training for this group. For content authors and copy writers, I stick to my main food groups: Alt text, link text, heading text, tables, lists, color contrast, color alone, putting pausability on motion, captions on videos, and identifying language on the page and parts of the page. I don't talk to them about anything else. Because they can't effect any change or outcome with anything else on the website.
They're using a content management system. It's highly templated. They're very limited in what they're able to do. So I talk to them about that in great detail.
And I have the link text piece here highlighted on my screen. Oops. And that's where I kind of dug in. And I decided that I'm going to build my own testing tools.
And why that's special is that I'm not an engineer. I'm not a software developer. I'm not a programmer. I am a subject matter expert.
I am a very good tester. I'm a great user of assistive technologies. A great auditor. And I can do training really well.
But I am not a developer. So in the past, when I've had ideas to do things, I've had to rely on others. And it's a wall that I hit, that I broke through. This is an example of one of the lessons that I would give to this group.
On the screen, I have three cards. Each has a call to action. That call to action is the word "open". It's a link.
And what I teach people here, and the way that I teach this lesson, is that: A screen reader user tabbing through this interface would hear "open: Link", "open: Link", "open:link". If they pull up the rotor with the voiceover tool, they're gonna hear "open, open, open". So the lesson that I give them is to expand on that. And the way I tell them to do that in this environment, with this group, is to grab that adjacent heading.
And instead say: Open: Text to image. Open: Generate video. Open. Text to vector.
And as I'm building this, I'm thinking... Why am I not also building them a tool that would help them understand how to do that in their situation? So when they go back to their desk, they can actually take the lesson I'll have given them and feel comfortable and confident in doing the work?
And the last part of the lesson I always give is that automated testing tools will only get you so far. And that exact scenario that I just showed you would not get picked up by Axe. It would not get picked up by WAVE by WebAIM. ANDI will give you a warning.
And Arc ToolKit will give you a warning. Which is cool. I didn't picture that all up here.
So in the face of that, I decided I don't want to have that conversation with them again. And I don't want to have that conversation with them again on link text or any other of those ten areas. And I want to build them something that will work for them. And again, I'm not a developer.
So I use Cursor AI. And I have long conversations with Cursor AI to build a set of tools based on these parameters. I only want to look at links that occur inside of main. Content authors can't do anything in the header or the footer of the page.
They're only working in main. Rule one is the one I just showed you. If you have the same link text that's going to different destinations, you owe me an ARIA label for those. Rule two: If you do an ARIA label, you have to start off the ARIA label with the visible text.
Learn more about what? Read more about what? Free trial of what? That's rule two.
Rule three: If you put blue link text inside of a block of non-interactive text that's black, give me the underline and do not look at the 3 to 1 contrast ratio. Because I think it's a copout.
So here it is in action. Again, I am not a coder or a developer. But I did make a graphical user interface. I used a bookmarklet style, and it will analyze the page and get extremely granular about the environment that they are working in.
So it will pick up CSS style names. It will pick up component names. It will pick up everything that's just germane to this group that I'm spending the time training. And here it shows a screen reader text, it shows why it's a failure, and it shows the suggestion, which I also built with Cursor AI.
Can you give them the right answer? The right answer is: Pick up the H3 that's right above the link. It's always going to be the same thing in that component. So I can tell them that.
And I can give them the tool, so they have the confidence to do it on their own. Rule two: The error that's caught here, the screen reader would read: Get help from our support team, link. But the visible text label is: Contact us. So... The tool also gives them a suggestion -- oh, that's not correct.
I had the wrong graphic there. The real thing will say "contact us. Customer support". And you can see that I do have listed out the levels of support for automated testing.
They'll get you so far. But they won't do everything that I need it to do.
And here is rule three. Where the link text is blue, set inside a black, non-interactive text. The only way to determine if that text is interactive is with the ability to perceive the color blue. So we put the -- and I don't care if it's 3 to 1.
That's a technique. It's non-normative. No. So... Why does it matter that I did that?
One: I think that this is a conversation that a lot of us are about to have. If you go and ask your leadership for head count, they're gonna ask you what you're doing with AI. And I think it's time for us to -- people like me, who are not developers, who have ideas, to get ahead of this and start having really good stories to tell. Because it's gonna come up, and it's gonna come up really quickly, and this time last year, I wouldn't have had an answer.
And now I do. So... I'm hoping that you will take the call. And if you're like me, you're not a developer, and you have ideas, don't let it stop you from building your own tools that do the exact thing that you need them to do.
For those people. I am not claiming that I am now a developer. Because I've used Cursor AI. I understand that.
I'm not exercising the hubris to say I'm now a software developer. But the cool icing on this cake, the development team for Adobe.com is a group called Consonant. They were making their own testing tool. And when they saw my testing tool, they said: Can we please have that?
I said of course. And what they got was all the logic. They got code snippets. And they got my subject matter expertise.
Which they wouldn't have had on their own. So... Yeah. That is... I'm a minute shy.
But I think I did all right. So that's my pitch. Go out and use Cursor AI and any other tool that you can. Build your stuff.
Don't let anything stop you. And keep going at it until it works. Which is what I did. So thank you.
He conducts content accessibility training. He only focuses on the things the attendees can control. They use a content management system, so they are limited in what they can do. Damian is not a developer, engineer, or programmer. Yet, he created his own testing tool. In the past, when he had ideas of things to do, he had to rely on others.
Linking text problem explained
One of the things he talks about is linking text. A webpage has three cards, each with an image, text, and a button that says “Open.” A screen reader user tabbing through this interface would hear “open: Link,” “open: Link,” “open Link.” If they pull up the rotor with the voiceover tool, they’re going to hear “open, open, open.”
He tells students to expand on that by grabbing the adjacent heading and instead say, “Open: Text to image. Open: Generate video. Open: Text to vector.” And Damian builds this lesson, he thought to himself, why not build a tool that would help them understand how to do that in their situation? This way, they can do the lesson and feel confident in doing the work.
For the last part of the lesson, he teaches them that automated testing tools will only get you so far. And this scenario that Damian just shared wouldn’t get picked up by aXe or WAVE. ANDI and Arc ToolKit will give you a warning.
Building the accessibility bookmarklet with AI
Damian wants them to learn the lesson and not have the conversation again. So, he built something using Cursor AI. He had long conversations with Cursor AI to build a set of tools based on these parameters:
- Only look at <a> links inside <main>. Ignore the <footer> and <header> of the page.
- Rule one is if you have the same link text that’s going to different destinations, add an ARIA label to make them different.
- Rule two: If you do an ARIA label, it must begin with the visible, inner text. “Learn more about what? Read more about what? Free trial of what?” Otherwise, it violates SC 2.5.3 Label in Name.
- Rule three: If you put blue link text inside of a block of non-interactive text that’s black, it must have an underline. Links with a class of “action-area” are excluded from this.
Again, Damian isn’t a coder or a developer. Yet, he made a graphical user interface. It’s a bookmarklet that analyzes the page and gets granular about the environment that they are working in. It picks up CSS style names, component names, and that’s germane to this group that he’s training. The tool shows a screen reader text, it shows why it’s a failure, and it shows the suggestion. All of it was built with Cursor AI.
Can you give them the right answer? The right answer is: Pick up the H3 that’s right above the link. The tool will give them the confidence to do it on their own.
Incorporating AI into work
Why does it matter that Damian did that? He thinks that this is a conversation that many of us are about to have. If you go and ask your leadership for head count, they’re going to ask you what you’re doing with AI.
It’s time for everyone including non-developers who have ideas to get ahead of this and start having good stories to tell because it’s going to come up. If you’re not a developer, and you have ideas, don’t let it stop you from building your own tools that do the exact thing that you need them to do.
The cool icing on this cake is the development team for Adobe.com were making their own testing tool. And when they saw Damian’s testing tool, they asked if they could have it. Go out and use Cursor AI and any other tool that you can. Build your stuff. Don’t let anything stop you. And keep going at it until it works.