Accessibility is a design and UX responsibility: How to run an Accessibility workshop
Jess Vice38:332022
Small accessibility checks cost $600; skipping them risked a $1 million lawsuit
Ask skeptics who counts as disabled and they list wheelchairs, canes and guide dogs, about 4.8% of Americans, while the CDC figure the speaker cites is one in four adults. Jess Vice, Strategy Director at Struck with 14 years in tech and product, argues accessibility belongs to designers from kickoff, not to developers at launch. So how does a creative team actually learn to feel what its users experience?
Get a step-by-step plan to run a hands-on accessibility workshop for your own team
Jess Vice, Strategy Director at Struck, argues that accessibility is a core UX and design responsibility that must start at project kickoff rather than be bolted on by developers or compliance teams at launch. She explains disability as a spectrum, makes the case for designing for extremes and for early accessibility checks, and walks through how her agency planned and ran a hands-on accessibility workshop for its creative team.
“The very first rule of user experience is this. You are not your user.”
“When we use the extremes to shape the problems that we're solving for, we often catch most of the middle in the process.”
What you will learn
Reframe disability as a spectrum of permanent, temporary and situational conditions that affects far more users than the narrow definition suggests.
Plan and run a station-based accessibility workshop with guides, a timekeeper and hands-on assistive tools.
Make the business case for accessibility by comparing the cost of early checks with late fixes and lawsuits.
Tailor accessibility arguments to each audience, from CEOs focused on cost to creative directors focused on users.
Raise accessibility gaps without blame by asking who is included, who is hurt and how to do better next time.
Key takeaways from the speaker
How designers can level up our ability to be inclusive, create accessible work by using tools that solve new-to-us problems
How to build an interactive workshop including using assistive tech (like voice to text), and other platforms to elevate the accessibility of the things we create.
Designing for averages is an exclusive and privileged approach. –When we use the extremes to shape the problem we’re solving for, we often catch most of the middle in the process.
creatives can build an interactive workshop including using assistive tech (like voice to text), and other platforms to elevate the accessibility of the things we create.
Details
Level
Intermediate
Format
Talk
Technical depth
Introductory technical
For
Mid-career, Senior individual contributor, People manager
Length
38:33
Published
July 2022
Questions this talk answers
Why is accessibility a UX and design responsibility rather than a developer or compliance task?
Because UX and design kick off every project, ask why, and advocate for users, accessibility is foundational and cannot be added at the very end. Leaving it to developers or compliance at launch is, in her words, irresponsible on the part of UX and design.
Is disability really a small share of users?
No. The narrow count of wheelchair, cane and guide dog users is 4.8% of the US population, but the CDC data she cites shows 61 million American adults, one in four, live with a disability, before counting temporary and situational limits.
How do you set up an accessibility workshop for a creative team?
Announce it early and warn people it is hands-on, research disability data and use your own work as examples, then run timed stations with a guide at each one for tools like colorblind tests, contrast checkers, screen readers and captions. Afterwards share the data and tools in an internal wiki and survey participants.
How do you respond when leaders say accessibility workshops waste resources?
Tailor the message to the audience: show CEOs the cost case, including a possible $1 million lawsuit, and show creative directors how large the population on the disability spectrum is. Persistence and examples of others getting good results are the two keys.
How can teams work better with neurodivergent users?
Ask, observe and listen without judgment, invite people to describe how an experience felt and what would feel better. An audience member added that patience and paraphrasing to check understanding, which she calls mirroring, help a lot.
About this talk
Designing for Accessibility requires due diligence, optimizing for edge cases, and deeply understanding all the ways all people need the product to serve them.
In this presentation/talk with industry veteran and Strategy Director Jess Vice, we’ll learn step by step how creatives can design a targeted and interactive accessibility workshop for their clients, and build.
As we learn how to better understand what others are experiencing, we begin to develop awareness and empathy, which can be designed to input directly into user experience.
Let's talk about accessibility as a UX and design responsibility. Or subtitle, how to run an accessibility workshop for creatives. That piece is the second half. So let's go through a quick overview of what we're going to talk about. I'm going to make a couple brief introductions of who I am and who I work for. We'll talk through what accessibility is and understanding how it plays a role in our current world. We'll look at accessibility in combination with UX and design. And we'll go through the steps of how to set up an accessibility workshop for a group of creatives.
But I understand that not everyone is working in a digital space or with creative teams. So I've modified it a little bit to be more applicable across a bunch of different industries. Also, at the end, I have a whole bunch of resources on slides that whether I'm not sure the conference will be sharing the slides, but we'll make sure that the video is published with closed captioning and all of the resources are made available afterwards.
As I said, I'm just vice. This is my Twitter handle. I'm the strategy director at struck where I lead a team of brand media UX and experiential strategists. We build thoughtful data driven strategies for our clients. And we work with struck who is a creative agency with a 25 year legacy of brand building and experiential design. We're based in Salt Lake City, Utah, in the west side of the United States. And we make market leaders out of brands by transforming their physical and digital experiences to create experience affinity.
You're welcome to use the Twitter handles if you want the conference hashtag and it's in the bottom right corner of my slides. Also, that can be a little overwhelming. So no worries. So why am I talking about accessibility? I have a deep background in UX. I've been working for 14 years in tech and product both on the agency side and in house with teams and clients directly.
But I would say the general theme for my entire career has been advocating for humans. And it seems unfair to me as I've gone through all of these different realms that we still expect folks with disabilities to both navigate this world and advocate for themselves. I believe that UX and design experts have the background, the tools and the experience to be really good advocates and allies. So that's why I'm here to talk about it today.
A quick definition of accessibility, even though we've heard this word a lot, let's just make sure we're all on the same page. So whether it's a physical experience, a mode of transportation, a service or product or digital interface, accessibility is a state where any user at any time can retrieve the information or goods that they need with little to no difficulty.
And I think the important piece here is the little to no difficulty. The part of accessibility that's most important, obviously, is access. And even though this is a very common topic and we hear a lot, we also still hear arguments. Well, why should we bother? Why does this matter? I've seen this equation come up where people even will say on the count on their fingers.
Well, there's wheelchair users and people with canes and people with seeing eye dogs. And that's such a small population. Why should we even bother designing for them? And they're right. If you look at this list, that's 4.8% of the United States population. That's not very much. But that is a really, really narrow definition of disability. It doesn't include cognitive disabilities, learning or neurological disabilities, auditory, physical, visual.
It's just this really narrow perception. And when you look at this list, we're actually considering a much larger portion of the population when we start designing. Another way to think of it is that not all disabilities are permanent either. This chart comes from Microsoft Designs Toolkit about inclusive design. And they point this out. We exist on a spectrum.
We have permanent disabilities. There's temporary disabilities. And they're situational. Every one of us has ended up in a situational disability environment where we can't access the thing that we need because of what's going on around us. I would bet that if you think back through your last week, you'll be able to come up with at least one situational disability that you experienced just because of where you were and the conditions around you.
So when we look at this larger picture of disability on a spectrum, and we start to think of how we're designing for all of these pieces, we also start to think about maths a little bit, which is not my favorite subject. But my friend Jared Spool says don't use averages. And in design, as we start to build personas or we start to build sort of these structural pieces of our design process, we're often averaging.
We're saying this whole group of people is like this one person, and we're going to use that one person as our template for design. But Jared says don't do this. He says that the entire purpose of an average is to dampen out the extremes, but the extremes are interesting. When we use the extremes to shape the problems that we're solving for, we often catch most of the middle in the process.
So a couple of questions that I try to take away from this and I would challenge you to think about going forward, especially on this topic of extremes and a sliding scale or a spectrum is how, as we do user research, are we including extremes? How hard are we trying to include those extremes? And how might we do a better job next time of including more stories?
So I want to run through really quickly because I know not everyone works in a digital space. I want to run through a bunch of different examples of accessibility and how it looks in the world around us. Because it is a global concept, right? And not just for websites. A lot of physical accessibility solutions are the first things that come to mind.
And my favorite is the curb cut effect. And I don't know if you've heard this philosophy, but in the early 1900s in America, city developers started building ramps into the corners of their sidewalks so that wheelchair users, and they were targeting veterans particularly, wheelchair users could access crossing the street much more easily. So what they found on accident was that mothers with strollers, elderly folks, children on bicycles, people with deliveries, and even more were using these curb cuts as well.
And so what happened to be a design for a very small portion of the population ended up being exponentially beneficial to the entire community. And this idea is recognized as the curb cut effect, which again is Jared's average statement. We're not designing for averages, we're designing for extremes, and we catch all these people in the middle. We've also seen a lot of really great technology advances in the last couple of decades from screen readers to these really clever single-handed keyboards.
And actually in our research for the workshop that we put on, we found out that Apple built one of the better screen readers. It's called VoiceOver, and it's actually on your phone if you have an iOS device. It's in your pocket, it's accessible to anyone. And the reviews from folks who use it frequently are that it's really spectacular and works very well.
In my experience, the gaming industry has been leading out on visual accessibility. They have been introducing all sorts of modes for colorblind. And even on the picture on the right for Fortnite, multiple different variations of colorblindness are accounted for in their settings. So that the games themselves are accessible to so many more people. My favorite is this example on the left.
It's a game called Two Dots. And you play by matching up the colors in the circles. But if you can't see the colors, you can add a layer where it puts shapes over each color. And so you're just down to matching shapes, and it's that much simpler. Another example is the voiceover ID, like the one I gave at the very beginning of my presentation.
And if you think about, that's helpful for folks who can't see, but that's also helpful for folks who are situationally unable to see. Like some of us who take Zoom meetings in our car with the video off. I won't point fingers, but I'm certainly one of those. But a voiceover ID certainly is very helpful and gives us a lot of context for the person who's speaking.
The captioning and subtitles are becoming way more ubiquitous. We've seen them on transcripts for podcasts and for interviews. But we've also seen them used on TikTok and Instagram and places that I was a little surprised, frankly, to see such accessible options being employed. And if you've been watching the news at all lately, we're starting to see sign language interpreters show up as a very common feature of news conferences and public addresses.
And I believed that the closed captioning was not available today. It does seem that it's working. So either way, we'll make sure when this video is over that we have captions and a transcript available. Cognitive and learning disabilities, things like measurement tools, like the Fleish Kincaid scale or readability checkers are actually really helpful to bring content down to an accessible level for a wide audience.
And one thing that I really love is adding labels to icons, which reduces cognitive load for the viewers. I don't know if you all saw this, but the photo on the left is from Venmo. About four months ago, they updated their UI and they launched these four icons across the bottom navigation. And the confusion was wild. No one could understand what they meant.
We all were so used to the original UI and there was no warning. And without any context or labeling, even those of us who are really tech savvy were super in the dark and didn't know what to do. I also just checked last night and they have updated the navigation to have word labels to go with each icon, which I think is a great react reactivity.
But they could have saved themselves a lot of trouble if they did it up front. The example in the middle is from the material design design system that Google created and it recommends always adding labels to icons. So you can see why as a UX practitioner and a design adjacent design advocate, I believe that accessibility is actually part of our job.
I really think it's foundational to the work that we do because we kick off every project. And it's really not something that can be added at the very end. So expecting the development team or the compliance team to show up at the end of a project and say, oh, hey, what about accessibility is really irresponsible on the part of UX and design.
And I want to talk a little bit more about why. So as UX and design and, you know, I just realized I didn't clarify UX. UX is user experience where we are focused on how humans interact with an interface or a product or even a building or a space. It's really focusing on the experience that folks are having with whatever it is that we've created.
So we're very human centric and focus on bringing that experience to as many users as possible. So as UX and design experts, we are experts at getting to why. We understand how to ask the right questions, how to help clients tell us what it is that they're trying to get to, what the desired outcome is. And then we're able to convey that over to the rest of the team who's building the project with words or with illustrations.
So we're really good communicators and we are very good at speaking up on behalf of the research that we've done. As UX and design, we're also advocates. The very first rule of user experience is this. You are not your user. We tend to make a lot of assumptions about other people based on our own experiences. And user experience asks you to stop and to admit that you are not the person that you're designing for.
So we've learned how to find those people and we've learned how to listen to them, listen to their experiences, and then bring that research back to the teams and to broadcast or share the information that we've found so that everyone understands the experience we're designing. And we've also learned through every step of the process how to recenter the work that we're doing on the humans who will be using it in the end.
One of the most important pieces of that recentering, though, is advocating that all users who use this solution will experience success. And because we study people and we listen so closely and hold the desired outcomes in mind, we're really great partners to work with across a bunch of different teams. We help others along on the journey of understanding how accessibility matters and how they can participate, especially developers.
And I do think while we could have an entire separate talk on developers, I want to take just a second to address this specifically from a UX and design perspective. None of what we build or none of what we design will make it to the real world without developers. So if we don't spend the time talking to them, listening to them, educating ourselves, understanding what's possible, and then asking where they can meet us, we don't give accessibility a chance.
And I think that, again, this could be an entire separate talk, but we really would benefit by building a stronger relationship with developers to bring accessibility into all of the work that we're doing. And if that's still not enough for a case for why we need accessibility, there's a really great business case behind this. This is an example, this is an illustration of a case study that I read where a teen was building a website and they did a quick analysis of when they did accessibility checks and how much it cost them.
So the first line at the top is a project end-to-end kickoff on the left, launch on the right of a website, let's call it a website. And the circles represent the times that they went around and did some accessibility checks. And you can see on this project, they checked in frequently on small things and they did it sort of consistently throughout the process.
And what they came up with was each of those accessibility checks cost about $100. So they spent about $600 and launched a product that was fully accessible. The second line is a more typical project where we kick off, we build the whole thing, we get to development and go, oh, hey, can you do some accessibility work? And we do, but it costs a lot more.
Often we have to bring in a third-party vendor and it gets really expensive, so it costs $10,000 was the estimate here. But it goes live still with all the accessibility checks in place. The last project happens almost as often where we build and launch without any accessibility work. And now, thanks to the GDPR and WCAG and ADA requirements, if you launch a website that isn't usable, you are liable for lawsuits.
So what they found was the lawsuit scenario costs closer to $1 million. And it makes a ton of sense at this point that we would just do accessibility checks as we're going throughout the entire process to make sure that we get it right from the beginning. So I want to talk about how we got started at Struck.
We ran an accessibility workshop for our creative team to help them understand the tools and all of the pieces that they could use to make their work stronger. And I wanted to also note, like, we are far from perfect. This is something that we have started and we're really glad to have started it, but we know that we have a lot more work to do.
And so this is an ideal starting place for folks who are interested in bringing accessibility to everyone at their company as they get started designing. So first off, we planned pick a date, let people know it's coming, put it on the calendar, share examples and articles. We started talking about things like voice to text and other technologies that we could use to make our work more accessible.
But we also started spreading word around the office that we would have a hands on activity. And I feel like in work culture lately that you kind of have to warn people that there's a hands on activity because everyone gets awkward. So we kept telling folks we're going to try stuff. We're going to, you know, use the screen readers and we're going to see how this works for ourselves so that we all have a better understanding.
And we were pleased a lot of people actually got over their awkwardness and joined us for it. This is an example of the calendar invite that we sent. And on the top left, we mostly posted on the calendar Slack. We sent emails and we made announcements. But if you wanted to go all out, you could print posters for the break room, mention things in internal reviews, do desk drops.
I mean, the sky is the limit. It's however much you want to keep the upcoming workshop at the top of mind for folks. We also did a lot of research before we started the workshop. Since we're based in Utah in the Western United States and most of our clients are local or national, we research disability statistics specifically in America.
And we put together a brief presentation that set the tone and the case for accessibility. It went through data around visual, auditory, physical, speech and cognitive, learning and neurological disabilities. And we decided to use our own work as examples. It didn't feel fair to point fingers at other people and say they are not doing it well when we had plenty of examples ourselves that we could pull and say, how did we do?
Could we do better? So we went through our own work and pulled up pages on websites or examples of design work that we could show on a laptop and share. This is an example of an infographic that we found from the CDC or the Center for Disease Control here in America that talks about how disability impacts the population.
And if you remember the early argument of 4.8%, you know, only 4.8% of people are disabled. You can see here how wrong that number is. The people who believe disability is minor are really misled. In our country alone, 61 million adults live with a disability and that's one in four people. So any one of us knows probably several people who live with a disability day to day and we're not talking about it.
So we did some research with the CDC. We looked at health departments. We looked at special interest groups and local nonprofits. And then there are other places, especially as a UX researcher, that I really like to look because you get more of the words of how people are talking about their own lives. So forums, Facebook groups, reaching out to people that you know and hearing from real people about their experiences brings this research piece full circle.
You start to get really personal understandings of what it's like day to day and then what kind of help they have and what kind of advocacy they have and where they would like to see things change and grow. So as we built out the presentation, we considered the context of our work, as I said. So when everyone showed up the first day for the workshop and it was just a quick afternoon, a couple of hours in our office, we gathered everybody around and went through the presentation just to help frame why this is important.
Again, I think a lot of people have this idea that is just not that big of a deal. And then as you look at the data, you start to realize it is a very common thing and it is something that most of us have come in contact with, if not personally experienced. So we encourage folks to start thinking about how we could build more empathy into our work.
Around the office, we set up a couple of different stations and each station, I would recommend this highly have a guide at each station who is familiar with the tool or the experience and can walk folks through it. That made a huge difference for us. There was one station that was unmanned and it went a little lost in the process because folks didn't quite know what to do.
So we asked people to go and try things. We also had someone who was appointed to keep time. So every 10 or 15 minutes, they would go from group to group and suggest they move on so that everyone got a full experience. And I think there's a lot of ways to get really creative with this. Here are some examples.
On the left, that column is what struck did. We tried a colorblind app, which was really cool. It actually has a filter where you can see the world around you through different colorblind lenses. And we tried a colorblind plugin that made our work on the internet look like it would for folks with different colorblind varieties. And we did a test to see if any of us were colorblind.
Turns out our CEO is. I've found if you do this in larger groups, there's almost always one person who turns out to be colorblind and didn't know it the whole time. So that's an interesting conversation starter. We looked at a contrast checker to make sure that our websites were matching the WCAG recommended contrast depths. We looked at a screen reader and tried that on our sites to see how they sounded.
We went through closed captioning and brainstorming sessions about what our work looks like and how we could do better. And because we also do some physical experiences, we talked about what we thought the current state was and how we could improve our physical experiences or spaces that we built in the future. On the right hand column are some more ideas of ways that you could play with understanding how all of these tools work.
It'd be really neat to have a sign language interpreter come and demonstrate for the team and talk through how to interact with folks who are deaf. So readability scores are really terrific, easy tests to run on all of your own materials, even if you don't have anything digital publications, pamphlets, flyers, all of those can be run through a readability score.
And I think there are lots of ways to get creative with taking a walk or a field trip as you think about the environment around you and paying attention to how other people experience it. Here are some photos from our team. On the left, a designer is walking her colleagues through the colorblind test. And on the right, you can see like it was a little awkward.
There's some crossed arms and some wide leg stances and some smiles because it felt a little funny. But we've found that trying new things together really breaks us open and grows our understanding of both each other and the experience that we're talking about. And by doing these together, we create a basis for accountability because we all share this experience.
It's now easier for someone to say, hey, we need to consider the contrast is not high enough or we need to look at how to code this so that the screen reader is more accessible and more effective. Or, you know, the copy is we don't have alt text on our images and no one is afraid now to raise a hand and say we forgot something because we've all shared that experience.
And so there's there's not nearly as much shyness. We also because, like I said, we do create digital to fully immersive physical experiences. We took a lot of time to brainstorm. You can sort of see in the background there's orange sticky notes on the windows. We walked through all of our different products and outcomes and talked about how how we have considered them in the past and how we might change our approach to them in the future.
We also looked at working in an office together when you have a whole bunch of people in the same building. If you don't have open conversations about each other's needs and how you can support each other sort of on a regular basis. There may be someone who is suffering or who needs more awareness and more attention or something different than they currently have that could get the help that they need, but hasn't had the platform to say so.
So regular check ins have been really great for us. We've had a couple more of these since. All right. And then the last step is really important. Implementing what you found is obviously the whole point of a workshop. So we were really careful to share the presentation data publicly where the rest of the team could find it.
We linked all of the tools that we've tried in our internal wiki, and I've actually seen designers go looking for them and come back up and say, oh, the contrast on this isn't good enough. Hang on, we have to change some of the colors and it's been it's been really encouraging that more folks know how to access the tools, where to get them and then how to use them.
We also sent around a survey afterwards to make sure that this was useful and it helped change people's perspective a little bit and asked if this was something that we could continue doing and everyone seemed to be really on board. But I think the most important piece of implementation is speaking up that if you see something that doesn't seem accessible or isn't considering accessibility, it's your job to say so, especially as UX and design.
But once you've been educated on something like this, it's not comfortable always, but it's definitely your responsibility to say we could do better. This this is OK, but we could do better going back to the shared experiences, building a workshop and putting this together really sets you up to be able to do that more comfortably as well.
One thing that I've learned from my therapist is that a really easy way to point out uncomfortable things is to ask questions instead of pointing fingers or throwing flags or laying blame. It's easier to make a space where people feel comfortable contributing solutions if you ask a question. And I've riffed on these questions a little bit. They're based on a quote by Dr. Victoria Verletza, who's a social justice educator on Instagram.
She's terrific. And she has these questions about who's being included. And I think they're incredibly relevant to UX and design research as well. Who has been included in this work? Who has not been included? Who benefits from the current setup? Who is hurt by it? Whose voice needs to be heard? How might we find those voices? Who else needs to hear these decisions?
And how might we do better next time? I think we always underestimate the value of slowing down and taking time at the end of a project to look back and say, what went well? What could have been better? How would we do this differently next time? And again, that creates a shared environment where folks feel more comfortable bringing up their learnings and then referring back to them when something comes up.
Because I believe that humans are UX and design specialties and that humans are the focus of our jobs. And if that's the case, then our shared goals are making the world usable and useful for everyone. And the power of one of these accessibility workshops is that when we feel for ourselves what other people are experiencing, we start developing awareness and empathy and that shared experience.
And by exposing ourselves to new things, we level up our ability to be inclusive, to create accessible work, and to make the world around us better. Because meaningful access to digital information and services is a basic human right. I blew through that way faster than I expected. So I'm going to stop sharing and open the chat up for questions.
I know the session was supposed to go a little bit longer, but I talked really fast today or something. So if you all have anything, let me go through the chat real quick. If you have questions, please drop them in the chat and I'll make sure that we read them out and try to answer them. Good, close captioning worked, that's awesome.
Yeah, Patricia says there are about 1.2 billion people with disabilities in the world, and they have a market power of $8 trillion. I love that statistic. And I think we should talk about things like that. We've been talking about this a lot in the U.S. lately, that money has power. And if we can find the strings where the money is and pull on those strings, we'll get things done.
And the gaming keyboard, the one-handed keyboard is a good gaming keyboard solution. I don't game, but I'm around friends who do. You're probably right. Yes, and Jackie pointed out that this is really only talking about diagnosed disabilities. There are a lot of neurodivergent people who are undiagnosed and don't know or understand why something doesn't work for them.
So this is even more important as we start to talk through it. And Patricia says that the other point is that, yeah, half the population is aging, and we're losing our color contrast starting in our 40s. So again, thinking about situational or temporary, situational could be just that I am older than 40 and I'm starting to lose color contrast, and it's not a disability necessarily under regulations and ADA protection, but it is absolutely the same thing.
Okay, let me scroll down and see if there are questions. Have you ever faced objections to starting accessibility workshops, i.e. that it's a waste of resources? If so, how did you respond to those objections? Thank you, Alexis. Well, yes, there's a lot of people who will say it's a waste of time. And honestly, I've taken that slide that has the example, the case study of how much it costs.
And when you tell CEOs or C-levels that it could be a million dollars if we don't do this, you tend to get their attention faster. It is still a place where we have to be a little bit creative. I call it content strategy. It's not creative. It's thinking about who's my audience and what message will most impact them.
So for the CEO, we talk about money and how much this could cost and how much it could hurt us. For the design director, the creative director, we look again at the number of people with accessibility issues and that sliding spectrum, right, of situational and temporary to help remind them this is actually a huge portion of our population.
It's not 4.8%. That's inaccurate. It's most people. And so we need, as good designers, as good UX researchers, we need to design for everyone. That helps. I think persistence and examples are really the two keys. If we can find examples of other people doing it well and having good results and share those results around, it makes the case for us doing it as well.
I hope that helps. Jackie asks, are there any tips or tricks about working with and for neurodivergent folks? That's a great question. And to your earlier point, like some folks aren't diagnosed, so they don't know. As a human centered person, my first response is ask them, sit with them and talk and sit with them the way that they're comfortable.
Anyone, right? And I think it's, I think it's less of a targeted, hey, you seem neurodivergent. That's not, not cool. But it's more of listening to people and watching people observing when they may be struggling with something and then asking, how did that feel for you? Is that a normal experience for you? Is that something like, how would you like for it to feel?
I think talking about desired future state is really helpful and saying, I realized that it wasn't as comfortable as it could have been. What would feel better? How could we do this differently? And inviting them to share their experience without judgment and without critique, just taking it and saying, thank you. Thank you for sharing that with me.
I'd really like to try this again. So I'm thinking specifically of user testing. When we do design work and we have a prototype that hasn't gone live yet, but we want to make sure that it's workable. We'll try to find folks across a wide spectrum of people who might use this and ask them to test it out.
And a lot of what we do is not correction. It's just observing and listening and asking questions. Questions are kind of my default. I think that's a really great way to to ask. But also, I think it's really fair to say, do you mind talking about this and see if they're willing to or if it feels too uncomfortable?
Because I think what you'll find is that a lot of people haven't felt heard and having a chance to tell you about their experience changes their point of view and it gives you more information. Laurie says, have you received comments afterwards that others without disabilities noticed the design improved for all? Not directly, but I am notorious for testing things on my mom and my grandfather.
My grandfather has just figured out how to use a smartphone at 86. And so I will send him things and just see how he responds to them. And he's not diagnosed with anything, but he's 86. And so there are some things that I know that he will pick up on and he'll say, oh, that moved too fast or I couldn't read this.
And he just sort of gives feedback. So I do think that we haven't done a ton of research into actually getting feedback on that specific topic. But we have seen overall the satisfaction goes up across the board for taking into consideration some of these extremes. I'll be honest, I've noticed I'm almost 40 that I squint more and I stare at the screen more with my eyes squinted shut and like trying to parse language and words and websites that have poor contrast actually annoy me.
And I didn't notice up until this year after COVID that my eyes have maybe not been as good as they used to be. And so it's, yeah, I think even personally, anecdotally, I think it's really helpful. Vijaya says, is there a place where developers or designers can learn more about accessibility? That's an excellent question. And I really want to have a whole separate thing on developers and accessibility.
When I post this, we will make sure that we post somewhere all of the resources for designers and UX folks. But also for developers, I want to pull a whole sheet of resources for developers to learn about accessibility. So this is a lame answer. But if you follow me on like LinkedIn or Twitter, I promise in the next couple of weeks as this video is available, we'll start sharing and posting.
Or if you follow Struck or if you follow Women in Tech, I'm sure that they'll retweet and share. But we will make sure that those resources get collected and put in one place so that they're readily available. And I'll see you in the next couple of weeks. I'll see you in the next couple of weeks. You're exactly right.
And that's why this is sort of only half a talk because the other half is the developers. The other half is the people writing the content. UX writing is a really thoughtful space to look into because it starts to talk about how words make meaning and how we reassure folks with our words on a website. That what they're doing is correct.
And that what they think is going to happen next will happen next. But you're right. It's development. Again, if we don't have conversations early and often with developers, we're not going to have conversations with developers. We're not going to have conversations early and often with developers. So I'll see you in the next couple of weeks. I'll see you in the next couple of weeks.
We don't have conversations early and often with developers to understand what they can do. And we don't make the case for even if my development team can't build a certain accessible feature that I need. We'll talk about vendors. We'll talk about a third party. We'll talk about a freelancer. We'll talk about some way to get it in so that we are able to make sure that this product goes out the way that it's supposed to.
That's a really great point. And again, I think the workshops create a really lovely, even open space where everybody has the same experience and then can comfortably talk about it later. And then Amy has great advice, actually, in response to Jackie's question about how to talk with folks who are neurodivergent. Amy says, as a neurodivergent person, patience in conversations and checking for understanding by paraphrasing is super helpful.
For example, is this what you meant? In therapy, we call that mirroring, right? Where I heard you say this. Is that what you meant? This is what I think you said. Did I understand you correctly? And then talking probably slower than I did today and being patient and having the same conversation, maybe a couple of different ways until you get through to the answer that both parties feel hurt and feel like they got what they needed out of it.
Thank you, Amy. Terrific. Well, I think we're at time. Thank you so much for joining us. I really appreciate it. And I hope that you enjoy the rest of your conference.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why accessibility belongs to designers from day one
Jess Vice explains why UX and design must own accessibility from kickoff and how her agency ran a hands-on workshop to make it stick.
In short
Jess Vice, Strategy Director at Struck, argues that accessibility is foundational UX and design work that has to begin at project kickoff, not a compliance task handed to developers at launch. She makes the case through the disability spectrum, the idea of designing for extremes rather than averages, and a stark cost comparison, then walks through how her agency planned and ran a hands-on accessibility workshop for its creative team.
Key takeaways
How designers can level up their ability to be inclusive and create accessible work by using tools that solve problems that are new to them.
How to build an interactive workshop, including using assistive tech (like voice to text) and other platforms, to elevate the accessibility of the things we create.
Designing for averages is an exclusive and privileged approach. When we use the extremes to shape the problem we're solving for, we often catch most of the middle in the process.
Creatives can build an interactive workshop, including using assistive tech (like voice to text) and other platforms, to elevate the accessibility of the things they create.
Disability is far more common than skeptics count
Vice opens with a definition: accessibility is a state where any user, at any time, can get the information or goods they need with little to no difficulty. She then takes on a familiar objection. People sometimes count wheelchair users, people with canes and people with guide dogs and conclude the group is too small to matter. That narrow list, as the speaker cited, is 4.8% of the US population, and it leaves out cognitive, learning, neurological, auditory, physical and visual disabilities.
Drawing on Microsoft's inclusive design toolkit, she describes disability as a spectrum of permanent, temporary and situational conditions. "Every one of us has ended up in a situational disability environment where we can't access the thing that we need because of what's going on around us." (3:58) Later, citing a CDC infographic, she notes that 61 million American adults, one in four, live with a disability.
Design for the extremes, not the average
Vice credits Jared Spool with a principle she returns to throughout: do not design for averages. Personas often collapse a whole group into one representative person, which smooths away exactly the people a product most needs to serve. "When we use the extremes to shape the problems that we're solving for, we often catch most of the middle in the process." (4:47)
Her favourite illustration is the curb cut effect. Ramps built into sidewalk corners for wheelchair users, particularly veterans, ended up helping parents with strollers, older people, children on bicycles and delivery workers. She adds digital examples: Apple's VoiceOver screen reader, colorblind modes in Fortnite, the game Two Dots layering shapes over colors, captions spreading to TikTok and Instagram, and Venmo's unlabelled navigation icons that confused even tech-savvy users until labels were added, something Google's Material Design system recommends from the start.
Why UX and design own accessibility
Vice frames UX practitioners as experts at getting to why, at communicating research and at advocating for users. "The very first rule of user experience is this. You are not your user." (11:42) Because UX and design kick off every project, she sees accessibility as their job from the beginning: "So expecting the development team or the compliance team to show up at the end of a project and say, oh, hey, what about accessibility is really irresponsible on the part of UX and design." (10:30)
She also stresses partnership with developers, since nothing designed reaches the real world without them. Then comes the business case, from a case study she read. Regular small checks cost about $100 each, roughly $600 for a fully accessible launch. Retrofitting at the end, often with a third-party vendor, came to about $10,000. Launching without accessibility work and facing a lawsuit under requirements such as WCAG and the ADA came closer to $1 million.
How Struck ran its workshop
Vice is candid that Struck is far from perfect, but the workshop gave the team a starting point. Planning came first: pick a date, put it on calendars, share articles, post in Slack and send emails. She advises warning people that there will be a hands-on activity, because everyone gets awkward.
Research followed. The team gathered US disability data from the CDC, health departments, special interest groups and local nonprofits, and listened to real voices in forums and Facebook groups. Rather than criticise others, they used their own websites and design work as examples.
On the day, a short presentation framed the stakes, then people rotated through stations every 10 to 15 minutes, with a timekeeper moving groups along. Her strongest tip is to put a guide at each station: the one unmanned station got lost. Activities included a colorblind app and browser plugin, a colorblind test (the CEO turned out to be colorblind), a contrast checker against WCAG recommendations, a screen reader, closed captioning and brainstorming on physical spaces. Other ideas include a sign language interpreter, readability scores and a field trip. "But we've found that trying new things together really breaks us open and grows our understanding of both each other and the experience that we're talking about." (22:53)
Making it stick: implementation and better questions
The shared experience creates accountability. After the workshop, the team published the data, linked every tool in the internal wiki and sent a survey. Vice has since seen designers fix low-contrast colors on their own. Most important, she says, is speaking up. "But once you've been educated on something like this, it's not comfortable always, but it's definitely your responsibility to say we could do better." (25:34)
To do that without blame, she suggests asking questions: who has been included, who has not, who benefits, who is hurt, whose voice needs to be heard and how to do better next time. In the Q&A she explains how she handles objections by tailoring the message, cost for CEOs and the size of the disability spectrum for creative directors, and how to work with neurodivergent users by observing, asking and listening without judgment.
Watch the talk
"Accessibility is a design and UX responsibility: How to run an Accessibility workshop" by Jess Vice, 39 minutes: https://www.womentech.net/video/accessibility-design-and-ux-responsibility-how-run-accessibility-workshop-jess-vice
About the speaker
Jess Vice is Strategy Director at Struck, where she offers qualitative and quantitative research with software, product and SaaS users and turns it into data-driven product strategy recommendations. She has worked in CRO, marketing, SaaS and product for over 12 years and writes and speaks about what she is learning.
Questions this talk answers
Why is accessibility a UX and design responsibility rather than a developer or compliance task?
Is disability really a small share of users?
How do you set up an accessibility workshop for a creative team?
How do you respond when leaders say accessibility workshops waste resources?
How can teams work better with neurodivergent users?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Curb cut effect
Permanent, temporary and situational disability spectrum
WCAG
ADA
GDPR
Flesch-Kincaid readability scale
You are not your user
Mirroring
Resources mentioned
Microsoft inclusive design toolkit
Apple VoiceOver
Google Material Design
Flesch-Kincaid readability checkers
Contrast checker
Colorblind app and browser plugin
CDC disability infographic
Cite this talk
Jess Vice. "Accessibility is a design and UX responsibility: How to run an Accessibility workshop." WomenTech Network, 2022. https://www.womentech.net/video/accessibility-design-and-ux-responsibility-how-run-accessibility-workshop-jess-vice