For government & public-sector bodies
Your website is the front door for people who need help.
Someone reaches a public agency’s website on a hard day — looking for a service, a form, a phone number, often on an old phone, sometimes using a screen reader. If the page fails, the agency wears it, and the person doesn’t get help.
LFW manages public-sector websites from Arlington, Virginia — with the accessibility discipline, the security posture, and the procurement patience the work actually takes.
Section 508 as a deliverable, not a hope
For a public body, accessibility isn’t a nicety — it’s an obligation, and often a contract term. We audit against WCAG 2.2 AA continuously, automated engine plus manual keyboard and screen-reader passes, and remediate as part of the engagement — or start with a standalone audit.
We work the way you have to buy
Public bodies purchase on their own terms — a purchase card under the micro-purchase threshold, a simplified acquisition, or a solicitation posted on eVA. We meet you on your paper: your terms and conditions, your order form, your fiscal-year and non-appropriation clauses. No pressure to adopt a vendor’s agreement you can’t sign.
Security and records, for sensitive services
People’s association with a public service can itself be sensitive. We run tested backups, monitored patching, least-privilege access, and TLS — on infrastructure we operate, with no third-party trackers anywhere on your pages.
Continuity of operations, in writing
You own the site, the domain, and the records outright, and a written handover procedure is part of the engagement itself — not a courtesy negotiated at the end. Ordinary professional practice for public work, documented from day one.
- Hosting
- Maintenance
- Security
- Content
- Accessibility
- Search visibility
- Governance
The full scope a website-management solicitation names — under one engagement, one point of accountability.
Whatever it runs on. In the federal website notices we track, when a solicitation names a content management system at all, it is far more often Drupal than anything else — a cabinet department’s digital-communications contract, an independent agency’s hosting task order, an accessibility RFI that lists it as the primary CMS. State and local bodies run both, with WordPress more common at smaller agencies. The work here sits above that choice: accessibility, performance, links, TLS, and email deliverability are measured against what your site serves a real visitor, not against its admin screen. Rebuilds and migrations are delivered on WordPress, Drupal, or a static build.
The Department of Justice’s rule under ADA Title II sets hard dates for WCAG 2.1 AA conformance:
We already audit to the newer WCAG 2.2 AA — which includes the rule’s 2.1 criteria. Monitor checks every page daily against the automatable criteria, and manual keyboard and screen-reader passes cover what no scanner can — so where you stand is something you can show, not assert. Our own numbers, live:
Monitor’s own scan of this website, August 10, 2026. Methodology
Pennsylvania Avenue, Washington, D.C. A record your agency holds, not one it has to request.
Every request, change, and decision is kept as a running record with reference numbers — and all of it exports in one click, in open formats.
When someone asks your agency what changed and when, the answer is a report you already hold.
A written handover procedure comes with the work — under your order form and terms, or under our own agreement, published in full.
Put your public site under management.
Start with the free audit of your site, or book a call — twenty minutes, no sales pressure, an honest read on fit.
A capability statement is available — read it here or request a copy at [email protected].