Back
Back

Mount Royal University

2019–24

Nearly five years of making a library website work for everyone

Nearly five years of making a library website work for everyone

Accessible, data-led web design for a university library.

Mount Royal University Library website

Role

Product Designer & Developer

Duration

November 2019 to August 2024

Services

Public web, PHP-based CMS

Category

Public sector

Overview

A library site that has to work at 11pm

For nearly five years I designed and built the Mount Royal University Library website. Students, faculty and staff use it to find rooms, resources and answers, on every device, and at every ability.

The Impact

The through-line was a loop: research, then a change, then analytics. These are the practices, not a scoreboard. The public case study does not claim a single percentage.

5 yrs

on a live public site

November 2019 to August 2024

AA

WCAG 2.1

Semantic HTML, keyboard and screen reader checks

Monthly

analytics reports

Custom tracking the team could read

Problem

People could not find the thing they came for

The homepage tried to be everything to everyone. Room booking and event registration were full of confusing date and time controls. WCAG 2.1 AA was the standard, not a nice-to-have.

01

An overloaded homepage

Top tasks were buried under everything the library might want to say.

02

Forms people left

Date and time pickers asked for more than the booking needed.

03

Access as a final check

A public site cannot treat keyboard and screen reader support as polish.

Research

Interviews, card sorts, then the numbers

I ran interviews and card sorts to learn what people actually came for, then used A/B tests and analytics to see whether the changes worked.

Interviews

Students, faculty and staff, on why they came.

Card sorts

What belonged together on the homepage.

Analytics

Custom tracking and a monthly report.

What we learned

People came for a small set of tasks: rooms, resources, answers. The homepage got better when it led with those, and the booking form got better when it asked for less.

Always a pleasure to work with, super amenable, open to feedback, and a general fantastic team member.

Work colleague

Mount Royal University

Organizing recurring patterns and behaviors

Research said what to try. A/B tests and analytics said whether it worked. Monthly reports kept the team looking at the same evidence.

Key insights

A homepage that tries to serve everyone should serve the top tasks first.

Date and time controls were where people gave up.

Mobile-first Bootstrap was the practical way to ship the new homepage.

Accessibility belonged in the build: semantic HTML, keyboard tests, screen reader audits, QA.

Understanding the user journey

Four jobs on a site that cannot go down: arrive, book, use it without a mouse, and decide what to change next.

01

Arrive on the homepage

Friction

Too many doors, and no clear first task.

Opportunity

Interviews and card sorts, then a restructure around top tasks.

Impact

Lower bounce was the aim. A/B tests kept the team honest.

02

Book a room

Friction

Confusing date and time controls.

Opportunity

A simpler layout, and pickers that ask for what mattered.

Impact

The aim was fewer abandoned bookings.

03

Use it with a keyboard

Friction

A public site has to work without a mouse, and for a screen reader.

Opportunity

Semantic HTML, keyboard testing and screen reader audits.

Impact

Compliance reviews with QA, as part of the build.

04

Decide the next change

Friction

Opinion was not enough on a site that cannot go down.

Opportunity

Custom Google Analytics and an automated monthly report.

Impact

The team could see what was working.

Ideation

The homepage, the form, and the evidence

The long work was the homepage and the booking form. Alongside that: posters, banners, icons and interactive displays in the Immersion Studio.

Mount Royal University Library website

Homepage structure, a simpler booking form, and a monthly look at the numbers.

01

Homepage around top tasks

Restructured from interviews and card sorts, then built mobile-first in Bootstrap.

02

A shorter booking form

Cleaner date and time controls, asking only for what the booking needed.

03

Evidence on a cadence

Custom analytics and a monthly report, so the next change had a reason.

Testing interaction flows early

A/B tests on the homepage, a close look at the booking changes, and accessibility audits with QA. Releases had to be careful, because the site stays up.

Designs

Homepage, booking, and the edges

I designed the key pages and built the front end in accessible HTML, CSS and JavaScript, on a PHP-based CMS.

The homepage redesign, organised around the tasks people actually came for.

The booking form and wayfinding solutions.

Side work: posters, banners, icons, and displays in the Immersion Studio.

Lessons

Careful, collaborative, and patient

Shipping to a live public site that cannot go down taught me to treat accessibility as part of the build. The data habit mattered as much as any single page.

Key outcomes

A clearer homepage

Structured around what interviews and card sorts found.

A simpler booking form

Fewer confusing controls between the person and the room.

Accessibility as default

WCAG 2.1 AA in the front end and in QA.

A shared evidence loop

Monthly analytics the whole team could read.

More work

All work

Callum O'Connor

I'm a product designer who makes complex experiences feel simple.

© 2026 Callum O'Connor

Callum O'Connor

I'm a product designer who makes complex experiences feel simple.

© 2026 Callum O'Connor

Callum O'Connor

I'm a product designer who makes complex experiences feel simple.

© 2026 Callum O'Connor