What is accessibility?

Understanding accessibility across government, nonprofit, and public-interest work


Conceptual illustration for accessibility in government and public services, showing an open pathway leading toward a city skyline and representing access, participation, and inclusive systems.

Accessibility helps create pathways into participation, services, and public life.

Accessibility is the practice of ensuring people can meaningfully access, understand, navigate, and participate in environments, services, programs, products, communications, and systems—regardless of ability, circumstance, technology, or context.

Accessibility shapes how governments, nonprofits, schools, healthcare systems, and public-interest organizations serve people. If someone cannot access a service, understand important information, participate in a process, or navigate a system, then the experience may not fully serve the public.

Accessibility is often discussed through the lens of disability—and for good reason. Many of the rights, standards, practices, and expectations that shape accessibility today were advanced through decades of advocacy, organizing, and leadership from disabled people and disability communities who challenged institutions to remove barriers and expand participation.

Accessibility work in government and public life did not emerge overnight. It reflects decades of advocacy, policy work, disability leadership, design practice, and lived experience that pushed institutions to become more inclusive and usable.

While accessibility remains deeply connected to disability justice and inclusion, its impact reaches far beyond any single environment or interaction. Accessibility shapes how people navigate services, understand information, participate in civic life, and move through the world.

Accessibility shows up across everyday experiences in many ways. Some examples include:

  • A resident trying to understand a public benefits application

  • A parent navigating a school enrollment process

  • A community member attending a public meeting

  • A patient interpreting healthcare instructions

  • A person using assistive technology to access a digital service

  • Someone reading information in a second language

  • A visitor attempting to navigate a physical space

Accessibility influences whether people can participate, not just whether something technically exists.

And because participation happens across environments, services, and systems—not just websites—accessibility extends beyond products.


Accessibility extends beyond products

Accessibility is frequently framed as a digital concern. Websites, forms, and applications matter. But public experiences rarely begin and end with screens.

Accessibility can influence many interconnected parts of an experience. Some examples include:

Environments

  • Buildings and public spaces

  • Transportation systems

  • Signage and wayfinding

  • Public meetings and events

Services

  • Application processes

  • Call centers

  • Service delivery workflows

  • Appointment systems

Programs

  • Eligibility requirements

  • Outreach and communications

  • Participation structures

  • Feedback loops

Products, content, and media

  • Websites

  • Forms

  • Videos

  • Documents

  • Social media

  • Publications

  • Presentations

Accessibility is not confined to one team or discipline. It often spans policy, technology, operations, communications, design, and service delivery at the same time.

That overlap is part of what makes accessibility work complex—and why it benefits from shared ownership.

Related reading: What is public-centered design? and More than digital


Accessibility works best when integrated from the start

Teams sometimes approach accessibility as a review step near launch:
"Let's check accessibility before we release it."

By then, important decisions have often already been made.

Language structures are set. Technologies have been selected. Processes have been built. Budgets have already been spent.

Retrofitting accessibility after implementation is often more difficult, more expensive, and less effective than integrating it early.

Integrating accessibility from the start may include:

  • considering accessibility during procurement decisions

  • including accessibility requirements in planning

  • selecting technologies that support assistive tools

  • designing content intentionally

  • involving people with lived experience early

  • integrating accessibility into workflows and governance

At Public Servants, we believe accessibility is strongest when integrated into systems and experiences from the beginning.

Accessibility is often strongest when considered alongside broader service design and systems decisions, not treated as a final checklist.

Related reading: When service design breaks down and What is the policy implementation gap?


Compliance is a baseline, not the goal

In the United States, accessibility work may intersect with standards and frameworks such as ADA requirements and Section 508 guidance. These establish important baselines, though accessibility often extends beyond technical requirements alone.

Requirements matter. Standards matter. But accessibility is broader than passing a review or meeting minimum requirements.

Compliance can answer questions like:

  • Does this meet technical standards?

  • Is this legally compliant?

  • Are required accommodations present?

Accessibility asks broader questions like:

  • Can people actually use this?

  • Can they understand it?

  • Can they complete what they came to do?

  • Can they participate with dignity?

An organization can technically meet standards while still creating confusing or exclusionary experiences.

For example, a city website may technically meet accessibility requirements while still requiring residents to navigate five confusing steps to pay a utility bill. Accessibility and ease of use often work together.

Accessibility is not only about reducing risk. It’s also about reducing barriers.


Accessibility requires testing, learning, and iteration

Even thoughtful teams can make assumptions. What feels clear internally may create friction externally. This is one reason usability testing matters.

Testing can reveal things like:

  • confusing language

  • unclear navigation

  • inaccessible interactions

  • technology limitations

  • hidden barriers in workflows

  • assumptions embedded in decision-making

Accessibility testing should not happen only at launch. Like public services themselves, accessibility benefits from ongoing learning and iteration.

Related reading: What is the policy implementation gap? and More than digital


Accessibility takes many forms

Accessibility often becomes visible through many small decisions. Language, technology, and format decisions each matter.

Language

  • using plain language

  • reducing jargon and acronyms

  • supporting multiple languages where appropriate

  • structuring content clearly

Images

  • descriptive alt text

  • avoiding graphics dependent on color alone

  • ensuring information is not trapped inside images

Video and audio

  • captions

  • transcripts

  • audio descriptions when appropriate

Technology

  • screen reader compatibility

  • keyboard navigation

  • mobile responsiveness

  • assistive technology support

Documents and presentations

  • accessible heading structures

  • meaningful link text

  • readable typography and contrast

  • accessible PDFs and slide content

Collectively, these decisions—and many others—shape whether people can fully participate.

 

"We considered the people we serve."


Accessibility is part of public trust

When systems repeatedly create barriers, people often experience more than inconvenience. They experience frustration, exclusion, confusion, and erosion of trust.

Accessibility communicates that people were considered throughout the design and delivery process.

"We considered the people we serve."

Because public systems serve communities with different abilities, circumstances, and needs, accessibility is not a niche concern. It is foundational to meaningful participation.

 

Related concepts

Accessibility often connects with adjacent concepts that shape how people experience public systems:


Frequently asked questions

  • Is accessibility only about disability?
    No. Accessibility is deeply connected to disability access and disability inclusion, but it can also involve language, literacy, technology access, context, and other barriers that affect participation.

  • What is the difference between accessibility and usability?
    Accessibility focuses on reducing barriers so people can participate. Usability focuses on making experiences understandable and effective. Strong public experiences often benefit from both.

  • Is accessibility only for digital products?
    No. Accessibility applies to services, environments, meetings, communications, programs, public spaces, and systems—not just websites or applications.

Public Servants Team

Public Servants LLC™ is a team of civic designers, strategists, and public service professionals strengthening how governments, nonprofits, and mission-driven organizations design, communicate, and deliver public systems.

Previous
Previous

Public understanding

Next
Next

Organizational drift