A later deadline does not remove today’s barrier

What we found in the news

On May 7, 2026, HHS announced an interim final rule extending certain web and mobile accessibility compliance dates (opens in a new tab) for recipients of its funding. The announcement described an action that:

“extends the timeline for compliance”

— HHS Office for Civil Rights, May 2026

The extension concerned specified digital-accessibility standards under Section 504. It did not remove existing disability protections or apply one timetable to every website. Organizations needed to understand the rules relevant to them while continuing to respond to the access needs of the people they serve.

A date changes; a task remains

Consider an illustrative visitor trying to register for a community event. The form may be difficult to use with a keyboard, or its instructions may be unclear with assistive technology. A later compliance date does not help that person finish the task today.

That is why we think an accessibility plan should begin with the experience as well as the calendar. People still need to find information, make contact, join activities, and ask questions while longer improvements are underway.

At genus, the useful ambition is participation. A technical standard helps define important requirements, while the service needs to examine what a person can actually do in its particular setup.

Choose the journeys that matter

List the tasks people most need to complete. Include the less visible steps around them: finding the correct page, understanding the offer, correcting an error, and knowing whether a request was received.

Ask people with different access needs to help review those journeys in suitable ways. One person's successful experience cannot stand in for everyone else's. A quiet demonstration may also miss difficulties that appear on a shared device or in a busy reception area.

Use technical review alongside participant feedback. Each can reveal problems the other misses. Give the work a responsible team and a clear way to record issues without collecting unnecessary personal information.

Keep a usable route available during repairs

If a task is difficult, explain how someone can request an appropriate alternative. Check that the alternative is genuinely available and respects privacy, rather than simply moving the same barrier into another channel.

A telephone route may help some people and exclude others. Asking a visitor to read private details aloud may create a new problem. Start by asking what arrangement works for the person, then involve the colleague who can provide it.

Staff need guidance for situations they cannot resolve immediately. The response should not depend on the visitor knowing which manager to ask for or on one helpful employee being present.

Turn extra time into a maintained improvement plan

Agree who owns the website, the content, third-party tools, and the service process around them. Some barriers may be fixed in a page template; others may involve a document, an embedded form, or a decision about how registration works.

Prioritize with a clear account of the effect on people and the relevant requirements. Give owners time and resources to act. Test changes in the actual journey, and check that fixing one problem has not introduced another.

Keep accessibility in routine content and purchasing decisions. A one-off project can lose ground if new documents and tools arrive without the same review. Progress becomes more useful when the organization knows how to maintain it.

For the people trying to participate

Invite people to describe the task that became difficult and the arrangement that would help. Make feedback possible without requiring a technical diagnosis. Where appropriate, explain what has changed and offer a way to say whether the response worked. Participation in a review should remain a choice.

The genus connection

Configured genus care apps and care walls provide places for reviewed resources, updates, and activities. The organization still needs to examine content, devices, permissions, and the complete experience with its intended audience.

We do not treat the presence of a platform as proof of accessibility or compliance. The useful connection is a continuing practice: prepare the information carefully, test the journey, listen to the people using it, and give the response an owner.

One question for the next review

Which important task is difficult for someone today, and what can we do while the longer fix is being completed?