University Website UX: Stop Losing Applicants to Poor Design

Your university website is losing 9 out of 10 prospects before they ever contact you

91% of university website visitors leave without ever making contact (Source: Skolbot funnel analysis, 30 institutions, 2025–2026). That number is not a marketing anomaly. It is the predictable result of websites built for institutional communications teams, not for a grade 12 student in Mississauga researching their options on a phone at 9pm on a Sunday.

Canadian post-secondary institutions face a compounding challenge. You are recruiting across six time zones, competing with U.S. institutions that market aggressively into your domestic pool, and navigating provincial application systems — OUAC in Ontario, provincial application centres in British Columbia, Alberta, and the Atlantic provinces — that your website must complement rather than duplicate. None of that complexity makes UX easier. It makes it more consequential.

This checklist covers the four areas responsible for the largest share of silent abandonment: mobile UX, inquiry forms, open house sign-up, and a prioritized fix matrix calibrated for Canadian institutional web teams.

For the broader picture of what high-converting Canadian university websites look like, see our guide on school website pages that convert and our enrolment conversion rate benchmarks by Canadian institution type.

1. How poor UX costs you applicants — the mechanics of silent abandonment

Abandonment follows a pattern that Skolbot's analytics have now tracked across thousands of Canadian post-secondary prospect journeys. Prospects visit an average of 4.7 pages before asking their first question — program pages (92% of journeys), tuition and financial aid (78%), and admissions requirements (71%) (Source: analytics from 15,000 prospect journeys, 2025–2026 cycle). Those three page types are where your website either earns continued engagement or loses the prospect permanently.

67% of prospective student activity happens outside business hours, with a peak on Sundays between 8 and 9pm (Source: Skolbot interaction logs, 200,000 sessions, Oct 2025–Feb 2026). For Canadian institutions recruiting from Vancouver to St. John's, this out-of-hours reality is compounded by a six-timezone span: a student in Alberta inquiring at 9pm MT is reaching out at 11pm ET — well past any staffed admissions office. A website that depends on a human response to close the loop is a website that cannot close this loop at all.

The opportunity is equally clear. An AI chatbot reduces bounce rate from 68% to 41% — a 39.7% relative reduction — and extends session duration from 1m 45s to 4m 12s (Source: A/B test across 22 partner institution websites, Sept–Dec 2025). The chatbot works because it intercepts the moment a question forms — on a program page, a tuition page, an open house registration page — and answers it before that question becomes a reason to close the tab.

2. Mobile UX checklist

In 2026, the majority of post-secondary website traffic in Canada comes from smartphones. A student comparing a U15 university's engineering program against two competitors is almost certainly doing it on a phone, often while commuting, and frequently after Maclean's rankings have already narrowed their shortlist. A website that does not work on mobile at this stage of the decision is a website that does not exist.

Performance floor

• Largest Contentful Paint (LCP): <2.5s on a mid-range Android over LTE. Measure with Google PageSpeed Insights. Program page hero images over 300KB are the most common culprit at Canadian institutions.
• Cumulative Layout Shift (CLS): <0.1. Layout shifts caused by late-rendering banner images and third-party embeds are particularly damaging on the smaller screens of mid-range Androids — the most common device class among Canadian first-generation university applicants.
• Third-party scripts: audit aggressively. Social media embeds, retargeting pixels, and accessibility overlay widgets can collectively add 4–6 seconds to mobile load time on a typical Canadian university homepage.

Structure and navigation

• Primary CTAs — "Register for Open House," "Request Program Information," "Apply via OUAC" — must be reachable with the right thumb in the bottom 60% of the screen without scrolling.
• Tap targets must be at least 44×44 pixels with 8px separation. This is the single most common mobile UX failure Skolbot encounters on Canadian university sites.
• Navigation must be <2 levels deep. A top-level "Academics" menu that opens into a full departmental tree is a dead end for a prospect who arrived looking for admission requirements for a specific program.
• Sticky navigation with quick links to program, tuition, and apply pages should persist through scroll on program landing pages. A prospect lost deep in a long-scroll page without an escape route is a prospect who uses the back button to leave the site entirely.

Accessibility — AODA and WCAG 2.1 AA

For Ontario institutions, the Accessibility for Ontarians with Disabilities Act (AODA) requires that public websites and web content meet WCAG 2.0 Level AA. The practical standard that most Canadian accessibility practitioners recommend — and that the W3C's WCAG 2.1 AA quick reference codifies — goes further and is the appropriate target for any institution seeking to avoid complaints under the AODA or the Canadian Human Rights Act.

Critical WCAG 2.1 AA requirements for Canadian university websites:

• Colour contrast: 4.5:1 for body text, 3:1 for large text. Institutional brand palettes frequently fail this test on mobile screens in variable lighting.
• All form fields and buttons must have programmatic labels (<label> elements or aria-label).
• Keyboard focus indicators must be visible on every interactive element — including chat widgets, which are frequently deployed without focus styling.
• Layout must hold at 200% text zoom without horizontal scrolling.
• Autoplay video (common on Canadian university homepages) must respect prefers-reduced-motion.

AODA non-compliance carries real consequences for Ontario institutions, including formal complaints to the Accessibility Directorate. For institutions with significant Quebec enrolment, note that Quebec's Loi 25 (Act 25) creates additional obligations around digital accessibility and data transparency.

For a complete mobile scoring methodology, see our mobile-first enrolment UX checklist for schools.

3. Inquiry form checklist

The inquiry form is the digital handshake. For a Canadian prospect who has spent 15 minutes comparing your engineering program against those of two other U15 universities, the inquiry form is the moment they decide whether your institution deserves their personal information. Most forms fail this test — not because institutions are careless, but because forms are built by IT teams to capture data, not by UX designers to reduce friction.

Field count and form structure

• Inquiry forms should have <6 fields. First name, last name, email, program of interest, intended start year, and province of residence (useful for routing to the correct admissions team and for OSAP vs. Canada Student Loans eligibility guidance). That is your maximum.
• Do not ask for GPA, transcripts, or references on an inquiry form. Those belong in the formal application — via OUAC for Ontario applicants, or through the relevant provincial application centre for other provinces.
• Multi-step forms with a visible progress indicator outperform long single-screen forms. A two-step form — "About you / About your program interest" — with a persistent progress bar converts at materially higher rates than an 8-field single-screen form.
• Full applications submitted through institutional portals (outside OUAC) should offer save-and-resume via email magic link. Ontario applicants using OUAC benefit from OUAC's own session management, but supplemental forms and interest registration forms do not.

Input types and autofill

• Set type="email" and type="tel" on the correct fields. Mobile keyboards that do not adapt to the field type add friction every time a prospect must switch keyboards manually.
• Add autocomplete attributes to name, email, phone, and postal code fields. Canada Post postal code format (A1A 1A1) is handled correctly by most modern browsers when autocomplete="postal-code" is set — but only if the attribute is present.
• For bilingual institutions with francophone applicants, ensure all form labels and error messages are available in both official languages. This is particularly relevant for institutions recruiting in Quebec and New Brunswick.

Error states and validation

• Error messages must be inline, field-level, and specific: "Please enter a valid email address" rather than "There was a problem with your submission."
• Validate on blur, not on submit. Submit-time validation on a mobile form forces the prospect to scroll up and re-identify errors — most do not complete the correction.

PIPEDA compliance and privacy at point of capture

Canada's federal privacy legislation — the Personal Information Protection and Electronic Documents Act (PIPEDA) — requires that institutions collect personal information with the knowledge and consent of the individual, and only for purposes that a reasonable person would consider appropriate. Quebec's Loi 25 adds materially to these obligations, including requirements for a privacy impact assessment before deploying new data collection tools.

Practical requirements for every inquiry form at a Canadian university:

• Display a one-line privacy summary directly adjacent to the email field: "Your information will be used to respond to your enquiry. See our [privacy notice]."
• Link to your full privacy notice from the form — not only from the footer.
• Include a consent checkbox for any marketing use of the submitted data that is separate from the primary enquiry response. Under PIPEDA, using an inquiry to add a prospect to a general marketing list without separate consent is non-compliant.
• If your institution recruits from or operates in Quebec, review your data collection practices against Loi 25's requirements for explicit consent, privacy policy readability, and the right to data portability.

For a detailed treatment of privacy compliance in student recruitment, see our guide to protecting prospect data.

4. Open house sign-up UX

An open house attendee converts to applicant at dramatically higher rates than a prospect who only ever visited your website. The decision to attend an open house is a high-intent signal — and the registration experience is where many Canadian institutions inadvertently suppress that intent.

The registration flow

• Open house sign-up should complete in <3 taps from the program page: program page → "Register for Open House" → date/time picker → confirmation. Every additional step — account creation, email verification before registration, selecting a secondary session track — is a drop-off point.
• Do not require account creation to register for an open house. A prospect who encounters a "create a password" step during a simple event registration will abandon at rates exceeding 40%. If your CRM requires an account to track the registration, create it silently on the back end using the submitted email.
• Show available dates prominently for the next four to six weeks. A registration page that shows no open house dates for the next two months is not a registration page — it is a reason to stop looking.
• Offer virtual open house options with equal prominence alongside in-person events. This is particularly important for interprovincial prospects — a student in British Columbia considering a Toronto-based university needs a credible way to engage before committing to a flight.

Confirmation and follow-through

• Send a confirmation email within 60 seconds with: the date, time, and location (or Zoom/Teams link for virtual events); a calendar file (ICS) for both iOS and Google Calendar; and a named contact in the admissions office.
• Send a 48-hour reminder email with a one-tap confirmation link. Institutions that add this step reduce no-show rates by 25–35%.
• After the open house, trigger a personalised follow-up email within 24 hours. Include a direct link to the OUAC application portal (for Ontario applicants), information about OSAP eligibility and the Ontario Student Assistance Program application timeline, and a named financial aid contact. Prospects who receive this email within 24 hours of attending an open house convert to applicants at measurably higher rates than those who receive a generic follow-up after a week.

For CEGEP students and Quebec applicants

Quebec-based students applying through the CEGEP system follow a different application pathway and timeline. Open house registration pages for institutions recruiting in Quebec should reflect this: include a field for "Current institution type" (CEGEP / Secondary school / Other), adjust the follow-up messaging to reference the appropriate application portal, and offer bilingual registration confirmation.

Out-of-hours booking

67% of prospective student activity happens outside business hours (Source: Skolbot interaction logs, 200,000 sessions, Oct 2025–Feb 2026). Open house registration must be fully self-serve, 24 hours a day, across all time zones — Pacific to Atlantic. If your current registration process involves emailing an admissions office to "confirm your spot," you are losing the majority of your most motivated prospects to institutions that let them register immediately and autonomously.

For the full treatment of optimising digital open day experiences, see our guide to open day digital optimization for schools.

5. Priority UX fix matrix

The table below rates the most common Canadian university website UX failures by their impact on enrolment contact rate, implementation effort for a standard institutional web team, and whether they belong in the first 30-day sprint.

Start with the first seven rows. They are high-impact, low-to-medium effort, and directly connected to the 91% abandonment rate. The remainder are genuine improvements, but they will not move the needle in your first sprint.

FAQ

Why does our university website have a high exit rate if the content is strong?

Content quality and content accessibility are different problems. A prospect on a mid-range Android phone researching your program at 9pm will not read your excellent program description if the page takes 4 seconds to load, if the mobile navigation requires three levels of tapping to reach the admissions requirements, or if the tuition page only offers a downloadable PDF. Exit rates are driven primarily by performance and structure failures — not content failures.

How many fields should a Canadian university inquiry form have?

Six at most: first name, last name, email, program of interest, intended start year, and province of residence (useful for routing and for OSAP vs. Canada Student Loans context). Everything else — GPA, grade 12 course selection, supplemental portfolio — belongs in the OUAC application or the institutional application portal. Every additional field beyond six reduces form completion rates by approximately 5–10%.

What does PIPEDA require for university inquiry forms?

Under PIPEDA, you must collect personal information with knowledge and consent, for purposes a reasonable person would consider appropriate. In practice, this means: display a clear privacy notice adjacent to the submission button; link to your full privacy policy from the form; and use a separate, explicit consent mechanism if you intend to add the prospect to a marketing list beyond responding to their enquiry. Quebec's Loi 25 adds further obligations, including privacy impact assessments for new data collection tools.

Should OUAC link directly from our program pages, or only from the admissions page?

Both. The OUAC link should appear on every program page — with clear labelling for Ontario applicants — and on the admissions page with full context about the OUAC application cycle, deadlines, and program-specific requirements. Prospects should never have to navigate from a program page to a separate admissions page just to find the application link. Reduce every step between interest and application initiation.

How does an AI chatbot reduce open house no-show rates at Canadian universities?

The chatbot intercepts the gap between registration and attendance. A student who registered two weeks ago may have forgotten details, lost the confirmation email, or developed a question about parking or accommodations. A chatbot available at 11pm the night before the open house answers these questions immediately — reducing uncertainty, and therefore no-shows. In Skolbot's data, the combination of a 48-hour reminder email and an available chatbot reduces open house no-show rates by 30–40% compared to reminder-only strategies.

Your university website is not underperforming because your institution lacks excellence. It is underperforming because the digital path between that excellence and the prospect who needs to find it contains friction that your admissions team has rarely been asked to measure. The checklist above is not a redesign. It is a targeted audit of the moments where your best-fit applicants are quietly, invisibly leaving.

For the generational context driving these expectations, see our article on what Gen Z expects from a university website.