Library Website Design: Public Library and Academic Library Websites Built Around Patrons, Staff and Accessibility

Updated October 2026 · Written and maintained by the Progression Agency strategy team

Library website design starts with what patrons come to do: find a book or a database, renew, register for a program, book a room, get a card, check the hours. A good library site puts those tasks first, connects cleanly to the catalog and events tools the library already runs, meets WCAG 2.1 AA, and lets staff keep it current without a developer. We design and build library websites on WordPress and Drupal for public library systems, college and university libraries and library foundations, working remotely from New York, with fixed starting prices published below.

What does library website design involve?

Library website design is the work of planning, designing and building a site around the tasks patrons carry out, then giving staff the tools to keep it accurate. It covers structure, templates, accessibility, connections to the catalog and events tools, and the launch. Library web design differs from most institutional work because the site mostly points people toward systems that live somewhere else: a catalog, a booking tool, a calendar, a database vendor.

Library web design compared with a city or school site

A library has patrons rather than residents or students, a catalog that sits beside the website, and programs and rooms that people reserve. A city site is organized by department and a school site by division and calendar. A library site is organized by task. If the library is part of a municipality, our government website design page covers the wider municipal site, and our school website design page covers districts and campuses.

Who we build library websites for

We work with public library systems and branches, library districts, academic libraries at colleges and universities, special libraries such as law, medical and corporate collections, and the friends and foundations that raise money for them; the foundation side connects to our nonprofit website design work. Our clients on a project like this are adults and institutions: directors, boards, communications staff and library leaders.

What a library website design company hands over at the end

A good vendor should leave you with a live site on hosting in the library’s name, the source files on final payment, redirects from the old addresses, an accessibility test record, trained editors, a recorded training library and a list of page owners with review dates. That list matches what we deliver on any public-sector build, and none of it depends on keeping us under contract.

What is a library website?

A library website is the library’s public front door online: it explains what the library offers, where and when, and sends patrons to the tools that do the work. It is a service as much as a brochure, and the way to judge it is whether a person finished what they came to do.

The front door to the catalog, programs and spaces

The website is not the catalog. The catalog holds the collection and each patron’s account, while the website routes people there and explains everything around it: cards, programs, rooms, policies, hours and help. Designing the handoff between the two is a large part of the job, because patrons rarely know, or care, which system they are using.

What should a public library website include?

Start from the tasks. The table lists the pages a public library site should carry and what each page has to show, so you can compare it with your current menu.

What staff and boards need from the same site

The same site carries governance material. Boards need agendas, minutes, policies, annual reports and budgets that are easy to find and dated. Job seekers need current openings. Journalists and funders look for a contact and a plain statement of what the library does. Keep this material in its own section so it never competes with the patron menu.

Designing a library website around patron tasks

Designing a library website around patron tasks means every top-level menu label answers a verb: borrow, find, attend, book, join, ask. Gather the tasks first, rank them by how often people do them, and let that ranking decide what the homepage shows and what moves lower down.

Find a book, an ebook or a database in one step

Give the search box a visible label that says what it searches. If the box searches the catalog, say catalog. Place a short list of the most used databases beneath it and link to an A to Z page for the rest. A page of bare vendor logos leaves patrons guessing, so describe each database in a sentence and say who may use it.

Account, renewals and holds

Account links should say where they lead and what opens next, for example that the catalog opens in a new window. Add a line for patrons who cannot sign in, with a phone number and a form. This small piece of copy can cut desk calls more than a flashier feature.

Programs, room booking and card signup

Each of these deserves a task page rather than a mention on a list. The program page holds the calendar tool or a link to it, the room page holds the rules beside the booking tool, and the card page holds the form with the ID rules above it. Keep the three consistent in layout so patrons learn the pattern once.

Testing the tasks with patrons before design

Run a five-task usability test with a handful of patrons and staff, and a tree test of the proposed menu with the same tasks. In library website usability testing, a missed task tells you more than a satisfied comment, because it shows the label or the path that failed. Fix the structure on paper before anyone draws a screen.

Library homepage design: a task menu before the news

Library homepage design works best when the first screen is a task menu, today’s hours and one featured program, with news and events below. A patron who opens the site on a phone in the lobby wants the hours, the catalog or a room, not a banner.

The first screen

On the first screen place the search box, today’s hours for the nearest or chosen branch, the four most used tasks as plain buttons, and one featured program. A rotating carousel hides most of that, because the second slide is easy to miss. One strong, current feature does more.

Hours and locations without hunting

Show today’s hours in text for each branch, flag closures and holiday changes in the same place, and give each branch its own address, phone number, parking and transit note. Hours that live in an image or a PDF cannot be read by a screen reader, a search engine or an assistant.

Events and news below the tasks

Below the tasks, add a filtered events strip, with filters for audience, branch and date, and a short news area. Archive news by month so the homepage never shows a headline from last year. The events strip should read from the same calendar the program pages use.

Public library website design for systems and branches

A public library site has to serve a main library and its branches with one coherent site, and to keep every branch’s facts current without a developer. Public library web design succeeds when branch staff can update their page and the system can still hold the standard.

Branch pages that stay accurate

Use one branch template with the same fields on every page: address, hours, services, staff contacts, meeting rooms and accessibility notes. Assign an owner to each branch page, and where the library can, feed hours from a single source so the homepage, the branch page and the map all agree.

Multilingual pages for the languages patrons speak

Translate the task pages first: card signup, hours, programs, help. A translated menu that leads to an English-only form fails the patron at the last step. Our multilingual website design page explains how we structure language versions so each is written natively and indexed correctly.

Library districts and municipal libraries

A library district and a library that is a city department are governed differently, and that changes who approves the site and which public rules apply to it; the accessibility section below explains why legal form matters. For the municipal side, see our government website design and government marketing agency pages.

Academic library website design for colleges and universities

Academic libraries serve students, faculty and researchers who arrive with a research task, so the site leads with search, subject guides and a way to ask a librarian. An academic library website also has to sit inside the university’s brand and content system.

Research guides, databases and subject librarians

Organize guides by subject and by course, give the database finder filters for subject and format, and name the subject librarian on each guide with a way to book a consultation. Link from every database description to the guide that explains how to use it.

Off-campus access and sign-in, explained in plain words

Many academic resources need a sign-in away from campus. Explain the path in a few short steps with one link, say what to do when it fails, and show who to contact. We describe the sign-in path in general terms on the site and do not tie the design to any one authentication product.

Fitting the university’s brand and CMS

The library usually inherits the university’s colors, type and navigation, and sometimes its content system. We build a component set that the campus and the library share, then add library templates on top. For the campus-wide view, see our higher education website design page.

Catalog, discovery and events: what a library website connects to

A library website connects to three kinds of outside tools: the catalog, a discovery layer that searches many sources, and the events and booking tools. Library catalog integration is usually a matter of choosing a pattern, not writing new software, and the right pattern depends on who runs the tool and how much control the vendor allows.

The catalog and discovery layer: link, embed or search box

There are three common patterns, shown in the table. We name them as categories because the choice turns on your tools and your vendor’s options; we confirm what a given product supports during the written scope rather than promising a connection in advance.

Events, program registration and room booking

Embed or link the library’s existing calendar tool, and style the page around it so it looks like part of the site. Check the embed with a keyboard, a screen reader and a phone before launch, since an embedded calendar is where accessibility and layout problems often hide. A library event calendar that lists each event as plain text with a date also reads well to search engines and assistants.

Digital collections and e-resources

Ebooks, audiobooks, streaming media and research databases usually come from outside vendors. On the website, describe each as a category, say who may use it and how to get started, and link to the vendor’s sign-in. We keep brand names out of the design logic so a change of vendor means a text edit, not a rebuild.

Online library card applications

A card application should ask only for what the library needs, show the ID rules the library sets, and say what happens after submission. Add a short privacy note that names what is kept and for how long, using the library’s own retention rules.

Library website search and navigation

Library website search and navigation come down to two choices: how many search boxes a patron sees, and what the menu labels say. Keep both plain, and test them with people who do not work in a library.

One search box or two?

Some libraries run a single box that searches the site and the catalog together, others keep two. Either can work if each box is labeled and results are scoped, with a small link such as search the whole site under the catalog results. A single unlabeled box that sends everything to the catalog frustrates anyone looking for hours.

Menu labels patrons recognize

Prefer Borrow, Events, Visit and Research to library shorthand such as OPAC or ILL. When jargon is unavoidable, explain it once in plain words on the page where it first appears. Test the labels with a tree test and change any that more than a few patrons miss.

Breadcrumbs and a next step on every page

Show a breadcrumb trail so patrons can step back, and end each page with the next likely action: register, book, renew or ask. A page that ends without a next step sends people back to the menu to start over.

Library website best practices

Library website best practices are habits that keep a site useful after launch: plain language, dated pages, regular review and a mobile layout that is tested. None needs special technology; all need an owner.

Plain language and a stated reading level

Federal plain language guidance, published by digital.gov, starts from writing for the specific audience that will read the page. For a library that audience is broad, so use short sentences, task verbs and everyday words, and decide on a reading level you will hold every editor to.

Show when each page was last checked

Add a visible last reviewed date and a named owner to each page. Patrons trust a page that says it was checked this month, and staff get a built-in prompt to check it. We deliver a list of page owners with review dates at the end of every public-sector build.

How often should library website content be updated?

Hours, closures and events need attention daily or weekly. Policies, card rules and fees deserve a check at least once a year, and every page should be reviewed at least yearly even if nothing changed. Put the review dates in a list that someone reads each quarter.

Mobile first, because patrons check hours on a phone

Design the small screen first: tasks at the top, hours in text, tap targets large enough to hit, tables that scroll inside their own box. Library website mobile layouts fail most often in embedded calendars and catalog panels, so test those on a real phone before launch.

Library website accessibility: WCAG 2.1 AA, documents and the Title II rule

Library website accessibility means patrons who use screen readers, keyboards, magnification or voice control can finish the same tasks as anyone else. For a library tied to a state or local government, the ADA Title II web rule makes WCAG 2.1 Level AA the standard. Library website ADA compliance and library website WCAG work are the same project.

What the Title II web rule requires, and when

The rule requires state and local government web content and mobile apps to meet WCAG 2.1 Level AA. Public entities with a population of 50,000 or more must comply by April 26, 2027, and smaller ones and special district governments by April 26, 2028, after an interim final rule in April 2026. The ADA.gov web rule page says population comes from 2020 Census data, not from the number of patrons served. Whether a particular library is covered depends on its legal form, so ask your counsel; this page is general information, not legal advice.

PDFs, newsletters and event flyers

Libraries publish a lot of documents. The rule has five exceptions, including archived content and preexisting conventional documents, and ADA.gov notes they have conditions. A document patrons use to get a service does not qualify for the preexisting exception. The practical order is to fix what patrons use, move older material into a true archive, and publish new items as web pages or accessible files.

Catalog and vendor tools are part of the patron’s experience

The embed in your page is a part of your page. Test each vendor widget, and ask vendors for an accessibility conformance report; Section 508 describes an Accessibility Conformance Report as a document that explains how a product meets the Revised 508 Standards. The ADA.gov guidance is blunt that a public entity cannot contract away its duties, a point our government website design page expands on.

Testing, not overlays

An overlay is a script added on top of a site that promises to fix accessibility; it does not change the underlying pages. We do not install them, for the reasons on our ADA compliant website design page. We build and test to WCAG 2.2 AA, and per the WCAG 2.2 text content that conforms to 2.2 also conforms to 2.1, which is the level the rule names.

Patron privacy on the library website

Library patron records are protected by state law almost everywhere, and a website can undo that protection by leaking search or account activity to an advertising or analytics tool. Design for the smallest amount of data that still lets you improve the site.

State library confidentiality laws

The American Library Association reports that 48 states and the District of Columbia have laws protecting the confidentiality of library records, and that Kentucky and Hawaii rely on attorney general opinions. Statutes differ on what they cover and how a court order works, so read your own state’s text and ask counsel; we do not give legal advice.

Analytics, embeds and third-party scripts

Collect the minimum, keep advertising pixels off account, search and card pages, and review every embed for what it sends back to its owner. Add a consent banner only where a rule requires one. A script added for a single campaign tends to stay for years, so list all scripts in the handover.

Card and room forms that collect the minimum

Card applications and room requests should ask for only the fields staff use, show what is retained and for how long, and avoid free-text boxes that invite sensitive details. State retention in the library’s own words, and let staff delete records on the schedule the library sets.

Staff editing, roles and governance

A library website stays accurate when the people closest to the facts can edit them within clear limits. That takes roles, locked templates and a short approval path, not a developer on call.

Can staff edit pages and events without a developer?

Yes. We build templates with fixed layouts so staff edit text, dates and images in a form, not the page structure. Roles decide who can edit what: a branch manager edits the branch page, a program coordinator posts events, and a communications lead publishes news and policies.

Who approves what

Use three steps: draft, review, publish. Routine edits can go straight through for trusted editors, while policy and fee changes wait for a second reader. Emergency closures need a fast path with one person empowered to publish at any hour.

Recorded training and written page standards

We provide recorded training for editors so new hires can learn the same way the first cohort did. Pair it with a short page standard that covers headings, link text, image descriptions and dates. The standard keeps twenty editors sounding like one library.

Library website platforms: WordPress, Drupal and hosted vendor sites

The choice of platform follows the library’s size, its editors and its integrations. Most libraries do well on WordPress, large systems and universities sometimes need Drupal, and a hosted vendor site suits a very small library that wants little to manage. Library website WordPress builds and library CMS choices are mostly about who edits and who maintains.

WordPress for most public libraries

We build custom block themes that library staff can edit without touching code, with templates for branches, events and programs. If that is the route, see our WordPress development company page. A ready-made library WordPress theme can serve a small branch well; a system with many templates usually outgrows one.

Drupal for large systems and universities

Drupal fits when content types, permissions and languages grow complicated, which is common in a large system or a university library. We build new Drupal 11 sites and migrate existing ones; see our Drupal development company page for the detail.

Library website templates and hosted vendor platforms versus a custom build

Library website templates and hosted platforms are fair choices for a small library with few pages and no integrations. A custom build earns its cost when tasks, branches or languages multiply. The table sets out the trade.

Library website redesign: inventory, redirects and launch

A library website redesign succeeds when the library knows what it has, decides what to keep and moves every address that matters. The visible design is the last stage, not the first.

Do we need a new website or a redesign of what we have?

If the structure works and the site only looks dated, a restyle in place changes type, color and imagery on your existing structure and carries little ranking risk. If patrons cannot finish tasks, the structure has to change. Our website redesign services page explains how we decide.

Content inventory and the redirect map

List every page and file, then mark each keep, merge or retire. Map each old address to the page that replaces it, and test the map on staging before launch. Our website migration services page covers moving content, and the cost of skipping the map is described on traffic dropped after a website redesign.

A library website redesign checklist

The grid below lists what to settle before launch and what to keep checking afterward. Print it, assign each row to a person, and tick it off in the meeting before go-live.

Library website redesign timelines

How long does a library website redesign take? Our fixed-scope table gives three to five weeks for a restyle in place, six to eight for a brochure site, eight to thirteen for a business site and twelve to eighteen for a bilingual one. Content and approvals decide the rest, so set dates for both at the start.

Library website design ideas and examples

These ideas are patterns, not screenshots: arrangements of tasks, hours and events that work across libraries. We describe patterns and do not name individual libraries.

Patterns that work on strong library sites

The strongest examples share a few features: a task bar near the top, today’s hours in text, an events filter, and staff picks that link straight to catalog records. Library website examples worth studying are the ones where you can finish a task without reading the menu.

Seasonal campaigns for adult patrons

Seasonal features give the homepage something current: tax help season, job search help, author talks and local history programs. Plan them on a calendar, build one reusable feature template, and retire each when the season ends.

What not to copy

Avoid carousels as main content, calendars that exist only as a PDF, and a separate mobile site that drifts out of date. Also avoid long paragraphs on the homepage; patrons scan for the task and leave if they cannot find it.

Library website development cost and timeline

Library website development cost depends on the number of templates, branches, languages and integrations, and on how much document work the old site leaves behind. We publish fixed-scope starting prices so you can plan before you ask for a quote.

Our published prices

The table shows our fixed-scope website prices from our published table, each shown as a starting figure. What a library pays inside these tiers depends on the scope the written proposal sets out.

Maintenance is optional at $50 to $250 a month for a small site. See the full table on our website design and development page and the website cost guide.

What moves the cost

Five things move the price: the number of templates and branches, the integrations, the languages, the document remediation backlog, and the editors and workflows involved. A single-branch library with few documents sits near the low end of a tier; a system with many branches and a large archive sits near the high end.

Quotes, RFPs and board approval

Many libraries need board approval or a formal quote process before they can sign. Use your own procurement steps; we supply a written scope and fixed prices that make a board paper easy to write. The municipal side of buying a site is covered on our government website design page.

How AI assistants answer patrons’ library questions

Patrons increasingly ask assistants for library hours, event times and card rules. Assistants answer from pages they can read, so the library’s plain-text pages decide what gets said.

Where assistants get library hours and events

Google says pages must be indexed and eligible to show a snippet to appear in its AI features in Search, and that no extra technical requirements apply. In practice that means hours, locations, events and policies in readable text, not in images or PDFs. We describe the pattern and make no promise that an assistant will name any library.

What a library should publish so answers are right

Publish today’s hours as text, events with dates and places, and card rules in full sentences. Keep one page per branch and one per policy. For related guidance, see our AEO for nonprofits and AEO for colleges pages.

Choosing a library website design company: questions and ownership

The choice comes down to a short list of questions about accessibility, training, integrations and ownership. Ask every vendor the same questions and compare the written answers.

Questions to ask library website vendors

Library website vendors should be able to say which accessibility standard they build to and show a test record, how editors are trained, how they approach catalog and events integrations, who owns the site afterward, and how redirects are handled. Treat a vague answer as an answer.

Who owns the site and content after launch?

The library does. Under our terms you own the domain, the hosting, the content, the design files and the source, all transferred on final payment, and none of it depends on continuing to work with us. The details are on our website design and development page.

Get a free proposal for your library website

Send us the branches, the tools and the languages. We reply with a free proposal and a written scope. We are based in New York, work with clients in all 50 states and worldwide, and run projects remotely.

Related services for libraries and public institutions

These pages cover neighboring work: sites for similar institutions, accessibility, platforms, migrations and the marketing around them.

• Government website design
• Government marketing agency
• School website design
• Higher education website design
• Nonprofit website design
• Membership website design
• Community website design
• Event website design
• Booking website design
• Multilingual website design
• ADA compliant website design
• WordPress development company
• Drupal development company
• Website redesign services
• Website migration services
• Traffic dropped after a website redesign
• Website design and development
• Website cost guide
• Website maintenance
• UI and UX design
• Education software development
• AEO for nonprofits
• AEO for colleges
• Nonprofit marketing agency
• Nonprofit SEO
• Higher education SEO

Frequently asked questions