Your website meets people before you do. What’s it saying to them?

What Miami Valley business owners and nonprofit leaders should know before the 2027 accessibility deadlines

Springs Content Studio graphic. A lit desk lamp in a dark room. Text: "The door is open. Can everyone get through it?" 2027 accessibility deadlines.

Your website meets more people than you ever will. It greets the customer in Yellow Springs at 9 p.m., the donor comparing two nonprofits before she gives, the family new to Xenia looking for someone they can trust. You are asleep, with your kids or three jobs deep — and it is out there, doing the work of a first impression on your behalf.

Which makes it, in a sense, your hardest-working employee. It never closes. It works nights, Sundays and the week between Christmas and New Year's. So, the question is not whether you have one. Most of you do. The question is who it is reaching, who it is turning away and whether the people you most want to serve can get through the door.

For a lot of small businesses and nonprofits, the honest answer is that some of them can't. Here is what a website earning its keep does — for everyone who lands on it — what is changing for some of you and what you can fix this week without hiring anybody.

Five jobs your website should be doing

1.   Get found. Someone in Beavercreek types "emergency electricians near me" into their phone at 9 p.m. and your name comes up or it does not. That is a function of your Google Business Profile, the actual words on your pages and how fast the site loads on a phone. It has almost nothing to do with how pretty the homepage is.

2.   Answer the question before the phone rings. Hours. Service area. Whether you take walk-ins. Roughly what things cost. Every question your site answers is a call you do not have to return and a customer who does not drift to a competitor while waiting for one.

3.   Build trust in about eight seconds. People decide fast. Real photographs of real people in a real place do more work here than any amount of polished copy. A stock photo of a smiling team that is not your team reads as exactly what it is.

4.   Ask for something. One clear next step per page. Book. Call. Donate. Subscribe. A page with five equally weighted buttons is a page with no buttons.

5.   Work for everyone who lands on it. This is the job most sites fail, and the one with the most riding on it. For a growing number of organizations in this region, it is also about to stop being optional.


The rules are changing, and not for everyone equally

In April 2024, the U.S. Department of Justice finalized a rule setting a technical standard for digital accessibility under Title II of the Americans with Disabilities Act. The standard is WCAG 2.1 Level AA, an international benchmark covering things like color contrast, keyboard navigation and whether a screen reader can make sense of a page. The DOJ publishes plain-language guidance on the rule at ADA.gov.

On April 20, 2026, the DOJ published an interim final rule pushing the compliance dates back by one year. It was explicit that nothing else moved. The technical standard is unchanged, and so is the underlying obligation. Only the date changed.

Whether any of this applies to you depends on what kind of organization you run. There are three buckets, and most coverage online blurs them together.

If you are local government, this is a hard deadline. Villages, cities, townships, school districts, library districts and park districts are all covered, and there is no exemption for being small. Under the 2026 extension, entities serving 50,000 or more people have until April 26, 2027. Entities under 50,000, along with special district governments, have until April 26, 2028. Most jurisdictions in the Miami Valley fall into that second group. Dayton, Kettering and the counties themselves fall into the first. Check your own population figure rather than guessing, because the two dates are a year apart.

If you are a nonprofit, you are probably not under Title II, but that does not put you in the clear. Organizations receiving federal financial assistance from Health and Human Services are covered by HHS's own 2024 rule under Section 504 of the Rehabilitation Act, which adopts the same WCAG 2.1 Level AA standard. HHS extended its dates in May 2026 to May 11, 2027, for recipients with 15 or more employees and May 10, 2028, for those with fewer. That reaches further into this community than people expect, and it commonly picks up health centers, human services agencies and aging services programs. Separately, nonprofits operating as places of public accommodation fall under ADA Title III, which carries no deadline because the obligation is already in force. Donation forms and program application portals carry the most risk, since those are the pages where an inaccessible site stops being an inconvenience and starts being a locked door.

If you are a small business, no deadline applies to you. Title III still does. The law firm Seyfarth Shaw, which tracks this litigation every year, counted 3,117 website accessibility lawsuits filed in federal court in 2025, a 27% increase over 2024 and roughly 36% of all ADA Title III federal filings. There is also a quieter reason to pay attention: if you sell to a municipality, a district or a federally funded nonprofit, expect accessibility requirements to start appearing in the contracts they send you.

Those are the dates. They are also the least interesting reason to do any of this.

The part that has nothing to do with a deadline

The Centers for Disease Control and Prevention reports that 28.7% of American adults, an estimated 70 million people, live with a functional disability affecting hearing, vision, mobility, cognition, self-care or independent living. Among adults 65 and older, it is 43.9%. Picture a room in Xenia, in Kettering, in Bellbrook, in Centerville, and run that math. These are your customers, your donors, your patients and your neighbors, and some of them are on your website right now, giving up.

That is what an inaccessible site is. Not a technical shortcoming, but a door somebody cannot get through.

We tend to picture a screen reader when this comes up, and that is part of it. The rest is broader and more ordinary. The customer with tremors who cannot hit your small mobile menu button. The retiree with cataracts squinting at light gray type. The person with a migraine who needs to enlarge the text. The parent holding a baby who has one hand free. The contractor in a loud truck who needs your video captioned. Accessibility is what makes a website work under conditions that are less than ideal, and almost nobody is browsing under ideal conditions.

There is a business case in this, and it is a real one. Every barrier you remove is a booking that gets completed instead of abandoned. Every labeled field is a donation that goes through. Reaching more people is the whole point of marketing, and this is one of the few investments where you can name the specific people you were losing.

We would make the case even if the numbers were smaller, and we want to be plain about that. Springs Content Studio builds for accessibility because it is the right thing to do. Your website is a public front door. Deciding who gets to walk through it is a choice, whether or not you make it on purpose. Almost nobody in this community would build a storefront with a step and no ramp. The digital version of that step is easier to miss, cheaper to fix and exactly as consequential to the person standing outside it.

The deadlines are useful for one thing. They give some organizations a date. Everybody else already had a reason.

Two things you have been told that are not true

•     An accessibility widget makes you compliant. It does not. In January 2025, the Federal Trade Commission charged accessiBe, one of the largest overlay vendors, with making false or unsubstantiated claims that its automated plug-in could make any website WCAG compliant. The final order required a $1 million payment and barred the company from repeating those claims without evidence to back them. Overlays sit on top of the problem. They do not fix it.

•     A clean automated scan means you passed. A scan is a starting point, not a verdict. Automated tools find machine-detectable problems. They cannot judge whether your alt text is meaningful, whether your headings describe anything or whether a person can finish your donation form using only a keyboard. Those take a human. For scale, WebAIM's annual survey of the top 1 million home pages found low-contrast text on 83.9% of them in its 2026 report, the most commonly detected issue for years running, and that is only counting what software can catch.

What is really getting in the way

In conversations with owners and directors across the Miami Valley, the same five obstacles come up repeatedly.

"I paid for it once in 2019 and nobody has touched it since." Put a recurring 30-minute appointment on the calendar once a quarter. Hours, staff, prices, photos. That is the whole job.

"I have no idea if it is doing anything." Pick two numbers and ignore the rest. How many people found you through search, and how many took the action you wanted. Google Search Console and your Business Profile insights will both tell you for free.

"It looks fine on my laptop." Most of your visitors are not on a laptop. Open your own site on your phone, one-handed, outside in the sun. That is the real test, and it is the same test that surfaces half your accessibility problems.

"I do not have time to write." You are already writing. Every question you answer by email is a page. Save your next three replies, and you have a month of content.

"I cannot afford a rebuild." You may not need one. Alt text, heading structure, color contrast and form labels are edits to a site you already own, not a reason to start over. Rebuild when the foundation is broken, not when the paint is.

Six things you can fix this week

•     Add alt text to every image that carries meaning, and mark decorative images as decorative.

•     Use real headings. One H1 per page, then H2s and H3s in order. Do not fake a heading by bolding a line of text.

•     Label every form field. "Email address" beside the box, not gray placeholder text inside it that vanishes when someone starts typing.

•     Check your color contrast. WCAG 2.1 Level AA asks for a ratio of at least 4.5 to 1 for body text, and free browser tools will flag failures in seconds. Light gray on white is the most common one.

•     Unplug your mouse and try to use your own website. If you cannot reach the phone number or finish the contact form, neither can a lot of your visitors.

•     Look at your PDFs. Scanned newsletters, menus and annual reports are frequently unreadable to a screen reader. Often the better fix is to put the content on a web page instead.

Where to start

Start with the page that matters most. Not the homepage — the page where someone does what you need them to do: the donate button, the contact form, the booking page. Fix that one properly. Then work outward.

If you are a village, a district or a federally funded nonprofit, start sooner than feels necessary. A year sounds like plenty until you discover the fix involves your vendor, your budget cycle and a board vote. If you are a small business, you have more time and the same reason to bother. Every fix on that list is one more person who can reach you.

Your website has been on the clock this whole time. It might as well be doing the job for everybody.


Sources

•     U.S. Department of Justice, ADA Title II web and mobile app accessibility guidance (ADA.gov): https://www.ada.gov/resources/web-rule-first-steps/

•     U.S. Department of Justice, interim final rule extending Title II compliance dates, April 20, 2026 (Federal Register): https://www.federalregister.gov/documents/2026/04/20/2026-07663/extension-of-compliance-dates-for-nondiscrimination-on-the-basis-of-disability-accessibility-of-web

•     U.S. Department of Health and Human Services, Section 504 final rule, May 9, 2024 (Federal Register): https://www.federalregister.gov/documents/2024/05/09/2024-09237/nondiscrimination-on-the-basis-of-disability-in-programs-or-activities-receiving-federal-financial

•     U.S. Department of Health and Human Services, interim final rule extending Section 504 compliance dates, May 11, 2026 (Federal Register): https://www.federalregister.gov/documents/2026/05/11/2026-09266/extension-of-compliance-dates-for-nondiscrimination-on-the-basis-of-disability-accessibility-of-web

•     Centers for Disease Control and Prevention, Disability and Health Data System: https://www.cdc.gov/disability-and-health/articles-documents/disability-and-health-data-now.html

•     Federal Trade Commission, complaint and proposed order against accessiBe, January 2025: https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-order-requires-online-marketer-pay-1-million-deceptive-claims-its-ai-product-could-make-websites

•     Federal Trade Commission, final order requiring accessiBe to pay $1 million, April 2025: https://www.ftc.gov/news-events/news/press-releases/2025/04/ftc-approves-final-order-requiring-accessibe-pay-1-million

•     WebAIM, The WebAIM Million, 2026 report: https://webaim.org/projects/million/

•     Seyfarth Shaw, federal website accessibility lawsuit filings for 2025 (ADA Title III blog): https://www.adatitleiii.com/2026/03/federal-court-website-accessibility-lawsuit-filings-bounce-back-in-2025/

Next
Next

We're cutting the ribbon — come celebrate with us!