Seeing everything is the start, not the finish
Large public institutions often reach the same moment. Discovery often finds far more sites than anyone expected. The view is useful. It is also overwhelming. Who decides which sites to retire? Who fixes the shared themes and components? Who builds the replacements?
That is the line between a governance platform and an implementer. One shows you the estate. The other helps you act on it.
What a governance platform does
A web governance platform sits above your CMSs. It inventories sites, tracks ownership and platform, and monitors health signals such as accessibility, performance, and security across the estate. Accorbis is one such platform. It is standalone software, not exclusive to KWALL. Other agencies can sell it, and KWALL implements it.
For product details and demos, the source is the Accorbis product site.
What the implementer adds
Setup that fits your organization
Mapping owners, groups, and policies to how your colleges, agencies, or business units actually work.
Decisions on each site
Retire, merge, fix in place, or rebuild, with the owners in the room.
Remediation
Theme, component, content, and document fixes on the sites that stay. A dashboard score is a signal; the fixes are engineering and editorial work.
Custom organization kits
Starting sites built to your brand and standards so new requests do not go around the web team. These take real setup and are scoped as implementation work.
Ongoing operation
Monthly review and fix cycles so the estate stays in shape after the first push.
Why the order matters under Title II
On April 20, 2026, the Department of Justice extended the Title II web and mobile app compliance dates. State and local government entities with a total population of 50,000 or more now have until April 26, 2027. Entities under 50,000, and every special district government, now have until April 26, 2028. The technical standard did not change: WCAG 2.1 Level AA. Source: the DOJ interim final rule extending the Title II compliance dates (91 FR 20902).
A plan built on a partial inventory spends money on the sites you know while the unseen ones carry the risk. Visibility first, then triage, then remediation, is the order that holds up when someone asks how you decided.
Keep the roles clear
Buyers should know what they are paying for. The platform is a subscription. Implementation is services work written into a separate scope. Hosting, if any, is its own decision. Mixing them in one line item makes it hard to compare options or change partners later.
A hypothetical: the first ninety days
Imagine a state university system that subscribes to a governance platform. Discovery finds many more sites than its inventory listed. Without an implementer, the web team has a long list and no capacity. With one, the first ninety days might look like this:
- Weeks one to three: map sites to colleges and owners, set up groups and policies, and agree retire-or-keep criteria with leadership.
- Weeks four to eight: owners make decisions on each site; retirements and redirects start; high-traffic sites get a manual audit.
- Weeks nine to twelve: shared component fixes begin, editor training is scheduled, and a monthly review cycle starts.
The platform made the work visible. The implementer helped the institution act on it.
Questions to ask before choosing an implementer
- Have they implemented the platform you chose, and can they show how?
- Do they do remediation work themselves, or only setup?
- How do they run retire-or-keep decisions with site owners?
- Who builds custom organization kits, and how is that scoped?
- What does ongoing support look like after the first push?
Signs you may not need one yet
If your estate is small, your owners are known, and your team has capacity to fix what the dashboard shows, start on the platform alone. Bring in services when the list outgrows the team.
Keep the scopes separate on paper
When you buy, ask for three things to be written separately: the platform subscription, the implementation scope, and hosting, if any. Each should name what it includes and what it does not. That makes it clear who is responsible for what, and it lets you compare partners on the services they actually provide.
Frequently asked questions
Do we need a platform to govern our sites?
Not always. Small estates can manage with a maintained inventory. Large, distributed estates usually benefit from one.
Is Accorbis exclusive to KWALL?
No. Accorbis is standalone software. KWALL implements it, and other agencies can sell it too.
Does a governance dashboard replace our CMS?
No. Sites stay on the platforms they run on today.
Can we use the platform without an implementer?
Yes. You can start on the dashboard alone and bring in services when you are ready to act on what you see.
Can we change implementers later?
Yes. Keeping the platform subscription separate from the services scope makes that easier.
Who decides which sites to retire, the platform or the implementer?
Neither. Your site owners and leadership decide. The platform shows the facts, and the implementer helps run the process.
Does the implementer need to host our sites?
No. Hosting is its own decision, separate from both the platform and the implementation work.
What should the first implementation milestone be?
Owners mapped to every site and agreed criteria for retiring, fixing, or rebuilding. Everything else builds on that.
Next step
Read how KWALL implements Accorbis, or if you are planning remediation across a large estate, tell us what you are working on.
