Accessibility belongs in the purchasing conversation

A public service can involve several suppliers

The Department of Justice published its ADA Title II web and mobile accessibility final rule (opens in a new tab) in April 2024. The rule addressed state and local government services made available:

“directly or through contractual, licensing, or other arrangements”

— U.S. Department of Justice, April 2024

Its scope is public entities and their covered services, not every private website. Implementation dates and later developments require separate current review. A public organization still needs to understand the responsibilities attached to a service it buys, including the work required to keep that service usable.

Begin with a task, not a demonstration

Picture a hypothetical community program choosing an online registration service. The demonstration is polished. A participant who uses a keyboard then tries to select an activity, review the details, and confirm a place.

That journey is a more useful starting point than a general question about whether the product is accessible. It connects the purchasing decision to something the person needs to do.

A demonstration may reveal promising features. It cannot establish that every configured page, document, message, and step will work for the intended audience.

Describe acceptance in practical terms

Before selecting a supplier, identify the important journeys and the applicable standards with appropriate accessibility expertise. Include the materials the organization will add after installation.

Ask how the supplier supports evaluation, addresses defects, and communicates limitations. The organization needs enough information to understand its own responsibilities as well as the supplier’s commitments.

Avoid treating a broad assurance as a complete answer. A useful agreement makes clear who investigates a reported barrier, who changes the relevant component, and how progress is communicated. Those questions are easier to resolve before an urgent problem arrives.

Involve people without making them the testing department

Participants can reveal difficulties a team has overlooked. Invite their contribution through a suitable, respectful process, with appropriate recognition for their time.

Do not ask one person to represent every disability or communication preference. User experience complements technical and professional accessibility evaluation; it does not replace it.

In our registration example, the participant may identify where the task becomes confusing. The organization and supplier remain responsible for investigating the cause and arranging a response. The person should not have to prove the same barrier repeatedly to different teams.

Plan for what happens after purchase

Digital content changes. Colleagues upload documents, update activity details, and add links to other services. Accessibility therefore needs a place in ordinary content review and supplier management.

Agree who reviews new material and how staff learn the relevant practices. Keep a route for reporting barriers visible and usable, including for people who cannot complete the online form.

When a component changes, revisit the important journeys. A previously successful test is evidence about that version and configuration, not a permanent guarantee about everything the service will become.

Give people a useful way to continue

If a barrier occurs, ask what arrangement the person would prefer while the issue is investigated. A telephone call may help one participant and be unsuitable for another.

Explain the available options honestly. An alternative route should preserve dignity and privacy as far as the circumstances allow, rather than asking someone to announce personal details in a public space.

Record the underlying issue through the proper process. Successfully helping one person finish a task does not mean the barrier has been removed for everyone else.

Where genus fits in the decision

Today, organizations can configure genus care apps and care walls for their audiences and use prepared resources within those experiences. That flexibility makes review of the actual content, device, and journey especially important.

We do not present choosing genus as proof of accessibility or legal compliance. The organization needs to examine the configured experience with relevant expertise and users, and agree how concerns will be handled.

A useful purchasing conversation connects capabilities with responsibilities. It should leave everyone clearer about the experience being offered and the work required to keep it usable.

Budget for that continuing work. Content preparation, training, testing, and responding to problems take time. A purchase price that omits those responsibilities may leave the program without the capacity to deliver the experience it promised.

Before the agreement is signed

Can we explain who will respond when a person cannot complete the task—and how we will know the response has helped?