A Practical Guide to Equitable Remote Access

A guide to equitable remote access starts with a plain question: can a patron use this resource from home, on the device they have, at the time they need it, without needing staff help to get past the first screen? If the answer is no for a meaningful share of your community, the resource is available remotely, but access is not yet equitable.

For public libraries, remote access is more than a technical setting. It affects whether a parent can find support after bedtime, whether a job seeker can build a skill between shifts, and whether a newcomer can practice English privately. Stronger families. Confident caregivers. More people able to act on information when it matters.

Start with the barriers, not the platform

Libraries often begin with a vendor list, a renewal calendar, or a request for a new subject area. Those are real constraints. But equity work is clearer when the first step is identifying where patrons get stuck.

A resource may be excellent and still be difficult to use because it requires a library card number that a new resident has not received yet. Another may work well on a desktop but be frustrating on a phone with limited data. A platform may offer valuable content in multiple languages, yet its sign-up instructions exist only in English.

Talk with frontline staff before making assumptions. Ask what patrons say when they need help accessing eResources from home. Review common questions in chat, email, and phone logs. If your library has community engagement staff, ask them what they hear at events and outreach stops. These details show where the access path breaks.

The goal is not to remove every obstacle. Security, licensing terms, and authentication requirements are part of the work. The goal is to make the remaining steps reasonable, clear, and possible for the people you serve.

Build an equitable remote access path

The best path is short. A patron should be able to move from a library webpage or catalog record to useful content with minimal decisions and minimal re-entry of information.

Make authentication understandable

Authentication is often the least visible part of an eResource decision and the most consequential for patrons. A login method may be technically sound but still create confusion. Libraries should test every remote access route as a patron would, especially from a phone and outside library hours.

Use instructions that name exactly what patrons need. If they need a barcode and PIN, say so. If a platform requires a one-time account after library verification, explain why and what happens next. Avoid directions that assume people know terms such as proxy, database, institutional login, or authentication.

It also helps to be consistent. If patrons encounter different credentials and different naming conventions across every service, they will assume they did something wrong. Where your systems allow it, use familiar labels and place help close to the login point.

Design for phones and limited connectivity

Many patrons will first encounter a library eResource on a phone. That is not a secondary use case. For some communities, it is the main one.

Check whether the platform loads reliably on older phones, whether text remains readable when enlarged, and whether key tasks can be completed without downloading a large app. Consider how much video, audio, or repeated loading a typical activity requires. High-bandwidth content can be deeply useful, but it may need a clear note about Wi-Fi, downloads, or shorter alternatives.

Libraries can also support access by offering practical choices. A caregiver may prefer a five-minute video and a printable handout over a 45-minute program. A language learner may need downloadable lessons for offline practice. A job seeker may need to save progress when a connection drops. Content format is part of access.

Treat language and accessibility as core requirements

Translated content is valuable, but navigation, onboarding, and help materials matter too. If a resource serves multilingual households, test the full journey in the languages your community uses most. Can someone understand what the service is for, start using it, and get help if needed?

Accessibility deserves the same attention. Ask vendors direct questions about keyboard navigation, captions, transcripts, screen-reader compatibility, adjustable text, and color contrast. Then test the patron experience yourself when possible. A vendor statement is useful. A real workflow test is better.

Not every platform will meet every need equally well. That is where collection balance matters. One resource may offer exceptional video content but limited language support. Another may be easier to navigate but narrower in scope. The right choice depends on your community priorities and the access supports your library can provide.

Promote the use case, not just the resource

A generic message such as “Try our online resources” rarely gives patrons a reason to act. Equitable promotion tells people what a resource helps them do and when it may be useful.

Libraries use targeted messages to connect services with real moments: preparing for a citizenship interview, helping a child through a hard transition, practicing workplace English, checking a claim before sharing it, or building a résumé. This approach respects patrons' time. It also makes discovery easier for people who do not think of themselves as eResource users.

Use the channels that already reach the intended audience. A resource for caregivers may belong in a new-parent packet, on a family program handout, or in a short message shared by staff at storytime. Workforce content may need a place in job-search appointments, computer lab signage, and outreach with local employment partners.

Keep the message concrete. Name the problem, show the first step, and explain that a library card provides access. If the resource is available in multiple languages or works well on mobile, say that when it is true. These are not minor product features. They can determine whether someone tries it.

Prepare staff for the first five minutes

Staff do not need to become platform experts before they can help patrons begin. They do need enough familiarity to handle the first five minutes well: where to find the resource, what login information is needed, what the first screen looks like, and where to send someone when a problem goes beyond the library's control.

A short internal guide is often more useful than a long training deck. Include the direct access route, a simple description of who the resource may help, common login issues, and a sample patron conversation. Update it when the interface or authentication process changes.

For small and rural teams, designate a regular check-in rather than expecting everyone to track every update. Ten minutes during a staff meeting can surface broken links, confusing messages, and successful patron referrals. Consortium staff can support this work by sharing tested language and troubleshooting patterns across member libraries.

Measure whether access is working

Usage numbers matter, but they do not tell the whole story. A low number may point to weak promotion, a confusing entry point, a mismatch with local needs, or a resource that requires more staff context. A high number may reflect one successful program rather than broad awareness.

Pair platform data with local evidence. Look for questions that come through staff. Track whether a campaign produces new registrations or repeat use. Ask a small number of patrons what they were trying to accomplish and whether they could finish. For resources used in programs, note whether participants return independently afterward.

It is also useful to look for uneven access. Are remote services reaching people in branches with fewer computers? Are multilingual materials being found by the households they were selected for? Do patrons who use accessibility tools report the same ability to complete key tasks? You may not have perfect data, but even a few patterns can guide better decisions.

Make equity part of renewal conversations

When renewal season arrives, bring access evidence into the discussion alongside cost, content quality, and usage. Ask whether the resource reaches a defined need, whether patrons can start without unnecessary friction, and what the library has learned about promotion and support.

This can lead to better decisions than a simple keep-or-cancel choice. Sometimes the answer is to improve the landing page, translate a handout, train staff, or place the resource in a stronger program context. Sometimes a good resource is not the right fit for your current community priorities. Both are useful findings.

Equitable remote access is built through small choices that add up: a clearer login instruction, a mobile test before launch, a staff member who knows where to begin, and a message that reaches someone at the right moment. Keep listening for the point where a patron hesitates. That is often the next place your library can make access more real.