LFW

For colleges & universities

Hundreds of editors. One accessible website.

A campus website is edited by people in dozens of departments who do not report to the web team. It still has to meet WCAG 2.1 AA, stay patched, and carry a prospective student from a program page to an application.

LFW hosts, maintains, and monitors college and university sites on WordPress. Department editors work inside tested templates, and one monthly report serves both your CIO and your accessibility office.

Request a quote Book a call

Interactive example

An approval you can trace.

Review a change, complete its checklist, and move it to Ready.

Publishing desk
Review the change

Program page

Current version

Deadline: see the PDF.

Proposed version

Application deadline: March 1, stated on the page.

Before approval

3 checks remaining

Sample content. Changes stay in this browser.

30-minute tasks

Routine management, one task at a time.

1 day / 4 hours

Standard / Priority acknowledgment during business hours.

Fixed project quotes

Rebuilds, integrations, and larger work scoped separately.

Who handles what

Distributed editing, clear ownership.

For campus web, marketing, and IT teams responsible for a site that many departments edit.

Your departments
Program facts, faculty and staff listings, office hours, forms, and the words on their own pages.
Your central web team
Brand, templates, navigation, the homepage, emergency messaging, and who may publish what.
LFW
Hosting, updates, security, daily accessibility monitoring, the monthly report, and routine changes. Admissions, student records, and learning systems stay with their vendors; the website links to them.

From request to delivery

Give every page an owner before you redesign anything.

In September 2026 LFW checked the homepages of four public colleges. Three had critical accessibility failures, and scores ran from 35 to 97 out of 100. The fix starts with templates and ownership, before any redesign.

  1. Host and patch the platform

    Managed hosting for WordPress with staging, daily backups, a firewall, and single sign-on through the campus identity system. Updates run monthly through staging, with security releases sooner. Recovery is tested every year, and the result is written down.

  2. Make accessibility a monthly number

    Templates are built and tested to WCAG 2.1 AA once. After that every page is scanned daily, findings are listed by page and department, and template failures are fixed at no charge. Content failures go to the editor who owns the page, with instructions.

  3. Keep editors inside the system

    Department editors build pages from approved sections, so a new page is on-brand and accessible without a developer. An image without a description cannot be published, and a PDF uploaded without tags is flagged at the moment of upload.

What the monthly fee covers

Routine tasks of 30 minutes or less, handled one at a time. Standard acknowledgment: one business day. Priority acknowledgment: four business hours. These are response targets; completion depends on the work.

Business hours only, with no after-hours or on-call coverage. Hosting and licenses are paid separately. Redesigns, integrations, custom development, and larger remediation work receive a separate fixed quote.

Read management scope and terms

Before you engage

What campuses ask first.

Do we have to leave our current platform?

No. If your sites already run on WordPress, LFW takes over maintenance where they are or moves them to managed hosting. Leaving a proprietary campus CMS is a rebuild, with its own scope, schedule, and fixed quote.

Can you provide a VPAT?

Yes. LFW delivers an Accessibility Conformance Report on the current VPAT template for the templates it builds, prepared from the written test record and refreshed after each annual assessment. LFW holds no accessibility certification, and the report says so.

What about penetration testing and security questionnaires?

An independent firm tests the site once a year. LFW scopes the test, fixes what it finds, and reports the result. For a HECVAT or a similar questionnaire, LFW answers for its own practices and supplies the hosting provider’s SOC 2 report for the infrastructure.

How does an emergency alert reach the website?

The site reads your campus alert system’s feed and shows a banner on every page while an alert is active. It is tested with your team at launch and each term, and an administrator can override it.

For public institutions

The accessibility rule covers public colleges.

Relevant experience

Experience with many sites and many editors.

At Stand Together, Leland worked on the in-house team responsible for more than 100 sites running WordPress, including a network of state-chapter sites with shared templates and editors who were not developers. He also administered Arlington County Government’s network of more than 40 public sites. Both roles preceded LFW.

These are roles Leland held before founding LFW. The organizations named here are former employers, not LFW client references.

Read Leland’s professional history
The work leaves a record. Enlarge screenshot
A real view of the LFW demo service report

Enlarge to view the full screenshot.

A real view of the LFW demo service report Read the sample service report

Bring the page your editors break most often.

Show us the template, the accessibility report, or the RFP you are writing. We can say which parts belong in ongoing management and which need a defined project.

    Powered by LFW Search
    Prefer to write?

    Tell us what needs to work better.

    Slow, fragile, hard to edit, missing a workflow. Say it plainly, and you'll get a straight answer, not a ticket number.