Workplace

Why Slack’s new accessibility manager says the work is never done

Sommer Panage, Slack’s senior accessibility manager, talks about her goals since joining the company in April and how she hopes to build a more accessible product.

A headshot of ​Sommer Panage.

“'How could someone else experience this?' is the number one question we ask."

Photo: Slack

Before Sommer Panage joined Slack, there was no centralized team working on accessibility.

Panage said there were some people who focused on desktop accessibility and others who worked on Slack for mobile, but they were scattered across the company. Panage joined Slack a few months ago as senior engineering manager and helped bring the company’s accessibility efforts under one roof. Before joining, she worked on accessibility efforts on iOS at Apple and held roles at Twitter before that.

Slack recently announced updates to improve keyboard navigation and introduced a new interface for screen readers as well as what the company called “an ongoing effort to bridge gaps.” Panage said bringing together one unified accessibility team has helped Slack focus on these different areas of improvement and work with teams across the company to build new features with accessibility in mind. But she stressed that the work is ongoing.

“Accessibility is never done,” she told Protocol. “A common challenge for companies is to say, ‘Oh, we made our product accessible. And now it's done.’ But it's not the case.”

This interview has been edited for clarity and brevity.

How is Slack’s approach to the topic different from others?

In large companies, in the Apples or the Microsofts and the big companies of the world, there's definitely an accessibility team. But I think it’s much less common in the small companies, and often there will be people who care deeply about it, and they might be scattered. They might start a networked effort across the company. I've seen that in various places as well, but it's not necessarily the standard for companies to have an accessibility team, a centralized hub of accessibility. That's one thing that Slack recognized pretty early as it started to grow … It's not super common, but it is super beneficial.

Can you point me to a time, either at Slack or a previous position, when you had an idea that didn’t work out in the way you expected? And on the flip side, what was a change you made that had an immediate impact?

Accessibility is a field that, especially when I started in it over 10 years ago, there was not a lot of information. There were standards online that I could read about there, but there was not much else. So I made a lot of mistakes early in my career. A common one I think folks will make as developers is to overlabel things or be overly verbose when you're thinking about screen-reader experience. So that was a mistake I made in many ways multiple times … We started getting this feedback from our screen-reader users saying, “Oh, hey, this is way too verbose. This is not helpful to me.” That was where I learned two lessons. One, verbosity is incredibly important for screen-reader users. Two, listening to our users is vital to making good decisions about the product, and certainly that's something that Slack was already doing before I arrived.

"[L]istening to our users is vital to making good decisions about the product."

As far as things that have gone really well, sometimes a very small idea can be a really big thing. One of the changes that we recently made in our updates at Slack was to add a couple preferences that allow users more fine-grained control over how their messages are read out. And it sounds so simple, right? It's like, “Oh, you read the date first or the date last.” It's the little preference, but this can be so important for someone using a screen reader because listening takes time. If the information I want is up front, you've just made me so much more efficient.

How did you decide to focus on these areas of improvement?

At Slack, we focus heavily on what our users tell us and the experiences that they're having. So this work stems from a large amount of time and feedback and process with both external user feedback that comes in through our various feedback systems as well as user groups who are full-time assistive technology users. By combining feedback from these two spots, we've found key pain points within the Slack product that we knew we wanted to really focus on.

And those were really focused around the notion of keyboard navigation and keyboard focus. We had a lot of feedback from our screen-reader users. And so we wanted to make sure we put a lot of work there to make sure the desktop product was fantastic for them.

Since joining Slack, what have been your top goals in terms of accessibility?

One of the things I've really wanted to focus on is thinking about how Slack can really take a stance in accessibility and build the product to be something that says, “This is how Slack should work from an accessibility standpoint. And this is how we believe — with the feedback of our users and with what we've learned in our research — this is what we want to create.”

The other thing is thinking about each platform individually. Just because there's a cohesive picture for accessibility doesn't mean it's going to behave exactly the same on each platform. It might need to be different. Android is different from iOS, which is different from web, etc. And so a second-tier focus there is then thinking about, “OK, so now we've agreed on how we want to approach it. What does that look like on Android? What does that look like on a web product?”

And then certainly as well, looking for any broken windows, any things where we're like, “Hey, this needs to be better.” So one thing that you may have noticed if you happen to use our Android product is significant improvements in our larger text size support.

What do you mean by your goal that you want to “take a stance” on accessibility?

We're thinking about Slack really as the digital headquarters right now. This is a place you go to get work done. Part of that stance is making sure that Slack is a place for everyone to come and to get their work done. And it's really about Slack being this digital headquarters that is equitable, that is delightful to us and that is efficient for all of our users.

And the other part of taking a stance on accessibility is about how we do accessibility. Not just that our product will be equitable, but also how do we actually approach making that happen? And the approach part of it is really strongly based, for us, in user-centered design and user-centered engineering. From both perspectives — from the design perspective and from the perspective of which we build the products — we want to be sure that we're drawing from our users and understanding what they're experiencing and what they experience in other products and on different platforms.

What does the process look like for introducing an accessibility improvement at Slack to implementing it?

We'll prototype an idea and we'll get something working, something functional, say, for example, a screen-reader feature. And so we'll get something prototyped and ready to share with our internal user groups who are full-time assistive technology users. And by doing that we can get that early information as to whether or not this idea was good or not … and there has to be a really big willingness to be wrong, because sometimes we don't get it right.

From there, we'll have a prototype, we’ll iterate with our internal user group and start to hone in on what the product is going to be. And then that will develop into a feature brief and something that becomes part of our road map for the accessibility team. From there, it's going to go through a pretty standard process of planning and execution all the way through. But through that planning and execution, we'll continue to iterate with our user group, so it won't just go into a box and come out the other side, but rather at various milestones, we will go back with them and say, “Hey, can you try this out? Give us feedback, take a pass at it.”

Would you say someone with an accessibility background should be in the room during every conversation about different Slack changes?

To some degree, yes. Obviously having accessibility in the room, in every meeting — we can't scale that. But when a feature is in the early phase — a great example would be something like the Huddles feature, where having someone say, “Hey, these are going to need captions" really early on — that's a really fantastic example of what happens when someone with an accessibility mindset is in that room really early.

What was your perspective as a user before joining Slack versus your experience since joining?

One of the things that drew me to Slack was noticing the progress they were making on accessibility. I'm always tinkering. I will make the text size way big, I will invert the colors on my phone, I will do all kinds of things just to see what happens, to learn about the product. And I was consistently noticing that Slack was making improvements. My friends who have visual impairments and my friends who are hard of hearing had made comments about some things they noticed and been impressed with the product. And so early on, I knew that Slack was a company that was really putting some great effort into accessibility, and that drew me there.

"[T]here has to be a really big willingness to be wrong, because sometimes we don't get it right.

Since coming in and joining, that perspective hasn't really changed. Now I just know the people who are doing this work. But since joining Slack, I noticed that the work was coming from a lot of different places. And so that was kind of what pulled me in. I thought, “Oh, it'd be so great if this were an accessibility team all under one roof working together,” because I think you can be more efficient that way. You can reach out through the company more successfully when you're coming from a centralized place. And it also helps people know who to go to when they have a question. So that was the shift I wanted to help Slack achieve by joining.

How has your background in psychology helped you in your role?

It's one of those degrees I did not anticipate I would utilize, and I found it very helpful in my career in technology and then specifically in accessibility. In studying psychology and doing a bit of psychology research through my undergrad, one of the things that I had to learn was a lot about thinking about how people think. And that particular skill … all of that became very, very useful then when I came to work in accessibility. “How could someone else experience this?” is the number one question we ask.

One of your goals at Slack is to identify “broken windows.” Are there any that you want to focus on in the coming year or so?

One that I'm very excited about is just seeing us improve our Android product and how it has its text sizes. I think that one of the challenges that the recent changes are trying to solve is around the fact that Slack is a web product on desktop. And so I think that because of that, I wouldn't necessarily say there's a lot of broken windows around it, but it creates challenges because it's a web product as a desktop app.

For a company that's scaling, how can you keep accessibility in mind?

It's a really big challenge. No question there. As a company grows, one thing that is important to establish pretty early on is what the accessibility process looks like … It's really important for something like accessibility in the same way we would process for security, right?

As a company is growing and adding teams, it's important to have a way that says, “This is how Slack does accessibility.” So as a new team spins up, that process is already there for them. They just need to look into it. They don't have to reinvent the wheel as to what these things mean. The process and the “how” is already there. In Slack’s case, that means the design reviews and the accessibility review toward the end, and the office hours.

Entertainment

Inside Amazon’s free video strategy

Amazon has been doubling down on original content for Freevee, its ad-supported video service, which has seen a lot of growth thanks to a deep integration with other Amazon properties.

Freevee’s investment into original programming like 'Bosch: Legacy' has increased by 70%.

Photo: Tyler Golden/Amazon Freevee

Amazon’s streaming efforts have long been all about Prime Video. So the company caught pundits by surprise when, in early 2019, it launched a stand-alone ad-supported streaming service called IMDb Freedive, with Techcrunch calling the move “a bit odd.”

Nearly four years and two rebrandings later, Amazon’s ad-supported video efforts appear to be flourishing. Viewership of the service grew by 138% from 2020 to 2021, according to Amazon. The company declined to share any updated performance data on the service, which is now called Freevee, but a spokesperson told Protocol the performance of originals in particular “exceeded expectations,” leading Amazon to increase investments into original content by 70% year-over-year.

Keep Reading Show less
Janko Roettgers

Janko Roettgers (@jank0) is a senior reporter at Protocol, reporting on the shifting power dynamics between tech, media, and entertainment, including the impact of new technologies. Previously, Janko was Variety's first-ever technology writer in San Francisco, where he covered big tech and emerging technologies. He has reported for Gigaom, Frankfurter Rundschau, Berliner Zeitung, and ORF, among others. He has written three books on consumer cord-cutting and online music and co-edited an anthology on internet subcultures. He lives with his family in Oakland.

Sponsored Content

Great products are built on strong patents

Experts say robust intellectual property protection is essential to ensure the long-term R&D required to innovate and maintain America's technology leadership.

Every great tech product that you rely on each day, from the smartphone in your pocket to your music streaming service and navigational system in the car, shares one important thing: part of its innovative design is protected by intellectual property (IP) laws.

From 5G to artificial intelligence, IP protection offers a powerful incentive for researchers to create ground-breaking products, and governmental leaders say its protection is an essential part of maintaining US technology leadership. To quote Secretary of Commerce Gina Raimondo: "intellectual property protection is vital for American innovation and entrepreneurship.”

Keep Reading Show less
James Daly
James Daly has a deep knowledge of creating brand voice identity, including understanding various audiences and targeting messaging accordingly. He enjoys commissioning, editing, writing, and business development, particularly in launching new ventures and building passionate audiences. Daly has led teams large and small to multiple awards and quantifiable success through a strategy built on teamwork, passion, fact-checking, intelligence, analytics, and audience growth while meeting budget goals and production deadlines in fast-paced environments. Daly is the Editorial Director of 2030 Media and a contributor at Wired.
Fintech

Wall Street is warming up to crypto

Secure, well-regulated technology infrastructure could draw more large banks to crypto.

Technology infrastructure for crypto has begun to mature.

Illustration: Christopher T. Fong/Protocol

Despite a downturn in crypto markets, more large institutional investors are seeking to invest in crypto.

One factor holding them back is a lack of infrastructure for large institutions compared to what exists in the traditional, regulated capital markets.

Keep Reading Show less
Tomio Geron

Tomio Geron ( @tomiogeron) is a San Francisco-based reporter covering fintech. He was previously a reporter and editor at The Wall Street Journal, covering venture capital and startups. Before that, he worked as a staff writer at Forbes, covering social media and venture capital, and also edited the Midas List of top tech investors. He has also worked at newspapers covering crime, courts, health and other topics. He can be reached at tgeron@protocol.com or tgeron@protonmail.com.

Policy

How I decided to go all-in on a federal contract — before assignment

Amanda Renteria knew Code for America could help facilitate access to expanded child tax credits. She also knew there was no guarantee her proof of concept would convince others — but tried anyway.

Code for America CEO Amanda Renteria explained how it's helped people claim the Child Tax Credit.

Photo: Code for America

Click banner image for more How I decided series

After the American Rescue Plan Act passed in March 2021, the U.S. government expanded child tax credits to provide relief for American families during the pandemic. The legislation allowed some families to nearly double their tax benefits per child, which was especially critical for low-income families, who disproportionately bore the financial brunt of the pandemic.

Keep Reading Show less
Hirsh Chitkara

Hirsh Chitkara ( @HirshChitkara) is a reporter at Protocol focused on the intersection of politics, technology and society. Before joining Protocol, he helped write a daily newsletter at Insider that covered all things Big Tech. He's based in New York and can be reached at hchitkara@protocol.com.

Climate

This carbon capture startup wants to clean up the worst polluters

The founder and CEO of point-source carbon capture company Carbon Clean discusses what the startup has learned, the future of carbon capture technology, as well as the role of companies like his in battling the climate crisis.

Carbon Clean CEO Aniruddha Sharma told Protocol that fossil fuels are necessary, at least in the near term, to lift the living standards of those who don’t have access to cars and electricity.

Photo: Carbon Clean

Carbon capture and storage has taken on increasing importance as companies with stubborn emissions look for new ways to meet their net zero goals. For hard-to-abate industries like cement and steel production, it’s one of the few options that exist to help them get there.

Yet it’s proven incredibly challenging to scale the technology, which captures carbon pollution at the source. U.K.-based company Carbon Clean is leading the charge to bring down costs. This year, it raised a $150 million series C round, which the startup said is the largest-ever funding round for a point-source carbon capture company.

Keep Reading Show less
Michelle Ma

Michelle Ma (@himichellema) is a reporter at Protocol covering climate. Previously, she was a news editor of live journalism and special coverage for The Wall Street Journal. Prior to that, she worked as a staff writer at Wirecutter. She can be reached at mma@protocol.com.

Latest Stories
Bulletins