Making a government website accessible on a limited budget means prioritizing high-impact WCAG fixes, documenting progress, and building a defensible ADA Title II compliance program over time.
Most accessibility guidance is written for agencies that can hire a consultant, commission a full audit, engage a development partner, and run a multi-year governance program. That is the right way to do it. It is also out of reach for a significant portion of the public agencies that ADA Title II covers.
The city with 12,000 residents and a two-person IT department. The rural water district with a website that nobody has touched since 2019. The small county library system whose web manager also handles purchasing, inventory, and the quarterly newsletter. The special district with a part-time administrative coordinator who manages the website in addition to her actual job.
These agencies have the same ADA Title II compliance obligations as Los Angeles County. They have a fraction of the resources. And most of the guidance available to them assumes a budget, a team, and a technical capacity that does not exist.
This guide is written for the agencies that have been told they need to be accessible and have no idea how to get there with what they have. It is not about doing accessibility cheaply. Accessibility done cheaply is almost always done wrong. It is about doing the right things in the right order so that every dollar and every hour of capacity you spend produces the maximum compliance value.
The framework here is explicitly about prioritization under constraint. What to do first. What to do next. What to defer. And how to build a documented compliance posture that demonstrates good faith even when you are not yet fully conformant.
First: What “Limited Budget” Means for Government Accessibility
Before getting into the framework, it is worth naming what resource constraint actually means for different types of agencies — because the constraints are different and the strategies need to match.
Constraint Type 1: No dedicated web staff. The website is managed by someone whose primary job is something else. Updates happen when they happen. There is no development capacity. There is no budget for professional services. Every action has to be something a non-specialist can do.
Constraint Type 2: Small team, minimal budget. There is a web manager or IT generalist who understands the site technically, but there is no budget for professional auditing, no development contractor, and no resources for significant technical work. Actions need to be things the team can do themselves with limited technical complexity.
Constraint Type 3: Moderate capacity, constrained budget. There is a capable web team and some technical capacity, but the accessibility budget has not been approved, the project has not been prioritized, and there is no structured program in place. The constraint is organizational and budget-related rather than purely capacity-related.
The strategies in this guide apply across all three types, with different actions appropriate to different capacity levels. Read the whole guide but be honest about which type of constraint you are actually dealing with. A Type 1 agency trying to implement a Type 3 strategy will fail. A Type 3 agency operating like a Type 1 agency is leaving significant compliance value on the table.
Defensible ADA Compliance vs Perfect Accessibility
The most important mindset shift for agencies working under resource constraints is understanding that the ADA Title II standard is not perfect conformance. It is demonstrated, documented, ongoing effort toward conformance.
An agency that has conducted no audit, made no documented accessibility improvements, has no remediation log, and has published no accessibility statement is in a completely different enforcement position than an agency that has assessed its compliance posture, identified its highest-risk failures, addressed what it can address with available resources, documented every action it has taken, published an honest accessibility statement with a working complaint contact, and established a plan for ongoing improvement.
The first agency has done nothing demonstrable. The second agency has built a good faith compliance record — even if it has not achieved full WCAG 2.1 AA conformance.
Good faith compliance is built from documented effort, not from completed remediation. That distinction is the foundation of every recommendation in this guide. Every action you take should be documented. Every decision about what to defer should be documented alongside the reason. The documentation record is itself a compliance asset.
TLDR: Minimum Viable ADA Compliance Program
- Publish an accessibility statement
- Open a remediation log
- Set page language attribute
- Run free accessibility scans
- Fix alt text on key pages
- Implement skip navigation
- Fix focus indicators
- Prioritize critical documents
- Test core forms
- Run monthly monitoring
Phase 1: Free Accessibility Fixes That Create Immediate Compliance Value
Start here. These actions require no budget, minimal technical expertise, and can be completed by anyone who manages a government website. Some of them will take an afternoon. All of them create documented compliance value immediately.
1. Publish an Accessibility Statement
An accessibility statement is the single highest-value, lowest-cost accessibility action a government agency can take. It takes two to three hours to write and publish. It is one of the first things enforcement bodies look for. And most government agencies do not have one.
Write the statement using the template in Hounder's accessibility statement guide. The key elements:
The technical standard you are working toward (WCAG 2.1 AA). Your current conformance status — be honest. If you have not done a formal audit, you are not "fully conformant." Say "partially conformant" or "working toward conformance." Known limitations and what you are doing about them. A working email address and phone number for accessibility reports. A description of what happens when someone reports a barrier (even if the answer is "we will investigate and respond within 10 business days"). The date you last reviewed the statement.
Publish it. Link it in the footer of every page on your site. Test the email address to confirm it works and goes to someone who will actually respond.
This takes an afternoon. It creates documented public commitment. It opens a complaint intake channel. And it signals to any enforcement body that looks at your site that you are engaging with the obligation rather than ignoring it.
Document it: Note the date you published the statement and the date you set up the complaint email in your compliance record.
2. Open a Remediation Log
Open a spreadsheet. Create these columns: Date Identified, Issue Description, WCAG Criterion, Location (page URL), Severity, Status, Date Remediated.
You do not need to have anything to put in it yet. Opening it and using it from today forward is what matters. Every accessibility issue you identify from this point — through testing, through user reports, through your own observation — gets an entry. Every fix gets a completion date.
The remediation log is the primary evidence of ongoing good faith effort. A log with ten entries showing ten issues identified and addressed over six months is more valuable in an enforcement context than a completed audit with no follow-through.
Cost: Zero. Time: 20 minutes to set up. Use Hounder's Remediation Log Template for expedited process.
3. Set the Page Language on Every Page
This is a technical fix that takes minutes and is one of the most universally missed accessibility requirements on government websites. Every HTML page must specify the language of its content in the <html> tag:
<html lang="en">
This allows screen readers to use the correct voice and pronunciation profile. Without it, some screen readers may default to a pronunciation profile that makes the content incomprehensible.
Check your CMS settings. In most platforms — Drupal, WordPress, and others — there is a site-wide language setting that applies this attribute to every page automatically. If yours is missing, it is usually a one-field fix in your site configuration.
Check it: Open any page on your site. View the page source (Ctrl+U in most browsers). Look for the <html tag in the first few lines. If it says <html lang="en"> or similar, you are set. If it says just <html>, you need to fix this.
Document it: Note the date you confirmed or set the language attribute.
4. Install and Run a Free Accessibility Scan
Install the axe DevTools browser extension (free version, available for Chrome and Firefox). Run it on your five highest-traffic pages. Read the violations output. Do not try to fix anything yet — just document what it finds.
The axe scan output gives you a prioritized view of your most common automated accessibility failures. It is not a complete audit — automated tools catch approximately 30 to 40 percent of WCAG failures — but it tells you what the easiest-to-detect problems are and which of them appear across templates (meaning a single fix resolves them everywhere).
Document it: Save the scan results for each page. Note the date. This is your baseline documentation — evidence that you assessed your compliance posture on a specific date.
5. Fix Any Images Missing Alt Text on Your Five Most-Visited Pages
From your axe scan results, look at image-alt violations on your five most-visited pages. For every image flagged as missing alt text, add one.
For informational images — photos, charts, maps — write alt text that describes what the image communicates. For decorative images, add an empty alt attribute (alt="").
Most CMS platforms allow you to add or edit alt text on images without touching code — through the media library or the image insertion interface. This is typically a task any content editor can do.
This is free. It takes an afternoon. It closes one of the most commonly cited ADA complaint categories immediately on your highest-traffic content.
Document it: Log each image fixed in your remediation log with the page URL, the issue description, and the date fixed.
Phase 2: Low-Cost Accessibility Fixes with High Impact
These actions require some technical capacity — either a web manager who understands HTML and CSS, or a brief engagement with a developer. They are not free, but they are among the highest-return accessibility investments a constrained agency can make.
6. Implement Skip Navigation
A skip navigation link is the first focusable element on every page. It allows keyboard users to bypass the navigation menu and jump directly to the main content. Without it, a keyboard user must tab through every navigation item on every page before reaching the content.
Implementing skip navigation is a small amount of CSS and HTML. For a developer, it is a 30 to 60-minute task. For a web manager comfortable with template editing, it is doable in an afternoon with the right reference.
The HTML:
<a href="#main-content" class="skip-link">Skip to main content</a>
The CSS (visually hidden but visible on focus):
.skip-link {
position: absolute;
top: -40px;
left: 0;
background: #000;
color: #fff;
padding: 8px;
z-index: 100;
}
.skip-link:focus {
top: 0;
}
And the target in the page template:
<main id="main-content">
<!-- page content -->
</main>
This single implementation resolves a critical keyboard navigation failure on every page of your site simultaneously. For a developer billing hourly, this is typically one to two hours of work. For a web manager with template access, it is a task with a clear tutorial available from WebAIM and others.
Document it: Log the implementation date in your remediation log. This is a template-level fix that resolves the issue across the entire site.
7. Fix Focus Indicators
Open your website. Press Tab. Can you see where keyboard focus is? If the default browser focus outline has been removed by your CSS — which happens when developers add outline: none or outline: 0 to suppress the visual indicator — keyboard users have no way to see where they are on the page.
Find in your stylesheet where focus is being suppressed:
/* These are accessibility failures */
:focus { outline: none; }
*:focus { outline: 0; }
a:focus { outline: none; }
Remove those suppressions. Replace them with a visible custom focus style if the default browser outline conflicts with your design:
:focus-visible {
outline: 3px solid #005ea2;
outline-offset: 2px;
}
This is a CSS change. For a developer it takes 30 minutes. For a web manager with stylesheet access it is a single edit. The impact is immediate and site-wide.
Document it: Log the date this was fixed.
8. Correct Heading Hierarchy on Primary Templates
From your axe scan and WAVE evaluation, identify heading hierarchy failures — heading levels skipped, H1 used multiple times on a page, section titles formatted as bold text rather than heading elements.
For template-level heading failures — where the issue is in the shared page template rather than individual content — a developer fix resolves the issue across every page simultaneously. For content-level heading failures — where editors have applied incorrect heading levels in specific pages — these need to be corrected page by page, starting with your highest-traffic content.
Prioritize fixing the template-level heading structure first. The H1 should be the page title. H2s should be major section headings. H3s should be sub-sections. No levels should be skipped. This hierarchy should be enforced by the template, not left to editor discretion.
Document it: Log template-level fixes as a single remediation entry. For content-level fixes, log the most critical pages individually.
9. Address Color Contrast Failures in Primary Text and Navigation
From your axe scan, identify color contrast failures. Focus first on:
- Primary body text on primary background
- Navigation link text on navigation background
- Button text on button background
These are template-level failures where fixing the CSS values resolves the failure across the entire site. Contrast failures in individual content areas — a colored callout box on one specific page — are lower priority than template-level text contrast.
Use the WebAIM Contrast Checker (webaim.org/resources/contrastchecker) to find replacement color values that meet the 4.5:1 ratio for normal text and 3:1 for large text and UI components while staying as close to your current brand colors as possible.
This is a CSS change that a developer or a technically capable web manager can implement. The work is primarily in identifying the failing color combinations and finding compliant replacements — the actual CSS change is minimal.
Document it: Log each color combination corrected with the old value, the new value, and the contrast ratio achieved.
Phase 3: Long-Term Accessibility Improvements for Government Websites
These actions require more significant time investment or organizational decision-making. They belong in a planned schedule — not as immediate actions, but as defined commitments with dates.
10. Address Your Document Library in Priority Order
PDF accessibility is the largest and most time-consuming accessibility problem in most government agencies. The approach for a constrained agency is triage — prioritize ruthlessly and build a going-forward standard to stop the backlog from growing.
The triage framework:
Priority 1 — documents residents need to complete government transactions with you: active permit forms, service applications, license renewals, payment information. These are the documents that create barriers to government services. Address them first, regardless of how much work it takes.
Priority 2 — current legally required communications: current-year water quality reports, current regulatory notices, current meeting agendas and minutes. These carry legal notification obligations alongside ADA obligations.
Priority 3 — frequently accessed informational documents: rate schedules, service guides, informational brochures that appear in search results and receive regular traffic.
Priority 4 — historical archive: board minutes from 2015, old reports, superseded documents. These can be addressed last, on a slow rolling schedule, or removed from public access if they are no longer relevant.
For each Priority 1 and 2 document that was created in Word: return to the source document, apply heading styles, add alt text to images, designate table header rows, and export using the correct accessibility settings. This can be done by a non-developer with a trained eye for Word accessibility — it does not require a developer.
For scanned documents that cannot be easily recreated: determine whether the information is still needed. If so, OCR processing and remediation in Acrobat may be necessary for Priority 1 and 2 documents. If not, remove the document from public access and replace with a note.
Going-forward standard: Before any new document is uploaded, it must pass a five-point checklist: heading styles used, alt text on all informational images, table headers designated, correct PDF export settings, accessibility checker passed. Train whoever uploads documents on this checklist. Post it next to their computer.
Document it: Create a document inventory log showing every document, its priority classification, its current accessibility status, and its remediation status. This inventory is itself a compliance document.
11. Test and Address Your Most Important Form
Identify the single most important transactional form on your website — the one residents use most or that is most essential to accessing your services. Run the keyboard navigation test protocol from the testing guide. Run axe DevTools on it. Note the failures.
For unlabeled form fields — the most common and most critical failure — the fix may be within reach of a web manager who understands HTML:
<!-- Before: unlabeled field -->
<input type="text" name="phone" placeholder="Phone number">
<!-- After: properly labeled field -->
<label for="phone">Phone number (required)</label>
<input type="text" id="phone" name="phone" required aria-required="true">
For more complex form failures — inaccessible custom components, broken error handling — a developer may be needed. Scope this as a specific, bounded engagement: "fix the accessibility of the [form name] form" with a defined list of issues from the testing output.
Document it: Log every issue found, whether it was addressed immediately or queued for developer work, and the date of each action.
12. Establish a Simple Monitoring Cadence
A monitoring cadence does not require expensive tools. A free, manually-run monthly check takes 30 minutes and creates the monitoring record that compliance programs need.
The free monthly monitoring protocol: Run axe DevTools on your five highest-traffic pages. Note any new violations not present in the previous month's scan. Log findings in the remediation log. Address any new template-level failures immediately. Queue content-level failures for the next available edit cycle.
Save the scan results each month with a date. This creates a monitoring record — dated scan results showing an ongoing evaluation cadence. Over 12 months, this record demonstrates sustained attention to accessibility, not a one-time assessment.
Document it: Save monthly scan results in a folder organized by date. The folder is the monitoring record.
The Budget Conversation: How to Make the Case
For agencies in Constraint Type 3 — where budget exists but has not been approved — the budget conversation is the key to moving forward. Here is how to frame it.
Frame the cost of inaction, not just the cost of action.
The average cost of an ADA accessibility lawsuit settlement is in the tens of thousands of dollars. A consent decree from the DOJ requires hiring third-party auditors, implementing court-supervised remediation timelines, and filing annual compliance reports — costs that dwarf a proactive accessibility program. The budget question is not "can we afford to do this?" It is "can we afford not to?"
Break the program into phases with budgets.
A full multi-year accessibility program is a large number. Phase 1 — baseline audit and template-level remediation — is a smaller, more approvable number. Present Phase 1 as the starting investment with a clear deliverable: an audit report, template fixes, an accessibility statement, and a remediation log that gives the agency documented compliance posture within 90 days.
Use the documentation you already have.
If you have already run the free tools and documented findings, present those findings to leadership. A list of specific accessibility failures on the agency's own website is a more compelling budget argument than abstract compliance requirements. Show the failures. Show what they mean for residents trying to use the website. Show what a professional audit and remediation program produces.
Connect to procurement cycles.
If a website redesign, CMS upgrade, or billing system replacement is already in the pipeline, accessibility can be built into that project's scope and budget rather than funded as a separate initiative. The redesign guide covers what accessibility requirements to build into an RFP. Folding accessibility into a planned procurement is often more achievable than securing a standalone accessibility budget.
What to Tell Residents While You Are Working On It
One of the most important things a resource-constrained agency can do is communicate honestly with residents about where the accessibility program stands.
The accessibility statement is the primary vehicle for this communication. A statement that says "we are partially conformant with WCAG 2.1 AA, we have identified the following specific limitations, and we are addressing them in the following order on the following timeline" is honest, demonstrates organized effort, and sets appropriate expectations.
A statement that claims full conformance when it does not exist — or no statement at all — is worse from a compliance standpoint than an honest acknowledgment of limitations.
When a resident reports an accessibility barrier, respond within 10 business days. Confirm you received the report. Tell them what you found. Tell them what you are doing about it. If you cannot fix it immediately, provide an alternative means of accessing the information or service while the fix is in progress. Document every complaint and every response.
These communications — honest statements, responsive complaint handling, documented follow-through — are the behavioral evidence of good faith that enforcement bodies look for. They matter as much as the technical fixes.
The Minimum Viable Compliance Program for a Resource-Constrained Agency
If you are starting from zero and have minimal capacity, here is the minimum viable program — the starting point that creates a documented compliance posture while you build toward more comprehensive coverage.
Do these things. In this order.
One: Publish an accessibility statement with an honest compliance status and a working complaint contact. This week.
Two: Open a remediation log. Start logging every issue you find from this point forward. This week.
Three: Set the page language attribute if it is missing. This week.
Four: Run axe DevTools on your five highest-traffic pages and document the findings. This month.
Five: Fix any images missing alt text on those five pages. This month.
Six: Implement skip navigation and fix focus indicators if they are suppressed. This month if you have the technical capacity, next month with a one-time developer engagement if you do not.
Seven: Address Priority 1 and 2 documents — active service forms and current legally required communications. Over the next 90 days.
Eight: Test your most important transactional form with keyboard navigation and axe. Document the findings. Fix what you can. Queue what requires developer work with a defined timeline.
Nine: Establish a monthly 30-minute monitoring check using free tools. Document each month's results.
Ten: Update your accessibility statement every time anything changes.
This is not a complete compliance program. It is a documented, ongoing, good faith compliance effort — which is the standard the law actually requires and which is achievable for any agency regardless of resource constraints.
Related:
How to Write Alt Text for Government Images, Charts, and Maps
How to Audit Your CMS for Accessibility
How to Train Your Government Staff on Accessibility
FAQ: Government Website Accessibility on a Limited Budget
What is the single most important accessibility action a small government agency can take with no budget?
Publishing an accurate accessibility statement with a working complaint contact is the highest-value, lowest-cost accessibility action available. It takes a few hours, costs nothing, creates documented public commitment, opens a complaint intake channel, and signals active engagement with the obligation. An agency with an honest accessibility statement and a responsive complaint process is in a meaningfully better compliance position than one that has done more technical work but has no public documentation of its efforts.
What free tools can government agencies use to assess their accessibility?
The most reliable free tools for government web team self-assessment are the axe DevTools browser extension for automated WCAG scanning, the WAVE browser extension for visual evaluation of page structure and contrast, the WebAIM Contrast Checker for evaluating color combinations, and NVDA (free download from nvaccess.org) for screen reader testing on Windows. VoiceOver is built into macOS and iOS at no additional cost. These tools collectively allow a web manager to identify the most common and impactful accessibility failures without any budget investment.
Is it acceptable to have a partially conformant website under ADA Title II?
ADA Title II evaluates whether agencies have documented, ongoing compliance programs — not whether every page achieves perfect WCAG 2.1 AA conformance simultaneously. An agency that has assessed its compliance posture, documented specific limitations honestly in an accessibility statement, established a risk-based remediation program, and is making documented progress is in a defensible compliance position even with some remaining failures. An agency that has made no assessment, has no documentation, and has made no organized effort is not — regardless of how accessible some individual pages may be.
How should a government agency prioritize accessibility work when it cannot do everything at once?
Prioritize in three layers. First, template-level fixes that resolve failures across the entire site simultaneously — skip navigation, focus indicators, heading structure, color contrast in shared components. These produce the most accessibility improvement per hour of work. Second, transactional workflow accessibility — keyboard navigation and screen reader compatibility in the forms and applications residents use to complete government services. These address the highest-risk barriers for enforcement purposes. Third, high-traffic page content — alt text, heading structure, link text on the pages most residents visit. Everything else follows these priorities on a schedule that reflects available capacity.
How much does it typically cost to make a small government website accessible?
The cost varies significantly based on site complexity, current compliance posture, and whether the agency has internal technical capacity. For a small agency with a simple website and moderate internal capacity, Phase 1 work — baseline audit, template-level fixes, document remediation for Priority 1 documents, and governance setup — typically ranges from a few thousand dollars with internal capacity contribution to ten to twenty thousand dollars with full external support. Ongoing governance retainers for small agency environments are typically in the range of a few hundred to a few thousand dollars per month depending on scope. These numbers are significantly lower than the cost of reactive compliance following an enforcement action.
What should a government agency say to residents while its accessibility program is in progress?
Publish an honest accessibility statement that describes the current conformance status accurately, lists specific known limitations, and explains what the agency is doing to address them. Do not claim full conformance. Do not use boilerplate that does not reflect the actual state of the site. When residents report barriers, respond within 10 business days with a specific response — what was found, what is being done about it, and what alternative means of access are available in the interim. This transparent, responsive approach is the behavioral evidence of good faith that matters in an enforcement context.