As some newsroom roles go the way of the dinosaurs, other new jobs are being born. This is the first in an occasional series of Q&As with people who are the first to hold their title in their newsroom.
Holden Foreman is the first-ever accessibility engineer at The Washington Post. Like many “first-ever” roles, the new job is a deeply multidisciplinary one.
I start a new job today as @washingtonpost’s first-ever Accessibility Engineer! I have long cared about making our content more accessible, and I love that I now get to focus on this. We always want user feedback. My DMs are open, and you can email us: accessibility@washpost.com.
— Holden Saige Foreman (@hsforeman) January 18, 2023
Foreman makes the case that accessibility in journalism is important for everyone: Making news products more accessible, after all, often means making them more user-friendly and efficient. He hopes to discover and standardize ways of making the Post’s journalism accessible to as many people as possible.
Foreman and I went back and forth about his new role over email. Our conversation, lightly edited, is below.
At many smaller news organizations, there may not be the option to hire an accessibility engineer, or any software engineers at all. That doesn’t mean those organizations don’t care about accessibility. Having this new title at the Post isn’t the difference between caring about accessibility or not. It’s about refining our existing efforts. It’s about having the time to innovate in this space and help make the Post a leader and model for newsrooms with less resources.
Some of the bigger tech companies have had accessibility engineers for years, which helped motivate us to create this role at the Post.
But it’s important to realize that accessibility in media is about so much more than alt text or any other single issue. There are many different types of disabilities, including temporary and situational disabilities — like a broken arm, bad internet, or loud surroundings — that change how people interact with journalism. Some people are unable to use a computer mouse due to a motor disability, for instance. These folks may rely on a keyboard to navigate content, but many websites and apps are built with the assumption that everyone can hover a mouse over a map, or click and drag on the screen. Assumptions like these hinder accessibility.
Having an engineer dedicated to accessibility at the Post will help us eliminate assumptions and focus on maintaining up-to-date standards. It will also give us the time to explore new opportunities in research and feature development. The accessibility engineer will help educate others at the company on the latest accessibility practices and will be a resource for support.
I’ve had hopes for an accessibility role at the Post since 2021, when I started an informal working group at the company with biweekly meetings for skill shares, news, internal updates, shoutouts and other discussions related to accessibility. With the help of Julie Bacon Arsenault, one of the Post’s engineering directors, I delivered a pitch last year for an accessibility engineer job title. Julie is a champion of this work, and I’m so grateful for that. I’m also grateful that Arturo Silva, an engineering manager who oversees the Washington Post Design System among other things, was willing to make a home for the role on his team.
Accessibility is a relatively small area of focus in journalism right now. There aren’t yet a lot of roles like the one I’m starting now. At its core, I think journalism is about wanting valuable information accessible to as many people as possible, and I believe I have potential to create real change if I invest fully into it. Thankfully, the Post agreed and created this new title.
Another big hope with this role is that we create a stronger dialogue with our users, real people with different backgrounds and including folks with disabilities, as we do our work. There are different types of manual and automated tests that we can use to gauge the accessibility of a website or app, but these only scratch the surface. It’s essential to learn how different people are actually using our tools and identify the opportunities for improvement with their input.
It’s definitely stressful to be the first in this new role. I feel deep down like I need to justify its creation with every step that I take. My managers and colleagues have been fully supportive, and it is thanks to them that the role exists, so I would say that the pressure feels self-enforced. Thankfully, there is a lot of collaboration in the accessibility world, and I have already been in contact with some folks from outside of The Post regarding how we can support each other.
There are many types of diversity that we’ll consider in our outreach. For journalists, it is essential to source with diversity in race, gender, sexuality, and more. It is also essential in accessibility work. People with the exact same disability can have different resources, needs, and preferences. And issues like low internet bandwidth can correlate with other user demographics like geographic location. There are nuances specific to the accessibility space. Not everyone with a disability has access to the same technology. Screen reader availability varies by operating system. JAWS, one of the popular screen readers, is not free to use. And there are many different types of disability. We cannot focus our work only on disabilities related to vision or hearing. We need separate initiatives to address separate accessibility issues.
I’m always looking to learn from others, especially those directly impacted by accessibility issues. Some have already reached out to ask questions and share resources, and that is always appreciated. I also realize that not everyone will be as forthcoming. It will take trust, commitment and regular engagement to ensure we are not only considering the most well-supported and outgoing voices in this space.