Why your county website fails accessibility audits, and the cheap fixes

Most county websites fail accessibility audits for a short list of predictable reasons: scanned PDFs that screen readers cannot read, text and buttons with too little color contrast, images missing alt text, forms whose fields have no labels, content that cannot be operated with a keyboard, videos without captions, and third-party widgets bolted on by vendors. The good news is that almost none of these are expensive to fix. Most are content and configuration problems your existing team can correct, not rebuilds that require new software or a new site.

That matters right now because government website accessibility is no longer just good practice. Under the Department of Justice’s 2024 ADA Title II rule, state and local governments must meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. In April 2026 the DOJ extended the deadlines by a year: April 26, 2027 for entities serving populations of 50,000 or more, and April 26, 2028 for smaller entities and special district governments. The standard did not change. You simply have more runway to get there. Here is what auditors actually flag, and what each fix really takes.

PDFs are the single biggest failure point

If your county is like most, your site links to hundreds or thousands of PDFs: meeting minutes, permit applications, budgets, zoning notices, tax forms. A huge share of audit failures trace back to these documents. The two most common problems are scanned PDFs, which are essentially photographs of paper that a screen reader reads as a blank page, and untagged PDFs, which have no underlying structure telling assistive technology what is a heading, a paragraph, or a table.

The cheap fix is mostly process, not purchase. Going forward, post the original digital file (the Word or Google Doc) rather than a scan, and run it through the accessibility checker built into Word or Acrobat before publishing. For your back catalog, you rarely need every old PDF remediated at once. Prioritize the documents people actually use: current forms, active permits, this year’s agendas. Many older documents can be replaced with a plain web page, which is easier to make accessible than any PDF. The win here is reclaiming staff time: a clear publishing checklist stops the problem from regenerating every week.

Color contrast: the failure you can see

Auditors consistently flag text that does not stand out enough from its background. Light gray text on white, pale blue links, white text on a light photo, or a county-brand color used for buttons that washes out against the page. WCAG 2.1 AA sets specific contrast ratios: 4.5 to 1 for normal text and 3 to 1 for large text.

This is one of the cheapest fixes because it lives in your site’s stylesheet, not your content. A free contrast checker (WebAIM’s is the standard) tells you in seconds whether a color pair passes. Often the correction is darkening one brand color by a few shades across the whole site, which your web vendor or staff can do in one pass. You do not redesign the site. You adjust a handful of color values.

Alt text for images

Every meaningful image needs alternative text: a short description a screen reader announces so a blind visitor knows what the image conveys. Your county seal, a photo of the new library, a map, an infographic with the trash pickup schedule all need it. The frequent failure is either no alt text at all or unhelpful alt text like “image1.jpg.”

Writing alt text costs nothing but a little judgment. Describe the purpose, not every pixel. “County seal” is fine. For an infographic, the alt text or nearby page text must convey the actual information, because a sighted-only graphic locks out anyone using a screen reader. Decorative images that add nothing should get empty alt text so screen readers skip them. This is a training item more than a technical one, and it pays back every time staff post a new page.

Forms without labels

Online forms are where accessibility and real county business collide: report a pothole, apply for a permit, register for a program, pay a bill. Auditors flag form fields that have no programmatic label, meaning the little caption next to the box is not actually connected to it in the code. A screen reader then reads an unlabeled box, and the user has no idea what to type. Error messages that rely only on color (a red outline with no text) fail for the same reason.

Fixing this is usually a small code change your developer or form vendor handles quickly: associate each label with its field, and make error messages readable as text. If your forms come from a third-party service, this is exactly the kind of question to put to that vendor in writing.

Keyboard navigation

Many people cannot use a mouse and navigate entirely with the keyboard, using the Tab key to move between links and fields and Enter or the space bar to activate them. Audits routinely catch menus, dropdowns, date pickers, and pop-ups that work with a mouse but trap or lose keyboard users. A related failure is the missing visible focus indicator: the outline that shows where you are on the page as you tab through it.

You can test this yourself in ten minutes. Put your mouse aside and try to complete a common task on your site using only the Tab and Enter keys. If you get stuck or cannot see where you are, so will your residents. The fixes range from a simple stylesheet change to restore focus outlines, to vendor work on a custom menu. Identifying the problem is free and tells you exactly what to ask for.

Captions and video

If your county posts videos, recorded meetings, public service announcements, emergency updates, they need captions so deaf and hard-of-hearing residents can follow along. Auto-generated captions from YouTube are a starting point but are often too inaccurate to count as compliant, especially with local names, street names, and acronyms.

The affordable path is to use auto-captions as a first draft and have a staff member correct them, which is far faster than captioning from scratch. For live-streamed meetings, build captioning into how you publish the recording afterward rather than treating it as an afterthought.

Third-party widgets are the hidden trap

Counties stitch a lot of outside services into their sites: payment portals, GIS maps, calendars, document viewers, chatbots, social media feeds, and so-called accessibility overlay widgets. Each is a place your audit can fail even when your own pages are clean, because you do not control that vendor’s code. Overlay widgets deserve special caution: they are marketed as a one-click fix, but they do not make a site compliant and have been named in accessibility lawsuits.

There is no overlay shortcut to government website accessibility. The realistic step is to inventory the third-party tools on your site, ask each vendor for their accessibility documentation (a current VPAT or ACR), and weigh accessibility when you renew or replace a service. Choosing accessible vendors is often cheaper than remediating an inaccessible one later.

Where to actually start

You do not have to solve all of this at once, and you should not try. A practical sequence: run a free automated scan to get a baseline, do the keyboard test yourself, fix site-wide color contrast in one pass, put a simple accessibility checklist in front of everyone who publishes content, and triage your PDFs by how often residents use them. That alone clears a large share of common audit findings, and most of it is staff time and configuration rather than new spending.

This is also where the right tooling can give your team its time back instead of adding work. At Rudder we build AI agents (12 agents across 3 products) aimed at the repetitive parts of work like checking documents against a rule set or flagging pages that drift out of compliance, so the people who run your county can focus on judgment calls a tool should never make. The technology supports your staff. It does not stand in for them.

If you want a straight answer about where your county actually stands, we are glad to look at your real site and tell you the smallest useful next step, even if that step is not hiring Rudder. Sometimes it is fixing one stylesheet color, replacing a handful of PDFs, or sending two questions to a vendor. You deserve to know what is genuinely cheap and what is not before the 2027 and 2028 deadlines arrive.