Ringside Access No Matter the Platform | A Conversation with Jon Fukuda

Today’s blog post explores how organizations can stop treating accessibility as a last-minute compliance task and start building it into the way people create, review, and publish digital content. The ideas grew out of a conversation with Jon Fukuda, one of my co-founders at Limina11y.

We talked about what organizations often miss when they approach accessibility as a technical cleanup project instead of an ongoing part of design and operations. Accessibility works better when people understand the fundamentals, use tools that support accessibility, and know what role they play in the process.

Video Guide

Start With Accessibility Fundamentals

One of the biggest mistakes organizations make is starting with advanced accessibility work before staff understand the basics. Someone may eventually need to learn accessible PDF forms, document tagging, captioning, or remediation software, but those skills are much easier to apply when the person understands the principles behind them.

Those fundamentals include:

Using headings to create meaningful structure
Writing useful alternative text for images
Making content usable with a keyboard
Creating tables with clear headers and simple structures
Checking color contrast
Organizing lists correctly
Creating a logical reading order

These concepts apply across platforms. Someone may work in Microsoft Word, PowerPoint, Google Docs, Canva, Excel, Adobe Acrobat, or another content creation tool, but the basic accessibility questions stay the same.

Build an Accessibility Operating Model

Accessibility requires more than knowing a set of technical requirements. Organizations also need a process for putting that knowledge into practice.

One way to think about accessibility is as several lanes that need to move together:

Knowledge: Do people understand accessibility fundamentals?
Tools: Can the software they use create and preserve accessible content?
Implementation: Do people know when and how to apply accessibility during their work?

Training someone on accessibility will only go so far if the software that person uses cannot produce the required structure. The same problem happens when an organization purchases accessibility software without teaching employees how to evaluate what the tool produces.

A stronger operating model connects accessibility with content creation, review, remediation, testing, and outside support when needed. It also establishes who is responsible for accessibility at each stage before content reaches publication.

Inventory What You Have

If your organization does not know where to begin, start by creating an inventory of your digital content. Include websites, PDFs, spreadsheets, videos, presentations, forms, apps, and other public-facing resources.

The inventory gives you a clearer picture of the work ahead and helps answer practical questions:

What needs immediate attention?
What can be archived?
What can staff handle internally?
What requires outside support?
What accessibility problems keep appearing?
Where does staff need more training?

The patterns you find can help determine where to focus next.

For example:

A large number of PDF forms may point to a need for forms accessibility training.
Hundreds of videos may require stronger captioning and audio description practices.
Recurring spreadsheet problems may show a need for Excel accessibility training.
Repeated design problems may indicate a need for training on contrast, visual structure, or accessible templates.

Start with broad accessibility fundamentals, then provide specialized training based on the types of content your organization actually creates.

Fix More at the Source

One of the best ways to reduce remediation work is to build accessibility into the source content before it reaches the final publication stage.

That means:

Using real headings instead of relying only on larger or bold text
Creating simple tables with clear headers
Writing useful alternative text
Checking color contrast during design
Setting up lists properly
Thinking about reading order before export

When content creators address accessibility early, they give the next person in the workflow a much better starting point. Otherwise, someone may have to reconstruct headings, repair tables, correct tags, rewrite alternative text, or rebuild the reading order after the content has already been exported.

That work takes real time. A 45-page report that arrives as a flattened scanned document can require roughly 10 to 15 hours of remediation, even for someone with substantial document accessibility experience.

Organizations need to account for that workload when planning projects. They may use staff time, outside remediation support, or a combination of both, but better source files can reduce the amount of work required later.

Share Responsibility Across the Organization

Accessibility becomes difficult to scale when an organization places most of the responsibility on a small number of specialists. If every inaccessible document, presentation, video, and form eventually lands on the same desks, those specialists become cleanup crews for problems that other people could have prevented earlier.

A better approach gives people responsibility for the accessibility decisions connected to their own work:

Content creators understand the accessibility requirements for the materials they produce.
Designers consider color contrast, structure, and accessible visual communication.
Video producers plan for captions, transcripts, and audio description when needed.
Managers know what accessibility requirements to review before approving publication.
Accessibility specialists handle complex issues, provide guidance, and help improve organizational practices.

Organizations do not need every employee to become an accessibility expert. They do need enough accessibility knowledge across the organization that good practices become part of everyday work.

This also protects the people with the deepest accessibility expertise from spending all of their time fixing basic issues that could have been addressed earlier.

Accessibility Still Needs Human Judgment

Automated tools can catch many accessibility issues and make review faster, but they cannot determine whether the experience actually works for the user.

Human review still matters for things such as:

Whether alternative text communicates the important information
Whether headings create a meaningful hierarchy
Whether PDF tags accurately represent the content
Whether reading order makes sense
Whether navigation works logically with assistive technology
Whether the content makes sense in context

A checker may confirm that alt text, headings, or PDF tags are present. A person still needs to determine whether those elements are accurate and useful.

Automation can support accessibility work, but people need to review the results and make the decisions that depend on meaning, context, and how someone will actually use the content.

Accessibility Makes Digital Content Easier to Use

Accessibility often improves usability for a wider audience, including people who may never describe themselves as having a disability.

For example:

Clear headings help screen reader users navigate while making documents easier for everyone to scan.
Captions provide access to people who cannot hear the audio and also help people watching videos in noisy environments.
Strong color contrast supports people with low vision and makes information easier to read under different viewing conditions.
Clear instructions help people using assistive technology and reduce confusion for other users.
Logical navigation creates a more predictable experience for people using keyboards, screen readers, or other input methods.

Accessibility also becomes more important as people’s needs change over time. Vision, hearing, cognition, mobility, and dexterity can all affect the way someone interacts with technology at different points in life.

Many people have already helped a parent, colleague, friend, or family member navigate an app, locate a control, read small text, or complete a confusing online process. Accessible design asks whether the product itself could have made that interaction easier.

Accessibility works best when it becomes part of how an organization creates digital content from the beginning. Build the knowledge, establish a workable process, give people responsibility for their part of the work, and accessibility becomes part of producing better digital experiences rather than a problem to repair at the end.

About Jon Fukuda

Jon Fukuda is a user experience specialist and co-founder of Limina and, more recently, Limina11y. Since 2003, he has helped organizations build scalable, resilient Research and Design operations that connect information, technology, and human-centered design.

His expertise includes UX research and strategy, design thinking, UI design, and design operations. Jon leads human-centered design efforts from requirements through solution validation, with a focus on making Research and Design practices continuous, scalable, and sustainable across the enterprise.

About The Accessibility Guy 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.