Choosing a Free WordPress Theme for a Government Website
For a public-sector site, accessibility is a legal obligation and the site will outlive the contractor who built it. Both facts rule out almost everything marketed as a government theme.
On a public-sector site, accessibility is a legal duty rather than a quality bar, and the site will outlive the supplier who built it. Those two constraints eliminate most of what gets marketed as a government theme, and they barely feature in any theme demo.
Nothing else about the decision is unusual. The unusual part is that the criteria are almost entirely non-visual.
Accessibility is the specification, not a feature
Public-sector accessibility rules in most jurisdictions point at the same technical standard — the Web Content Accessibility Guidelines, at level AA — and require a published accessibility statement describing where the site falls short and what you are doing about it.
A theme cannot deliver that on its own, but it can make it impossible. Assess candidates against the parts a theme owns:
- Colour contrast in the default palette, including link text, buttons, placeholder text and focus states. Most demos fail on placeholder and muted text; choosing a colour palette covers how to check properly.
- Visible focus indicators that survive the theme's own styling. Tab through the demo. If you lose track of where you are, the theme has removed the outline.
- Keyboard-operable navigation, especially dropdown menus and mobile toggles.
- Heading order that reflects the document, not the visual design — one h1, no jumps from h2 to h4.
- Type that resizes. Set the browser to 200% and see what breaks. Fixed-pixel layouts fall apart.
- A skip link, and landmark regions that a screen reader can jump between.
Filtering the official theme directory by the accessibility-ready tag is the fastest way to a credible shortlist, but treat it as a starting filter. It reviews the theme's own markup, not your content, your PDFs or the plugins you add on top. Accessibility plugins help with monitoring and remediation; they do not make an inaccessible theme compliant, and overlay widgets that promise otherwise are not a defensible position.
Build for the supplier who comes after you
Government sites get re-procured. In three or five years a different agency will win the contract and will bring a different theme. Anything the current theme owns is what the next team has to recreate or lose.
That matters more here than commercially, because much of the content is a public record with retention obligations. Council minutes, planning notices, consultations and press releases cannot simply be dropped because a post type stopped being registered.
| Content | Owned by | Consequence if the theme owns it |
|---|---|---|
| Public notices, consultations | A plugin | Statutory publication dates become unreachable |
| Meetings, agendas, minutes | A plugin | Archives 404 while remaining in the database |
| Departments, services, staff directory | A plugin | Navigation and search break at handover |
| Alert or emergency banner | A plugin or core block | The banner disappears mid-incident |
| Templates and styling | The theme | Correct — this is what a theme is for |
Write that split into the specification before procurement, not after. When the day comes, changing a WordPress theme should be a presentational exercise.
What "free" means here
Free means free of licence cost. It does not reduce the obligations, and it is genuinely the right answer for most public bodies: a maintained free block theme from the official directory gives you templates editable by staff, no vendor to renew with, and a maintenance story tied to WordPress itself rather than to one company's business model.
The themes actively sold as government or municipal themes tend to be multipurpose themes with a civic demo, and they add exactly the lock-in described above. Free avoids the licence-lapse problem entirely, which for a body that budgets annually is a real advantage.
Constraints that catch public-sector sites specifically
No external asset calls. Themes that pull fonts, icon sets or scripts from a third-party network send visitor IP addresses to an organisation nobody procured. Self-host everything — choosing fonts for a website covers doing that without losing typographic quality.
Documents are the accessibility problem nobody budgets for. Most public-sector sites publish far more content as PDFs than as web pages, and a scanned PDF is inaccessible no matter how good the theme is. Prefer HTML pages; where a document is unavoidable, it needs real text and structure.
Plain language and search. Residents search for "bin collection", not "waste management services". The theme's search template and its results layout matter more than its homepage.
Security and update discipline. Public sites are targets and are expected to be patched promptly. Fewer plugins, from maintained sources, on a supported PHP version — the baseline is in the WordPress security checklist.
How to run the choice
Shortlist three accessibility-ready themes, load your own real content — including the longest committee agenda you have — and put each in front of a screen reader and a keyboard-only user before anyone looks at the homepage. The theme that survives that is the one to procure around.
Frequently asked
- No. The WordPress directory's accessibility-ready tag is a review of the theme's own markup and default styles, not of your content, your documents or your plugins. It is a sensible filter for a shortlist and no substitute for an audit of the finished site.
- Every external request sends visitor data, including IP addresses, to a third party you have not procured. Public bodies are held to a higher standard on that than commercial sites, and self-hosting the assets removes the question entirely.
- No — they need dates, categories, attached documents and predictable archives, which means a custom post type from a plugin. Registering it in the theme guarantees the archive breaks the next time the site is re-procured and redesigned.