
On October 6, 2020, Accessibility New York City hosted a meetup entitled “5 Things I Learned from the Accessibility Community.” Presenter Marcy Sutton, freelance web developer, accessibility specialist and founding member of the Accessibility Seattle Foundation, offered her unique perspective and professional experience surrounding the realities of working in the field of inclusive design. She shared 5 key lessons learned over diverse career in accessibility and digital inclusion. Slides from this presentation can be found here.
Here are some of our highlights from the presentation:
- Disability and accessibility communities are not always the same
- Laws and guidelines
- Working in Accessibility or the Mainstream
- Testing often for user impact
- Accessible doesn’t mean boring
Transcript: 5 Things I Learned from the Accessibility Community - Marcy Sutton
MARCY SUTTON: All right. So... Tonight I'm gonna talk about some things that I've learned from the accessibility community. Over about nine years or so of working in the industry. I've been a web developer for 11 years, getting paid for it, at least. I was aspirationally a web developer before that. But I didn't know anything. And that first two years, I didn't know anything about accessibility. I mean, I'm sure I was putting click events on divs and not really knowing what lists or buttons were for in HTML. And so over the past nine years, I've learned quite a few things. And so tonight I'm gonna tell you some of those things.
This is one person's perspective, though. So if you have another perspective, that's super valid, and we all make up this patchwork of passionate accessibility specialists around the world, and our experiences will vary. And that's a big theme that you will find throughout all of this. I really try to pay attention to those other perspectives, and really uplift and listen to other voices as well. But these are a few years that I've learned in the nine years. You can find me on Twitter @MarcySutton, also on GitHub and Instagram. I share content periodically.
But let's hear what else I've been up to. So a bit about my background. As Thomas mentioned, I worked on the axe-core testing library for a while at Deque Systems. I worked on the Open Source JavaScript engine, the browser extensions, various other tools at Deque, so I got to see behind the curtain of an accessibility company, and I'll talk about that a little more later. I'm also lead admin of the web accessibility Slack.
And that is a community that has existed for five years now. And if you want to get into that group, it's currently invite only by email. Any member who is in there can invite someone. We locked it down a while ago to prevent abuse of open Slack communities. Currently exploring different options to make that easier to get into. But you can always tweet at me.
I believe there's also a dedicated Twitter account now called @a11yslack on Twitter. So you can DM or hit up that account, if you're having trouble getting into the Slack group. There are some really great archives in there that you can search, and ask a global community of passionate experts for help if you have questions. In the past, I've done some screencasting for egghead.io, teaching people how to code for accessibility, I have some new things coming out in the future, working with egghead. Most recently, I worked as the head of learning and then a lead developer advocate or lead developer relations engineer at Gatsby, which is an Open Source website generator.
I have also been a part of the a11y Seattle Meetup for a while. We're currently figuring out our new normal with COVID as well. Without physical events, figuring out how to make things that work with all of our webinar fatigue that I think we've all been feeling. So it's really great to see this group come together tonight, with people around the world. I'm thrilled to be here with all of you.
So what else am I into? Well, my big passion, aside from accessibility, is getting out into nature. And I have a photograph on the screen of a recent hike that I did, where I actually baked a pie earlier in the week. And found enough room in my backpack to cart along a slice of pie, and I ate it at sunrise. So these are my two big passions in life, are accessibility and the outdoors. And photography plays a big role in that for me, in that I can go to these really remote places, have the physical exertion and energy to be able to get out there, there's some really inaccessible places that are hard to get to, and photography is a way for me to transport my friends and colleagues and people into these
spaces that are not very accessible. And having a slice of pie just made it extra special.
And it's kind of funny. I was going back through old photos on my new laptop, and I found a photo from a conference I spoke at in Switzerland, called Uphill Conf, and I did a talk there called Empathy Driven Development. And that was a really fitting conference, since I love the mountains so much. But when I look at an image like this, I see already -- I can think of things that I've learned since then. Like... I prefer to use the word "compassion" over the word "empathy". Because when I'm talking about accessibility, I mean, empathy is a good word. It's a good concept and a good thing to aim for. But I can't fully understand what someone's experience is like. If I don't have the same perspectives, the same abilities, so having compassion for someone's experience to me
resonates a bit more. In that I can have a heart and feel for what they're going through, but I don't exactly know. So even -- I look back at things like this, and I can think of how much I've learned, even from being there as an expert, speaking on a topic, so what I want -- I guess the first takeaway is just to know that we're continuously learning. People you consider experts are people too. And they're learning. And growing. Myself included.
So my biggest growth recently has been that I've struck out on my own as a freelance web developer. And as of yesterday, I have officially started my own business called Modern Sole Design. And you can consult with me to review designs for accessibility, do some UI prototyping and engineering, manual and automated testing, that's a bit of my specialty, writing documentation, since I have all of that background as the head of learning at Gatsby, I do paid talks and break and learns for teams, as well as workshops and training.
And office hours for accessibility. So that's what I'm up to now. And if you have a need for that kind of thing, you can get in contact with me on my website. It's MarcySutton.com, and on my contact page, I have a form. You can contact me there.
So today, we're gonna talk about five things. I've learned definitely more than five things. But these are the things that are really coming to the surface for me in this moment. And that includes disability and accessibility communities. Laws and guidelines. Working in accessibility versus the mainstream. So some career development topics. In the practice of developing for accessibility, testing often for user impact, and accessibility doesn't mean that a design has to be boring.
So let's dive in. And why do I care about accessibility? What is it about accessibility? For me, personally, it's that I care about people. Even if people are frustrating, sometimes, infuriating, I care about them at the end of the day. I care about people's experience.
And as technologists, we're in positions to remove barriers and make the web a more accessible place. And I don't know about you. But that gets me out of bed in the morning. It really makes me excited about work. And I love that they're within the whole range of roles in our industry -- there's different ways that we can contribute to making the web more accessible to people with disabilities. Like, that's huge for me. So hopefully I'm guessing with this group -- we probably have a lot of that in common. No matter whether you're a developer or a designer or QA, project manager, the whole gamut, we can all make an impact with accessibility, and that's what it's all about for me. Because in the US, one in four adults has some type of disability,
and I've found some statistics from the Centers for Disease Control and Prevention, breaking down the experience of people in the United States and globally -- there's so many people who are affected by disabilities in all different forms, and so for the web, that's huge. I mean, that's more than IE8 or IE10 or whatever old browser versions you're expected to support. Accessibility is huge. And how we can impact the designs that we put out there in front of people... You know, if they're not accessible, that's leaving out a huge segment of people.
So the disability spectrum -- I mean, different ways that we can make a difference, including but not limited to the cognitive experience, for someone with autism or a traumatic brain injury, learning disabilities, hearing, with deafness, hearing loss, motor disabilities, like spinal cord injuries, cerebral palsy, or ALS, for people with vision disabilities, like low vision, blindness, color perception, and so many different experiences that people have, that it really is a spectrum. And so I try to really keep that in mind, when I'm thinking about accessibility. It's that to me, it's about disability. And people with disabilities. And that's really what I'm trying to make -- who I'm trying to make it better for.
There's the perspective that your life can change at any time. Like maybe you don't have a disability now, or someone in your family doesn't, but that could change. You could have -- you could lose an arm. You could have an arm injury. You could be a new parent or have a cup of coffee in one hand. The permanent versus situational disabilities, and I've long appreciated Microsoft's inclusive design toolkit, which has some of these personas that you can use to talk about accessibility in different ways...
But there's also the perspective that accessibility should be centered on people with disabilities. And that leads me to the first big thing that I've taken away or learned from the community. Is that disability and accessibility communities are not always the same. Sometimes there's overlap. Depending on who you're talking to. Or who is speaking. Who is doing the work. Who is using the website. But they're not always the same.
And when this first really started to enter my consciousness was this tweet that I saw from Matt May, who, fun fact, was my manager for a little while at Adobe. And he said: Accessibility protip. If your timeline is not flooded with, quote, "Brian has a wheelchair!" Tweets, you are following accessibility Twitter and not disability Twitter. Consider branching out. Or possibly your friends don't watch Game of Thrones. But that's way less likely.
And I went... Oh yeah. He's got a great point there. That accessibility communities are typically speaking about technical things. Design questions. The practice and the industry of making the web more accessible or technology more accessible.
Whereas the disabled communities are talking about their experience. The barriers that people are facing. Legislation that's being passed. The different types of topics that might come up.
Okay. So Matt May's got this tweet. That got me thinking. So I expanded who I was following on Twitter. Including people like Imani Barbarin, Crutches and Spice. And she has this quote: #AdaptTheFeed is about saying enough is enough. Disabled people saw how quickly the things we have been calling for were made available now that non-disabled people needed them, like remote work when COVID came around. She said: We want change now. You can commit to accessibility outside of a pandemic too, you know? And her feed has so many interesting insights about all kinds of things accessibility-related. And on #AdaptTheFeed, she had further commentary, saying: Adapt the feed is for the disability community and anyone committed to disability representation and inclusion. And this really hit home for me. She said: Disabled people find themselves adapting to an inaccessible
society constantly. So now it's your turn to adapt your content and social media feed to not only accommodate disabled people, but elevate our voices and include us in your work. And Imani Barbarin's website is Crutches and Spice.com. So this concept of -- if you're sharing things on Twitter or really any social media, making sure you have alt text, making sure you're sharing videos with captions, and Twitter is often a place where we're sharing our work that we're doing elsewhere in the industry. So sharing a website that you built.
Or a talk that you did. Or really anything. So she's talking about the social media feed. I would take that -- that's the messaging channel for anything else that you're working on.
So trying to make sure that content and those projects are accessible from the ground up, and really elevating voices of people with disabilities in the process...
And I also saw tweets from people like EJ Mason. They said: At one point, accessibility is so draining. I need to find rituals that help me destress and turn off my work brain. Trademark. I know. I'll order myself delivery. And then, five minutes later, they say... DoorDash says keyboard users can get effed, I guess. So they're working hard. Doing their job as an accessibility specialist. And then trying to get some respite later in the day, and just hitting accessibility barriers. So there's a privilege for non-disabled workers in accessibility, that you can sometimes turn that off. You can escape accessibility needs at the end of the day. And use your mouse. There's a workout channel on YouTube that I've found, that the teacher doesn't actually
say out loud what the exercise is. So I have to be able to see the screen. And that's such a huge privilege. That extra tiredness at the end of the day -- you aren't having to experience. And so this is why it's so important to really listen to what people with disabilities go through.
So that you understand what the stakes are. For what we're trying to put out there on the web. Because accessibility is really about supporting disabled people first and foremost. You can't separate the two. You can't talk about accessibility or work toward accessibility and just focus on the technical challenges. It's not really what it's about. And so I always try to remember that. And highlight that, for folks. So you know why we're doing it. Because that helps you get answers. And know who to talk to, to get more information. And those nuggets of information you can get through user testing and interviewing people who are impacted by the barriers they experience, just adds so much more information and meaning that you can put into your work.
And I love this quote from the Alliance for Inclusive Education that says: What disables people are the barriers that society creates for people with impairments. And as designers, developers, really anyone putting content and applications on the web, or native as well... You might be the person creating that barrier. Without realizing it. So you are part of that society and that system that is oppressing disabled people. So... Mind blown! For me to go...
Wow. I can actually make a difference there. And I can tell people about it. And then they can make a difference. We can make a difference! For people with disabilities. And I really love that.
So listen to more diverse perspectives. Follow disability Twitter. The #a11y hashtag. There is so much great information about what people are going through.
That really can give you that oomph that you might need to go... Okay. Yeah. I'm gonna really knock this project out of the park for accessibility. There's also the a11y hashtag, which is great.
It's kind of a practitioner area. Talking about websites and the practice of accessibility. It's super valuable as well. It's good to get all of the information you can, if you're on Twitter.
Disability Twitter is pretty great. So diversify your feed. That's the takeaway. Okay. Moving on... Laws and guidelines. This was a big one for me. Because I came into accessibility for the passion and the heart of it. And the curiosity, and the further I got into my career as an accessibility engineer, the more I learned about laws and guidelines. It's not that I really wanted to. I think I've sort of skated by, not having to worry about that part as much. That's a bit of a privilege as well, in that... If you have a disability, the law is a tool that you can rely on to try and get your... Have a space that's more accessible to you. You might need to really have the law in your pocket on that one. So it's important to know about laws and guidelines,
as accessibility practitioners. And for me, that really... Even though I kind of ignored the guidelines and the laws at first, really the big impacting event for me was working on projects for Target. The case with them and the National Federation of the Blind, back in I think it was... 2009? Is when they -- decided 2006. And the Wikipedia page...
You know, Wikipedia is normally not where I go to for... There's some historical information about the case and kind of like... What the NFB was... What they wrote to Target, what they were asking for. And there's some examples of, like, how that process went.
And as an agency partner, everything that I made for Target had to be accessible. And that was my introduction to it. And this was a big case for accessibility. And they referenced -- they were trying to get Target to optimize its website for the blind by adopting standards from the W3C, including the Web Content Accessibility Guidelines.
And section 508 of the Rehabilitation Act of 1973. So they pointed to those guidelines back then in 2006, and that's really the first I ever heard of it. Was thanks to this law case. So the Americans with Disabilities Act and Section 508 are part of enforcing user civil rights in the United States. So these are the things that people have in their back pocket to lean on, because it has been legislated on, and so this is the part in the United States that we talk about, with accessibility. And a lot of the guidelines around the world rely on some of the same guidelines that these point to, which is the Web Content Accessibility Guidelines. We'll talk about that more in a second.
In the legal space, the person that I really respect the most and know about the most is Lainey Feingold. And she has a book called Structured Negotiation, which I would highly recommend. She cheekily describes herself as the attorney that doesn't sue people. She has this Structured Negotiation process of working with organizations to come to an agreement about how to make an application or a website more accessible without litigating.
And she puts out these legal updates every year. There's one from July, when the Americans with Disabilities Act turned 30 years old. You can read about her legal update to learn about what's happening in the legal space. And this is something that I really grew to appreciate a lot. In the last...
5, 6 years, I would say, of working in accessibility. Was understanding the legal space. And Lainey is a really great person to follow. She's just been writing today or yesterday about some legislation being proposed about the ADA. So you can really keep your finger on the pulse of what's happening there, by following Lainey and reading her book.
So around the world, there's other global accessibility requirements. Like Canada's Accessible Canada act, the EU Accessibility Directive, various equality acts and bills in places around the world, and Lainey again has a blog post on her website that is updated periodically with all of the global accessibility requirements. But pretty much all of these that I've looked at reference the Web Content Accessibility Guidelines. Or WCAG.
As I've heard. It's not a trivia question, but -- how do you pronounce it? I call it "WICK-ag". So it was a recommendation back in 2008 and it's really a standard for the success create of how you make something accessible. And it's broken down into four parts. Perceivable, operable, understandable, and robust. And within that, there are individual guidelines, there are different levels, level A, AA, and AAA. Double A is usually the standard that people aim for. Or companies aim for. AAA being -- if you can meet it, awesome. Do it.
And so WCAG I really grew to appreciate more over time as well. In that it's a sort of road map of how to codify some of these details of how to make things work for people with disabilities. And it's been evolved over time as well. There's the WCAG version 2.2. Which is in a working draft and I think will be published next year. So in between, we've had WCAG 2.1. That's the current standard. And so it's good to sort of keep an eye on what's happening. You can provide comment when things are in certain phases. Like I think WCAG 2.2, they had a comment period that may have just ended. And so that's a really great thing to keep on top of. If you have time and you're interested.
At the very least, referencing the most recent published version, which right now is WCAG 2.1, can be very helpful to know what do you have to incorporate into your practice as a web developer? Or accessibility specialist? To keep things current. So about the WCAG versions. 2.0 was published back in 2008. 2.1 was published in 2018. How time has flown! It seems like just yesterday. And then 2.2 is scheduled to be published in 2021.
And the W3C's Web Accessibility Initiative is always up to date. That's the place that I go to learn the most up to date information about what's happening with WCAG. And you can go real deep and really detailed into WCAG for sure. And so I think for me that's why maybe I just tried to work on the mechanics of accessibility and sort of the practical user base scenarios, but as I got more professional with it, and more detailed, really, on the job, that's where WCAG becomes more and more relevant. And if you've used any testing tools recently, you might see little breadcrumbs of WCAG popping up. Because the usefulness of accessibility testing tools comes from the fact that they are really written to support WCAG.
So on the screen, I have a screenshot of Rover.com, the petsitting website. And I ran the Accessibility Insights for Web Chrome Extension on it from Microsoft, that uses axe-core under the hood, and this site had a couple of color contrast issues. And this is what could be automatically detected, at least. And so like the search buttons got a little red highlighter box on it to show me that that's what the tool has found. And I've got an arrow pointing to the spot where it says WCAG 1.4.3. So the automated check is telling me which success criteria from the Web Content Accessibility Guidelines it's referring to. So that's a great detail to pay attention to. Like, what did it find? What is it referring to? Where do I go learn more information?
Or is the result I'm looking at in axe or whatever tool -- is it even based in a WCAG success criteria? Or is it a best practice or something that's kind of a nice to have, if I fix it? So if I've got that little clue, that little detail of the success criteria number, I can go over to WCAG's understanding documentation and read more about what the requirements are. For example, for minimum contrast. So in a nutshell, you have to have enough of a ratio between your foreground and background colors, and that's written in detail here in WCAG 2.0. And I didn't mention it at the time, but with WCAG 2.1 and then 2.2, they are backwards compatible. And they contain everything that was in a prior version.
So we're looking at contrast from WCAG 2.0. That's the same guideline that will be in 2.1 and 2.2 and so on. So it's all encompassing. They were just adding on new success criteria for things like cognitive disabilities, mobile devices, and things like that.
So if you're using automated tools, which are great, totally love them, totally use them all the time, however... There's some big gaps. And they can't catch everything. And there's a famously awesome article from Manuel Matuzovic, called Building the most inaccessible site possible with the perfect Lighthouse score.
So Lighthouse also uses axe-core under the hood, and his blog post successfully illustrates why automated testing is not enough at the moment. So there's a lot of things that you can accidentally let into your websites and web applications that current tooling will not catch. And a lot of people think they're fine. They see the 100% score on Lighthouse and they're like... All right.
I'm done! But unfortunately, there's some big gaps that you could have missed. And so I love this blog post. Because it goes into detail of what some of those things are.
So I would read that. And while you're at it, another one of my favorites is a blog post from Eric Bailey, who I think is here tonight. I saw him in the chat! His post on Smashing Magazine called The Importance of Manual Accessibility Testing is a long time favorite of mine as well, from 2018. I like Eric's gentle approach. He's frank. He's not beating around the bush about the problems. But he's also kind of gentle about it.
Because we want to win people over. Like, I hear a lot about accessibility as like it's too hard. And I don't get why it's so hard, and there's all these differing opinions and all of that. The more we can kind of... I don't know. Persuade people to really dig in and understand trade-offs and be like... Come on! It'll be okay! We can talk through these differing opinions. I think Eric's style is really great at accomplishing that. And manual accessibility testing is a huge part of the practice. Because automated tooling only goes so far. So I would highly recommend this blog post on Smashing, from Eric Bailey.
Because it'll further help you understand where the line is of what you can automate, what you need to test manually. Because manual testing is never going away. At least, I don't think so.
Okay. So working in accessibility or the mainstream. This is a good one. A bit of career development. So this is definitely more of a personal experience kind of thing. But hopefully there's some nuggets of wisdom in here, for all of you. So I get questions a lot of like -- should I go work at an accessibility company? Should I go -- what should I do with my career?
And I've done a lot of various things. I went from mainstream into accessibility. Back to the mainstream. Now I'm back in accessibility. So accessibility companies in my experience...
They're more specialized. So the products and services at an accessibility-focused company like Deque or Paciello Group -- those kinds of companies -- that's all they do. There is some really valuable internal knowledge there. Getting to see a mailing list or a Slack conversation from recognized awesome experts in the industry -- amazing. Super valuable. You can see conversations of, like, well, how would you -- they're trying to align on how they would audit a certain feature or a certain web page, to know which success criteria does this meet or not.
And all of those discussions are so interesting. And that's hard to get anywhere else. I mean, maybe in the accessibility Slack. That's a good place where some of that stuff is discussed.
But the professional level behind closed doors conversations are super valuable. There's usually company alignment on accessibility. Like, you don't have to convince anyone of its importance. That's not typically where you're meeting friction. I guess it's possible. Hopefully not.
But as opposed to mainstream companies, there's typically more alignment on accessibility being important. So here's an interesting one. And this will super vary, but in my experience, the roles at accessibility companies are potentially less competitive. So some of the technology might be old... (dog barking) My dog is now barking. So... The roles... Just like the tech stacks might be a little dated. You might not have as much choice. The pay may vary pretty widely. There might not be a lot of data out there to know, like, how much money can I make in this role?
I guess on the other hand, you can potentially get a really competitive offer. And so that's sort of... I don't know. A space you have to navigate when you're interviewing and hiring at a company. I've heard this one a lot. Subject matter experts feel their development skills atrophy. Or kind of like... They suffer. Whereas they're focused a lot on auditing and reviewing accessibility things. Not so much on engineering. So if you're okay with that, awesome. If you're worried about that, maybe talk... You know, to your manager or hiring manager. Find ways to keep those skills sharp. If that's something that's important to you.
And it's a really small world. So a lot of people in the accessibility industry have worked together. We know -- a lot of us know each other. We've got some baggage. We've got some dirt. We've got some drama. It is a really small world. So burning bridges is not so good. I don't know. It's kind of hard to avoid sometimes, when you have disagreements, or things just don't always work out. It's just part of it.
So trying to conduct yourself professionally and... I don't know. Just know that people talk and we know each other, and it's a pretty small world. It's a niche part of the industry.
So in comparison, in the mainstream, you probably have wider reaching products and services. So websites that a lot of people use. I guess if you're a subject matter expert at an accessibility company, you might be consulting on some of those wider reaching products or services. But you might not be an owner of it, necessarily. So your relationship to it, to the work, is different. So if you're at a product company and you're working full-time on something, your goals are about that product. And that's what you're working on all the time. So it's worth asking if you're going to a mainstream company and you want to work on accessibility...
What's the culture like there? Do they have internal specialists? Is there an accessibility team? Or is it like Twitter where they had all volunteers?
It's gonna vary. And that might change how supported you are. It could drastically change your experience. In the mainstream. Are you a lone champion, trying to right a big ship? That's gonna be hard to do. It's gonna be hard to succeed if you're the only one. It's worth asking like -- what's the landscape like for accessibility here?
Am I the only person who cares? Might be kind of an uphill battle there. The company size, type, and culture can really affect this as well. So if it's a tiny company, like a startup, if you are the lone accessibility person, maybe it could work out with the right group of people.
Because you have less bureaucracy. Potentially less friction. The people you're working with are really open to learning and they pick it up. It could work. But maybe not. I don't know.
I've also... You know, struggled when I'm like... How do people not... I've been working here for a year. How do they not... How are they still shipping accessibility antipatterns?
It can be a little painful. You've just got to keep on trucking. Because there might be less company alignment on accessibility. And that can be frustrating.
And like any company, and this is true at accessibility companies too, you're probably gonna have to work through some friction. This is my most recent thing that I personally have been overcoming, is working through friction. And you have a whole bag of techniques you might use. Depending on the person you're trying to persuade. They might respond to the carrot approach. The go talk to legal and make their life hard if they don't adopt accessibility... Or no, that's the stick. Sorry. I got it backwards.
That's the stick. To poke and prod someone to do the right thing. Whereas the carrot is more the -- hey, the cool kids are doing it. And you're kind of dangling the carrot to persuade someone that way. And so how you convince people to make change with accessibility... Can totally vary. When you have less company alignment on accessibility. You know, what succeeds?
You might need to try multiple things and go find different techniques to get stuff to stick. So there's definite differences in working in accessibility, versus in the mainstream. It's really all about: What do you want to do with your career? What do you care about?
Where do you want to go? What are your values? For me, I wanted to have an impact on more than one website at a time. I was working on individual client sites. I was like... Man, I really want to, like, have more of a wider reaching impact. So I went to work on frameworks. Like Angular.
I worked on accessibility testing tools, which got really specific and really niche. And then I opened it back up to the mainstream, to have that broader impact again. So it might... You know, what you want to do can evolve, but it's all about what you want to do to get to where you want to go in your career. And what you value and the kinds of things that you want to work on. But no matter what, accessibility skills are highly employable. Super competitive.
As a hiring manager, if I have two candidates, and one has accessibility and the other one doesn't, guess who I would hire? The person with accessibility! And it's a very sought after skill. So highly employable. You can try different roles over time.
So if you're doing the SME thing and you want to get back into engineering because you're just missing it, do your best to keep your skills sharp so that you can go back to it. But I've seen people go into management and then back into individual contributor work. That's what I did. So you can try different things out. You're not stuck in the same pathway forever. But the further you get away from expertise, the harder you're gonna have to work to get back. Make sure you're asking about salary ranges and levels when you're interviewing for something. To know kind of like what the pay will be like. Talk to people who've worked at the company, to see... You know, what's the dirt? Was it a good thing or not?
Do work that you can believe in, with people you trust. And maybe I'm a little naive, or idealistic or something. But the more I've been in this industry, the more I care that I am working with people I trust. And doing work that I care about.
So here's some bonus questions for you to steal. And if you're considering an accessibility role, who you're asking these to will kind of change what exactly you're gonna ask them. Whether they're the hiring manager or a friend you've got, who just happens to work at the company. Whether they work there now or they used to. So here's a good one. How are accessibility impacting decisions made? You know, if I have to recommend something for accessibility, and I hit that friction, ultimately, who has final say?
How does accessibility fit into your road map or your process? Is it just kind of like... Oops, we forgot it! Let's try and shoehorn it in at the end. You're gonna be in for a world of pain.
Or are they more proactive? And thinking about it earlier?
How are disability representation and diversity at the company? Is there anyone with a disability that works here? Is the HR tooling completely inaccessible? So that you have a harder time hiring someone with a disability? Those are good questions to ask up front.
On the personal kind of development direction, what's the path to promotion like for this role? Are there performance reviews? Is there even a track for me to go forward? I didn't even think to ask that up front at some of my jobs, and some of them... You maybe don't progress as much as you would like.
Great questions to ask if you have a friend that works there, or you get ahold of an acquaintance or somebody, and you can ask what they like about working there, what their least favorite part is, what kind of friction they encounter in their job. You can potentially sniff out some of the issues that can change whether or not you want to work there up front. By asking good questions. And really paying attention to what people answer. All right. So cruising through the rest, I do want to leave time for questions, so I'm gonna try and get the move on here.
So number four. Testing often for user impact. And the real purpose of this is to remove barriers iteratively. Like, all the time. So we're not shipping them without realizing it.
And we do this by making accessibility part of our web design and development workflow. And making it part of your definition of done. Get project managers on board. This is really the ideal. Is to try and chip away at it all the time. And not this, like, we'll add mobile in phase 2.
We'll add accessibility in phase 3. That is a huge red flag, if you ever hear those. I mean, the best place to be doing this is -- you know, I have a screenshot from GitHub on the forum project, which is dev.to's -- their community platform. When you open a pull request, they have some prompts for things like: Did you add tests? Have you added to the documentation?
You could add a line here that says: Has it been tested for accessibility? To prompt someone who is submitting the pull request. You know, this is the smallest scoped opportunity to try and implement accessibility. With each feature. With each shipment.
So as you're doing this, you can support users by starting with accessibility basics, like those always apply, form labels and image alt text and all those things. Using browser extensions and testing tools. Zooming in and out and magnifying your layouts periodically, to see if they break or if you can even zoom at all. Testing with assistive technology, baking accessibility into automated tests, and then actually testing accessibility use cases. Like do you have some alt text interface that no one actually uses, and it's awful? Testing those. So that they aren't just this product graveyard of failed experiments.
You can really support users by making these things part of your regular workflow.
I'd highly recommend taking the no-mouse challenge. So turning your mouse off. Or unplugging it. Or something one day a week or more. And related to this, I wrote a sort of joke, but sort of not, package called no-mouse days. Where I was like... What if we just turn the mouse cursor off for everyone? That would do it.
So you can play around with that package. It's on GitHub and on npm, if you want to take the no-mouse challenge and put it into your application for other people. Maybe not in production. But for your colleagues. And testing with screen readers.
This is one that would really help. Testing with -- on Windows, with NVDA and Firefox, on mobile devices, with iOS, on Android, and there are some great articles on screen reader testing. The caveat is if you're not a daily screen reader user, you might not even know what you're looking at, or what you're hearing. So hire people with disabilities to join your team.
That -- disability representation can be huge to getting perspectives surfaced earlier. You can also work with groups like Fable and Access Works. Potentially groups local to your area. To get that input regularly about your designs. Your prototypes. Your features.
Get that input all the time. And I would highly recommend doing that. And remember that you're not the user. Maybe in some small use cases, for your own side projects or something. But we're not the user. You just don't have the same perspective that users really will, when they're not as familiar with the design. They don't -- you're just not -- you don't have that bias. And so that lack of representation of diverse users and user groups leads to a lot of assumptions about what's safe or intuitive, that are not correct. So we've got to remember that. And get some usability and accessibility testing with real users with disabilities.
Okay. So... Our last thing before we break and have some questions... Time permitting...
Is that accessible doesn't mean boring. But simpler is often better for a lot of reasons. One of my favorites of a beautiful gorgeous fresh website is the recent a11y Project Redesign. I wrote about it on my blog, called Accessibility Wins, where I really try to highlight what's working. What's good? What's awesomely designed? What's innovative?
So if you've worked on something that you're proud of, that you think is innovative and fresh and cutting edge and all that, send it to me. Because I am dusting my blog back off and starting to write again. Because I think we need to celebrate the wins more. I know it's kind of fun to look at the fails. But I think the wins are important too. Especially since there aren't that many. Especially in this...
I don't know. Cutting edge design category. They do exist, though. And it is possible.
And a big part of this that's followed me throughout my career is this idea of simplicity being intuitive. And that making users think, assuming that somebody is going to hover or focus on something, to, like, get a visual label of what it means -- removing that, those steps, can make it a streamlined, easier to use interface, and I think that's super powerful. So Steve Krug's book, Don't Make Me Think, was super pivotal in my practice of becoming a web developer. So I would highly recommend that. Even if it's got some dated screen shots in it. The concepts still apply. And here's an example of some icons that maybe don't -- aren't as obvious to everyone. So there's four icons on the screen.
I mean, maybe depending on how old you are, you might have a guess of what they are. But I think of apps like some of the apps from Google, sometimes, it's really hard to tell what the icons are for. And without visual labels, it's hard to know that they mean save, home, menu, or stats. I mean, some of these are a bit conventional. Like the menu.
Hamburger menu. But who knows? I mean, there's an assumption right there. Is it obvious? Or not?
Here's one that I found this week. In Instagram. That's been really bugging me. Of the alt text interface on iOS on Instagram. If you have more than, like, really more than one photo and you go to add alt text, they don't show the image next to the text area that you have to fill in. So you have to use your cognitive abilities to remember what photo was in what order. I can never remember.
It also -- the keyboard covers part of the interface, when you're trying to use it. So I talked a minute ago about the product graveyard of failed experiments. Sorry, Instagram. But... Is anyone using this? Because it's painfully hard to use. And the cognitive part to me is like that having to remember ten images in a row to be able to fill in the alt text.
It's just really hard to use. So testing it early and often, getting it in front of people to get their feedback -- that would all have applied here. And then that cognitive complexity -- put the image next to the field. Make it easier to remember!
So there's established UI patterns that you can follow. Like, if you're really wanting to innovate, make sure you look there first at the ARIA practices guide. They are not production ready, but you can at least look through the mechanics and the navigation conventions for how a lot of patterns work. And you can use that as your starting point. So I would recommend that.
I would also recommend prototyping designs with code for accessibility. Prototyping with code, I think, is superior to prototyping tools. It's my own opinion and my own bias. And that's because a lot of prototyping tools maybe don't have accessibility built into them. With code, you can really get fine grained about how these mechanics should work for the keyboard and screen readers.
And prototyping up front can save costs long-term, because you've already validated: Is this going to be accessible? You know, we did a lightweight prototype, and yes, it will work. And you can even test those with groups like Fable. So prototyping is awesome.
And as you're doing that, consider input modalities in your software architecture. When you build the real thing. So that you're not, like, backing yourself into a corner. I think of back when we used jQuery, and everything was event driven. I click this, this function gets called, and I do this thing. If you do more of -- not necessarily using the React framework, but the way that React is more programmatic state changes, if you architect your websites and applications to be more -- responding to state instead of user input events, specifically, you can sort of trigger those user input events, but it makes it a lot easier to support things like pointer devices, keyboards, touch, speech, waving your arm with a motion gesture, or even changes in ambient light. Who knows what else will come up.
So if you kind of think ahead of time in how you architect your app to consider different input modalities, it's a good way to go. Save yourself from some technical debt.
And really all of this, this whole nine years of experience that I've sort of distilled here for 2020, it's all about user experience. Accessibility is about user experience. They're not separate. So we can all make it better. And we're all in positions to have our own little sphere of influence and our impact. And so I'm thrilled to have gotten to share all this with you. Because I feel like I'm in good company here, with people who care as well.
So let's make it better! We really have potential to make the web more accessible, as we learn more and we share with our friends and colleagues. So yeah. That's what it's about.
I've got some resources here. And I need to wrangle Git a little bit, but I'll try and get these slides up tonight. I've got some resources on my website, like books, testing tools, various learning resources and things. I have a Smashing Magazine accessibility workshop coming up in November. It's on Fridays and Saturdays. It's like two hours each day, over five days. Over like a couple of weeks. So you can check that out. If you're more on the design side of things -- because I do sort of come from design to development and back again -- I would highly recommend WebAIM's Accessibility for Web Designers.
Speaking of different input modalities and different ways of interacting beyond desktop, I love BBC's Mobile Accessibility Guidelines. I talked a little bit about working with Fable and prototyping. I wrote up some research on accessible client side routing when I was at Gatsby, and then the link to my accessibility wins Tumblr. So I'll try and put these up on the web. But that's it!
So thank you so much, everyone at Accessibility New York and around the world. I wish I could be in New York. That would be awesome. But with the power of the internet, we've come together!
So yeah. We've got time for some questions. STACY SMITH: Thank you so much, Marcy. This was amazing. And hello to everyone. My name is Stacy. I'm one of the co-hosts for tonight's Meetup.
Yeah. We've moved into the Q and A portion. So if you have any questions for Marcy, you can speak up. Over your microphone. Or you can type it into the Zoom chat. And for those of you who are watching on our YouTube channel, you can also type questions in over there. I'm watching you. Over there. And we'll happily bring it back to the Zoom.
So without further ado, go ahead and fire off, everybody. I know one of the first questions that already came up: People are interested, Marcy, in your slides from tonight. And if we will be able to make those available. MARCY SUTTON: Yes. I will tweet them a little bit later. So yeah. I just got a new laptop. And Git was not playing along. So I'll push them up and share a link on my Twitter, which is @MarcySutton.
STACY SMITH: Excellent. From Ryan, we have: What is the biggest takeaway that you have found in usability testing with disabled participants? MARCY SUTTON: The biggest takeaway I had was that even after working in accessibility and coming into it, with all of the knowledge that I had, I still had biases and gaps. That was the biggest thing. I loved working with Fable, and there's other groups as well.
It's really teaching you how to work, more than the specific thing you're solving. That was a bigger, broader takeaway. I was trying to get answers about client side routing. But I learned so much more about usability testing and I think that's a really valuable exercise for teams to learn how -- what is it like, when someone with a disability tries to use my app? Or this feature that we're trying to put out? Getting that feedback is amazing. So I would highly recommend it. STACY SMITH: Excellent. Okay. From Aurelia, she has a question regarding your previous points about HR and hiring.
Specifically about government agencies. She's wondering how you would tell or show a hiring manager that you have an accessibility skill, if you want to be broadcasting that, or using that as part of your sort of skill set, when you're trying to get a job.
MARCY SUTTON: Oh yeah. I guess my caveat is that I have not actually worked for government agencies directly. But I think for any job, finding ways to tell your story is super valuable. So where it can be hard is if you can't show your work, like you don't have clearance or permission or something. Maybe you try to find a way to recreate that. In a CodePen or find some way to represent the higher takeaways of what you've learned from that thing.
But having ways to tell that story... It'll vary, depending on what you need to show. But having a GitHub, a portfolio, some sort of... People have to see your work somehow.
So finding the best way to represent that... I think having some projects listed that you've worked on, and those give good talking points for them to ask you about. So like -- hey, tell me about this project you worked on! And maybe think ahead of time of what your biggest takeaways were, or things you've learned, so that you're already armed and ready to answer.
And you can even lead with some of that stuff. Given the opportunity. Hopefully that answers the question. STACY SMITH: I think so. I think that's great.
Let's see. We have another question. Is the IAAP certification appropriate for that question? In terms of... I'm guessing if that's a useful certification for people that are wanting to be able to display their accessibility capabilities, as part of the HR process?
MARCY SUTTON: Absolutely, yes. So the IAAP certification -- I would recommend it. I didn't personally go that route. I was already pretty far into my career. And so I just didn't feel a need personally. But I've heard really great things from friends and colleagues that have gone through that. And that the practice of studying for it and going through it -- you learn so much.
So the exercise of doing that, getting that certification, has a lot of value. And then having that certification at the end -- I think both of those things can really serve you in your career. So I would recommend it. STACY SMITH: Excellent. So we have a question from Cristina. What should we expect with the emerging technologies of AR, VR, MR, in terms of accessibility? Can we somehow get ready, familiarize ourselves?
MARCY SUTTON: Ooh, good question. So I guess... Well, the first thing that comes to mind for me is that there's always going to be emerging technology. And so that's a really great way to market yourself. Keep your finger on the pulse of what's coming. And if there's something in there that you're particularly interested in. For whatever reason. You have a passion for gaming or whatever your connection is. Find something that just has that extra level of interest for you. And try to find who's doing the research. Like... For me, early on, it was web components.
And there wasn't any information about accessibility in web components. So I just started testing it. And interviewing. I think I interviewed Marco Zehe, who worked at Mozilla.
I think he still might. I found whoever I could, who knew something about it, because they worked in the domain, and tried to create that information, if it doesn't already exist.
You can't be an expert in everything, so finding what is most interesting to you, and not shying away if there's not much information out there. You might have to create that information. And the best tip I got at some point when I was like... Why am I not getting any answers? My friend was like... That's the thing about being at the top of the food chain or being the first. It might not exist yet. Especially with existing technologies.
That's an opportunity to set yourself apart. I was really curious about this thing. I did all this research on it. How does the keyboard work with it? Whatever aspect of accessibility you want to dive into -- that was a really cool technique, to learn more and market yourself as a technologist.
So Twitter might be a good place to look. Find people who are talking about it, and interview them. Just start pulling at threads. You know. STACY SMITH: Very good. From Margie, we have: When figuring out how to remediate accessibility bugs, what are tips for convincing product leadership to include this work into product road maps? MARCY SUTTON: Good question. I mean... So I talked a little bit earlier about working through friction with carrots and sticks. So what people respond to... What actually succeeds is going to depend a lot on who you have to persuade.
Are people more sympathetic to it? Are they -- do they respond more to hard numbers? Sometimes talking to legal might help. Or taking a finance angle of lost income from people with disabilities as customers. So it's all about finding the best way to persuade whoever -- whatever stakeholders you need to convince. Like, what do they respond well to? What's worked in the past?
Because there's no one right silver bullet. To do it, unfortunately. But making it compelling, trying to provide estimates up front of how long you think things are gonna take, give people easy wins, quick wins, that you can celebrate, and be like... Hey, look, we really made some progress here. That might kind of give you some leverage to do bigger efforts.
Just make it really hard for people to say no. And I've found being less adversarial has worked for me. It's something about persuading people. I don't know if there's a gendered part of that. As a woman in tech, I have to kind of change how I -- my tone. And that's an unfortunate reality. At least, in my own experience. And it's all about trying to find those -- how to be persuasive. So it'll vary. But I think yeah...
The takeaways, I would say, are like: Give people quick wins and come with solutions and estimates. STACY SMITH: Great. So from Jacqueline Ong, she had a question. How would you go about suggesting accessibility recommendations to websites and apps for bigger firms? MARCY SUTTON: Can you repeat that one?
I think my energy just dipped. STACY SMITH: How would you go about suggesting accessibility recommendations to websites or app companies or bigger firms?
MARCY SUTTON: So that sounds big. I think I was just like... Whoa. That's a really big topic. That sounds like whole programs, potentially. If there isn't anything in place...
I mean... That's a pretty big topic to try and, like, get a whole program spun up in place. Yeah. I think it'll probably depend on which part of the market it is. What type of a product or service is it. Sort of back in the persuasion angle. Who are the customers? What kind of customers are you missing out on by not including accessibility? Yeah. I guess depending on how deep you want to go, how much time you have, maybe interview some people? Get some user feedback. If it's a big company, they probably have a feedback channel or even feedback customer service team.
Maybe interviewing them and seeing... Hey, do you ever get accessibility feedback? There might already be some feedback that you could use. As leverage to take to your -- the stakeholders and say: Hey, people are already having a problem with this.
So that's probably where I would start. Is go befriend the customer service folks. And see if they've heard anything. And yeah, I think my approach now is pulling at threads. I got a little clue over here. I'm gonna see if I can find out anything. Hopefully that's not a free time endeavor. Kind of goes back to my point about... If you're interviewing for a company, are you gonna be the only person that cares? Is there a team of people? Is this a volunteer effort that you're not getting compensated for? That could be kind of exhausting. When you're just trying to make the web a better place. So yeah. It's a big topic. Hopefully I answered that somehow. STACY SMITH: No, I think it's great.
I think we have time for one or two more questions. We had a question...
Saying that you've been a leader in highlighting accessibility wins. What is your favorite one or two accessibility wins? MARCY SUTTON: Ooh. Well, definitely the accessibility project. Yeah. I sort of just dusted this project off. I got pretty burned out the last couple years. And I think I launched this in, like, 2014. So it's been a while.
So the fact that it's still alive at all, I think, is a pretty good win. Some of the recent ones, just looking at the site... Adobe Spectrum CSS Library I think is really awesome. And I sort of -- I want more user interfaces to show. There's always more tools to talk about.
Things like accessibility insights. But what I'm really yearning for is more interfaces. And I was pleasantly surprised when I looked at Google Maps, their interface, I thought, was pretty cool. I did test it and saw it regress, and I think they fixed it again.
But seeing modern web applications that they have solved some hard problems...
STACY SMITH: We had a comment about -- in the Zoom chat, about Google Maps specifically. That they had limited accessibility toggles. Do you have any comment on that? Did you experience the same thing? MARCY SUTTON: Well, I would have to ask whether it was the app or the API. So when you embed a Google map, that's different. The thing I was writing about was when you go to maps.Google.com and it's the full web application in the browser.
That one had good accessibility built in. But I wrote about it... Gosh. It had to have been...
It was a year ago. So there's always that caveat. I already saw it regress once. And it got worse. And maybe it got better. So sometimes when I... That's the hard part about wins, even. Is like -- it might be awesome at that moment in time. And then it can regress.
But when I did review it, it had great keyboard accessibility. And yeah. It was actually usable.
But yeah. I would have to... See more about the limited accessibility toggles. Yeah. I'm not sure.
Hopefully accessibility is just built in for everyone. And it's not something you have to toggle on and off. That's really what we want to aim for. Is like a streamlined, inclusive design that just works. STACY SMITH: Excellent. Any more questions? Before we wrap up with Marcy tonight? Last call. Here and also on YouTube. Let us know. If not... MARCY SUTTON: I see one comment from John Croston, that says what about making things accessible as you go and asking for forgiveness later? Yes, I am a big proponent of that. I sort of would do that. I would be working on a Target thing and then switch over to Nintendo. Accessibility wasn't part of the requirement, but I'm like... I'm not gonna, like, not make it as accessible as I can! As I'm working on it! And you just do it. So... Yeah.
I'm a big fan of that. But you also need to get compensated for your time. So staying late to do it is not ideal. Even though I did it anyway.