ADA compliant website design has a deadline attached if you are a public entity

ADA compliant website design means building to WCAG 2.1 Level AA, the standard the Department of Justice adopted for state and local government websites. MediaCutlet handles accessibility during the build rather than selling an overlay widget that claims to fix it afterward. For public entities the current compliance dates are April 26, 2027 or April 26, 2028, depending on the population served.

Most ADA compliant website design conversations begin with a question about legal exposure and end with somebody buying a widget. The useful starting point is the standard itself. WCAG 2.1 Level AA is a published set of testable criteria covering contrast, keyboard operation, form labelling and focus order, and it is what regulators and courts have converged on.

MediaCutlet is four senior operators who embed with leadership teams, so the person testing your site is the person who built it. No account managers, no junior handoffs, no subcontracted outcomes. We keep score in dollars rather than impressions on the results page. Across web and AI projects we have helped clients support more than $500 million in revenue, on sites that had to work for everyone who landed on them.

MediaCutlet works out of Red Bank, New Jersey, with clients nationally, and Strato Doumanis leads the digital and AI practice. Much of our work sits with associations, government agencies and the organizations serving them, which is where accessibility stopped being optional first. One thing to say plainly up front: we are not attorneys and we will not tell you whether you are exposed. We will tell you exactly what your site does and does not do.

What standard does ADA compliant website design actually mean?

There is no such thing as an ADA certificate for a website. What exists is WCAG, published by the W3C and organized into three conformance levels. Level A is the floor, Level AA is what regulators reference, and Level AAA is aspirational and not expected across a whole site.

WCAG 2.1 arrived in 2018 and WCAG 2.2 followed in 2023, adding new criteria without changing any of the existing ones. That matters practically: building to the newer version does not put you out of step with a rule written against the older one. We build to 2.2 and report against 2.1 AA where a regulation names it.

Who has a legal deadline, and when is it?

State and local governments do, including public universities, school districts and special districts. The Department of Justice finalized a Title II rule in 2024 naming WCAG 2.1 Level AA, then in April 2026 extended the compliance dates by a year. Entities serving 50,000 or more now have until April 26, 2027; smaller entities and special districts until April 26, 2028. The substance did not change, only the calendar.

Private businesses sit differently. No federal rule names a technical standard for them and that rulemaking has been paused for years, but courts and plaintiffs reference WCAG anyway, so the absence of a rule is not the reassurance it sounds like. Whether that creates risk for you is a question for your counsel, not your web team.

Do accessibility overlays and widgets work?

Not as a substitute for building the site properly. An overlay sits on top of your markup and tries to correct it in the browser. It cannot know what an image of a chart is meant to show, restructure headings that were never in order, or untangle a keyboard trap in a component built without one.

Practitioners have argued this for years, and organizations running overlays have still faced complaints. Vendors dispute the criticism and you can read their side. Our position is narrower: an overlay is at best temporary cover while real remediation happens, and treating it as the fix is how a site stays broken while its owner believes it is handled.

How do we know whether our site passes?

Automated scanning finds perhaps a third of it. The tools are good at contrast ratios and missing attributes, and blind to whether an alt description is meaningful or whether a screen reader can complete your checkout. The rest is manual: navigate with the keyboard alone, run it with a screen reader, and try the tasks people actually come to do.

Test at template level and then at content level, because they fail differently. A perfectly built template is undermined the first time somebody uploads an image with no description. Accessibility is a build standard and an editorial habit, and skipping the second quietly undoes the first.

An accessibility engagement with us includes:

• A conformance review of the current site against WCAG 2.1 AA, tested rather than scanned
• A prioritized remediation list, worst barriers and highest-traffic pages first
• Template-level fixes so new pages inherit the work, plus keyboard and screen reader testing of the tasks that matter
• Document and PDF review, which is where public entities usually find the backlog
• An accessibility statement that describes your real status
• Training for whoever publishes content, where conformance erodes

Engagement options: accessibility built into a new site, remediation of an existing one, or a $2,500 to $3,000 assessment that tells you where you stand before anyone commits a budget.

If you are a public entity the calendar is deciding for you, and remediation takes longer than the deadline suggests. Start a conversation and find out where your site actually stands.

Frequently asked questions

Are nonprofits and associations covered?

It depends on the organization, and it is worth asking your counsel rather than guessing. Many operate places of public accommodation, receive federal funds or serve public entities under contract, and any of those can bring obligations along with it.

What if we only fixed the pages people actually use?

That is usually where we start, and it is a legitimate strategy rather than a shortcut. Highest-traffic pages and the paths to your core tasks come first, then templates, then the long tail nobody visits.

Do our PDFs need to be accessible too?

Under the Title II rule, documents you publish are treated as web content, and PDFs are where most public entities discover the real size of the job. Scanned documents with no text layer are the common worst case.

How much does accessibility work add to a build?

Very little when it is designed in from the start, because it is mostly discipline rather than extra features. It is expensive when retrofitted, which is the honest argument for handling it during the build.

Who keeps the site accessible after launch?

Your content team, whether or not they know it yet. One uploaded image without a description, one heading used because it looked right, and conformance slips. We train publishers and set up checks so it does not depend on memory.

Does accessibility work help our search performance?

Often, though not because Google rewards accessibility directly. Clean heading structure, descriptive text alternatives and pages that work without a mouse tend to be pages search engines and AI assistants parse more reliably.