Public libraries · Website fixes

A library website patrons can use with a keyboard and a screen reader.

A county library system had an audit that found 64 barriers on its website. Its small web team could not fix them all before the ADA Title II deadline, so we fixed them alongside the team and retested each one by hand.

Client
A county library system
Type
Website fixes
Scope
64 barriers across 3 key tasks
Result
All 64 fixed and retested

Context and goals

Patrons use the website to search the catalog, place holds, sign up for events, and apply for a library card. Many use the computers in a branch, and some use a screen reader or a magnifier.

The library wanted every task to work for every patron, and proof that the work was done.

What success looks like

  • A patron can search, place a hold, sign up for an event, and apply for a card with a keyboard alone.
  • Every form field has a label, and every error says what to fix.
  • Text and buttons have enough contrast to read on a bright branch screen.

What we measured

We started from the audit’s list of 64 barriers, confirmed each one by hand, and grouped them by the task each one blocked.

Barriers fixed, by task

  • Apply for a card22
  • Sign up for events19
  • Menus and pages site-wide14
  • Search and holds9

All 64 were fixed and retested by hand in six weeks.

A sample of the fixes
BarrierTaskFixStatus
14 fields with no labelsApply for a cardLabels and clear errorsFixed
Calendar needed a mouseSign up for eventsKeyboard access and a list viewFixed
Low-contrast buttonsEvery pageDarker button colorsFixed
Hover-only menusEvery pageMenus that open by keyboardFixed
Hold button with no nameSearch and holdsA name screen readers announceFixed

What we found

  • The good news: the catalog vendor had already fixed its own search screens, so most barriers were on pages the library controls.
  • The event calendar could not be used with a keyboard.
  • The card application had 14 fields with no labels.
  • Light gray text on buttons failed the contrast check across the site.
  • Menus opened only on hover, so keyboard users could not reach them.

Hear the difference

A patron who uses a screen reader applies for a library card.

Before

What a screen reader says

  1. “Edit text.”
  2. “Edit text.”
  3. Fourteen fields in a row with no names, so the patron has to guess what each one asks for.

After

What a screen reader says

  1. “First name, edit text, required.”
  2. “Date of birth, edit text, required. Use the format month, day, year.”

The path to good

  • We fixed the barriers in the order that unblocked the most patrons, starting with the card application.
  • We worked in the library’s own website tools, alongside its web team, and showed them how each fix works.
  • We retested every fix by hand with a keyboard and a screen reader before we called it done.

Follow-up

All 64 barriers were fixed and retested in six weeks. The web team now checks new pages with the same steps before they go live.

All case studies are samples. Each is based on our past work or on our audits of publicly available websites, documents, and social media. Names and details have been changed to protect privacy.

Before you buy

We start with a free light audit.

We prepare it for you and send you what we find.

  • We check your homepageKeyboard, screen reader, contrast, and zoom.
  • We review one public documentTags, headings, image descriptions, and language.
  • We fix one public document freeYou get it back fixed, with a before and after.
  • We send you what we findA short written summary you can share with your team.

Start the conversation

No cost and no obligation. We only look at public pages, and we keep your results only as long as the follow-up needs them. You’ll also get occasional deadline updates, and you can unsubscribe anytime.