Finding Your Accessibility Champion | A Conversation with Sherri Smith
Today’s blog post explores how an accessibility champion can help your team build accessibility in from the start. A champion helps coworkers learn everyday accessibility skills and recognizes when specialist support is needed. They are not responsible for fixing everything alone.
From teaching the next useful skill to making room for human review, the champion’s role is to give people a workable way to improve what they create. That includes advocating for tools, staff time, and future revisions, so the future documents do not bring back the same barriers.
The ideas in this post grew out of a conversation with Sherri Smith, Architect of Participation and Accessibility Champion.
Video Guide
Support Your Accessibility Champion
Your accessibility champion may be the coworker people turn to when they’re unsure what to do next. That person can help others recognize barriers and find a way forward. They might:
- explain heading styles to a coworker
- identify a recurring problem in a template, or
- connect a team with a PDF remediation specialist.
Being that helpful person doesn’t mean knowing everything about every format, website, form, and procurement requirement. A designer can bring accessibility into design without taking on every complex PDF repair. A teacher can improve classroom materials without becoming a full-time remediation specialist.
If your team relies on an accessibility champion, make room for that work. They need time to learn and someone to turn to when a problem calls for specialist help. Be clear about who can approve resources, too. Enthusiasm matters, but it won’t create extra hours in an already full working day.
Coworkers still play a part in improving the content they create. With support, the champion can help them learn instead of spending all their time working through everyone else’s unfinished files.

The rest of this post looks at what that everyday work can involve: teaching a useful skill, keeping people in the review process, making time for accessibility, and planning for the next version of a document.
Teach the Next Useful Skill
Someone who asks how to improve a document may not be ready for a lesson in every accessibility term. Start with the file they’re working on. Show them a change they can make, then explain how it helps the person using it.
In Word, you might apply a heading style together and show how a reader can move between sections. If your coworker is preparing a presentation, look at color contrast. If they’re writing an email, try replacing a vague link label like ‘Click here’ with wording that tells readers where it goes.
Keep the first lesson focused:
- Show one change in a familiar file.
- Explain the barrier that the change addresses.
- Let the person practice it in their own work.
- Give them a reliable place to get help.
Keep Human Review in the Process
It’s encouraging to run a check and see fewer problems. Just leave room for a closer look before calling the document ready. Microsoft’s accessibility checker has documented limitations, and PDF review includes checks that need human judgment.
Treat AI suggestions as something to review, too. A confident answer still needs checking. If a tool moves text into another format, compare it with the original: Did the words and punctuation stay intact? Missing spaces or an unexpected edit can be easy to overlook.
Then check how the document works for the person using it.
- Does the reading order make sense?
- Can someone navigate its sections?
- Do links and form controls behave as intended?
Include Staff Time in the Cost Conversation
When you ask for a tool or training budget, bring the day-to-day work into the conversation. Software price is only part of the picture. Someone also needs time to learn the process, repair files, check the results, and revisit them when content changes.
Include that time when comparing in-house work with specialist support. Your team may be comfortable handling routine content and need help with complex documents. Or the best place to invest may be the source files and the people who create them. Either way, leave time for quality checks.
You don’t have to promise that a purchase will solve everything. Show where your team is spending time now. A repair that keeps coming back, or a file nobody knows how to fix, gives decision-makers a concrete problem to consider.
Plan for the Next Version
That brochure may be headed to the printer today, but will someone put it on the website next month? Will the annual report need new figures or a replacement page? Asking those questions early helps you choose how to build the document for the ways people will actually use it.
Keep an editable source file and build accessibility into that source wherever possible. Agree on content before final PDF remediation and include accessibility review when revisions occur. Do not assume that an updated export preserves every repair made to an earlier PDF.
If the same repairs come back every year, take a look at where the document starts and how it moves between people. A better source file or a clearer handoff can give the next person something useful to build on, rather than the same problem to work around again.
Start With One Everyday Document
Start with a document your team creates regularly. Work with its author and your accessibility champion to fix a recurring barrier in the source file, then check the result before sharing it. Keep what you learn in a template or brief process note so others can build on it. With time and support for that shared learning, accessibility becomes part of everyday work.
About Sherri Smith
Sherri Smith is an Architect of Participation, using communications, design, digital accessibility, and responsible AI to remove barriers, expand participation, and keep humanity at the center of innovation.
In her current role as Design and Communications Coordinator with Center for Schools and Communities, Sherri brings that philosophy into practice through strategic communications, visual design, digital accessibility and emerging technology. Her work focuses not simply on whether people are invited to participate, but whether the systems, information and experiences around them actually make participation possible.
A designer by background and a systems thinker by nature, Sherri is especially interested in the spaces where communication, accessibility, technology, and human experience intersect.
About The Accessibility Podcast
The Accessibility Guy Podcast explores real projects, practical challenges, and the ways accessibility laws, standards, technology, procurement, AI, education, and lived experience shape accessibility work.
The podcast features voices from across the field, including accessibility professionals, developers, designers, educators, government leaders, assistive technology experts, and people with lived experience.
Interested in joining the conversation? Register your interest to be a guest on The Accessibility Guy Podcast.
Responses