Colleges & Universities
Coordinating accessibility across hundreds of department sites, an LMS, and course content nobody centrally controls.
Nobody owns the whole publishing surface — that's the actual problem.
Higher education has the hardest version of this problem: decentralized publishing, a learning management system full of faculty-uploaded content, third-party courseware, and a public website that is really a few hundred loosely governed sites. Public institutions are covered by ADA Title II; private ones are reached through Title III and, if they take federal funds, Section 504.
What's at stake: Accessibility complaints in higher ed tend to arrive through students with documented needs and end in resolution agreements with deadlines and reporting requirements. Getting ahead of that is dramatically cheaper than being placed under one.
This is you if
- Each department or college runs its own site with its own publishing habits
- Course materials — PDFs, slide decks, recorded lectures without captions — live in the LMS unreviewed
- Procurement buys courseware and platforms without asking for a VPAT
- Disability services fields accessibility complaints that web and IT never hear about
What we actually do, in order.
Map who publishes what
An honest picture of the publishing surface — central web, department sites, LMS, third-party platforms — and who is accountable for each.
Baseline the highest-traffic paths
Admissions, registration, financial aid, and the LMS shell get audited first. These are the paths where a barrier blocks enrollment or coursework.
Build a policy with teeth
A written accessibility policy naming the standard (WCAG 2.1 AA), covering procurement, and assigning ownership — not an aspirational statement.
Train the long tail
Role-specific training for faculty and department content owners: headings, alt text, captioning, and accessible documents. Most of the long-tail fixes are authoring habits, not code.
Close the complaint loop
A single intake path that routes accessibility issues from disability services to whoever can actually fix them, with a tracked response time.
Deliverables, not a status update.
- A defensible institutional accessibility policy and standard
- Audited, remediated core student-journey paths
- Faculty and staff who can author accessible content without help
- A functioning complaint and escalation process
Services this draws on
Industry context: Education
Other situations we're brought in for.
Healthcare Patient Portals
Scheduling, intake, and patient portals that work for the patients most likely to need them.
Read the use caseE-Commerce & Retail
Making the path from product page to confirmed order work for every shopper — and closing the highest-litigation-risk gaps.
Read the use caseSaaS Vendors in Procurement Review
Producing a defensible VPAT and closing the gaps it exposes — before accessibility stalls the deal.
Read the use case