Oogle

counties, municipalities, districts and public agencies

Public information everybody can actually reach.

A public sector website has an unusually wide audience and very little tolerance for failure. Accessibility, clarity and maintainability matter more than anything visual.

WHAT WE DON'T CLAIM

We hold no government procurement certifications, no security clearances and no contract vehicles. If your procurement requires any of those, it's worth establishing that early.

What a public sector site has to do.

The audience is everybody, which changes nearly every decision.

Make required information findable

Meetings, notices, minutes, budgets, permits, forms, contacts.

Be usable by the whole public

Screen readers, keyboard navigation, magnification, translation, old devices.

Say something urgent quickly

Weather, outages, closures and emergencies, without calling a developer.

Work for staff who aren't web people

If publishing is hard, it either doesn't happen or it happens badly.

Stay accurate over years

Stale official information is worse than none.

Most of it's governance, not technology.

Information trapped in PDFs

The most common accessibility failure in the sector.

Structure that mirrors the org chart

The public doesn't know which department handles their question, and shouldn't have to.

Content nobody owns

Pages published by a department that has since reorganized, with no review date and no owner.

What public bodies ask.

Do you have a contract vehicle or certifications?

No. We aren't going to imply otherwise. If your procurement requires a specific vehicle, registration or certification we may not be eligible, and it's better for both of us to establish that in the first conversation.

Can you make our existing site accessible?

Usually a large part of it. How much depends on how it was built. Some accessibility problems are template fixes. Some are structural and are cheaper to solve in a rebuild. An audit tells you which you have before you commit to either.

Should we stay on Drupal?

Often yes, particularly where structured content, permissions and editorial workflow are doing real work. Sometimes the site has become a simple brochure carried by a complex platform, in which case moving is reasonable. We have no commercial preference between those answers.

Public website that needs work?

Tell us what it runs on and where the accessibility position honestly stands. Those two answers shape everything else.