limena for healthcare, see all use cases

Care that doesn’t depend on being able to use a mouse.

The person blocked by your patient portal is often the person least able to work around it. limena ranks barriers by what a person can’t complete, starting with refills and bookings.

Book an appointmentpatients.example.comCan’t be completed
  1. Choose a clinicPasses
  2. Pick a timeBlocked
  3. Your detailsNot reached
  4. ConfirmNot reached
Barrier identified

Time slots aren’t announced to screen readers

Patients using a screen reader can’t tell which times are free, so they call the front desk instead of booking.

WCAG 4.1.2Assigned to: Frontend · Jira
Bookings moved to the phone1,100 a year44,000 online bookings a year × 2.5% who use a screen reader
VerificationPending: re-tested when the fix ships
Illustrative example, not a real finding.

Your users are having their worst week.

Nobody arrives at a patient portal casually. They are unwell, anxious, on a phone in a waiting room, or acting for someone who can’t.

  1. Clinical consequence comes first

    A blocked prescription refill outranks a contrast issue on a health article.

  2. Failed bookings land on the front desk

    Each one is priced at your cost per assisted contact.

  3. Letters and labelling count too

    Results letters and patient documents are read page by page.

What limena ranks first

Ranked by the care it delays.

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

  1. Refill: submit button has no nameBlocks a prescriptionBlocker: High
  2. Booking: time slots not announcedMoved to the phone1,100/yr
  3. Health article: low contrastContent fix, editorLow
Laws covered
  • ADA Title II and III
  • Section 508
  • AODA
  • Accessible Canada Act

Start with appointment booking.

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