limena for higher education, see all use cases

One standard across a federated institution.

Forty departments publish independently, and the obligation still lands centrally. limena gives each faculty its own findings and trend, priced in accommodation requests.

Apply for admissionapply.example.comCan’t be completed
  1. Choose a programmePasses
  2. Personal detailsPasses
  3. TranscriptsBlocked
  4. SubmitNot reached
Barrier identified

Transcript upload field has no label

Applicants using a screen reader can’t tell what the field is for, so they have to ask for an accommodation to apply.

WCAG 3.3.2Assigned to: Admissions web team · Jira
Applicants who need an accommodation to apply480 a year16,000 applications a year × 3% who use assistive technology
VerificationPending: re-tested when the fix ships
Illustrative example, not a real finding.

Accountable for everything, in charge of nothing.

The central web team can’t compel a department to fix anything. The complaint still arrives centrally.

  1. Every unit sees its own position

    Each faculty gets its own workspace and trend, alongside where it sits against the rest.

  2. Fix it once, not per student

    A template fixed once ends a stream of individual accommodations.

  3. Most of the estate is licensed

    Vendor platforms are tested and tracked too, with evidence for the procurement conversation.

What limena ranks first

Ranked by the students it stops.

Three findings from one university, in the order limena puts them.

  1. Application portal: upload has no labelBlocks applicationsBlocker: 480/yr
  2. Course page: lecture video without captionsAccommodation requestMedium
  3. Department site: heading orderContent fix, editorLow
Laws covered
  • ADA Title II
  • Section 504
  • AODA
  • Accessible Canada Act

Start with the application portal.

We’ll run limena on one of your journeys and show you each barrier priced, who owns the fix, and what to do first.