Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

13 pass 7 fail WCAG AA 1 pass AA only

button Search

1.29:1

#000000

#002044

needs 4.5:1 (normal text)

16px · top of page (header area)

a Academic Calendar

1.28:1

#000000

#06203D

needs 4.5:1 (normal text)

16px · above the fold

a Campus Services

2.70:1

#000000

#575338

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Maps

4.16:1

#000000

#6D724D

needs 4.5:1 (normal text)

16px · above the fold

a Quicklinks

1.36:1

#000000

#212525

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Workday

1.36:1

#000000

#182633

needs 4.5:1 (normal text)

16px · above the fold

a UBC Directory

1.24:1

#000000

#051D37

needs 4.5:1 (normal text)

16px · above the fold

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The University of Br…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Marquee	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Spotlight	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Connect with UBC	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore UBC	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Smarter forest pract…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About UBC	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 UBC Campuses	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title The University of Br…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Search UBC	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Search	1.29:1	4.5:1	#000000	#002044	Fail
a Academic Calendar	1.28:1	4.5:1	#000000	#06203D	Fail
a Campus Services	2.70:1	4.5:1	#000000	#575338	Fail
a Faculties & Schools	7.11:1	4.5:1	#000000	#98996D	Pass
a Library	5.32:1	4.5:1	#000000	#828352	Pass
a Maps	4.16:1	4.5:1	#000000	#6D724D	Fail
a Quicklinks	1.36:1	4.5:1	#000000	#212525	Fail
a Workday	1.36:1	4.5:1	#000000	#182633	Fail
a UBC Directory	1.24:1	4.5:1	#000000	#051D37	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

5 <nav> landmark(s) found

2 of 5 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

H1 The University of British Columbia
H2 Marquee
H3 Smarter forest practices
H2 Spotlight
H3 Attend a spring workshop at the UBC Farm
H3 Join a weekly tour at the Chung | Lind Gallery
H3 UBC researchers aim for earlier toxic drug supply warnings
H2 Connect with UBC
H2 Explore UBC
H3 New UBC wash removes pesticides and extends produce shelf life
H3 Push forward with UBC: Revolutionizing wildfire preparedness
H3 The retirement of the single-use cup
H3 Bridges, roadways threatened by changes in weather patterns
H3 It’s not all in your head: Seasonal allergies are getting worse
H3 Understanding why owners surrender their pets
H3 About UBC
H3 UBC Campuses
H4 UBC Sites

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

1 image(s) with alt text over 125 characters

9 image(s) with good alt text

10 images 9 good alt text

Issue	Count
too long	1 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#q	text	Search UBC	for/id

Link & Button Quality

89 links, 2 buttons — all OK

PASS

89 links, 2 buttons — all OK

12 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: //www.facebook.com/universityofbc?fref=ts; //instagram.com/universityofbc; //twitter.com/ubc; https://www.linkedin.com/school/universityofbc; //www.youtube.com/user/ubc; https://www.tiktok.com/@universityofbc; //www.facebook.com/universityofbc?fref=ts; //instagram.com/universityofbc; //twitter.com/ubc; https://www.linkedin.com/school/universityofbc (+2 more)

77 link(s) with descriptive text

89 links

0 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
//www.facebook.com/universityofbc?fref=t…	facebook	new tab	Add '(opens in new tab)' to text
//instagram.com/universityofbc	instagram	new tab	Add '(opens in new tab)' to text
//twitter.com/ubc	twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/universi…	Linkedin	new tab	Add '(opens in new tab)' to text
//www.youtube.com/user/ubc	YouTube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@universityofbc	TikTok	new tab	Add '(opens in new tab)' to text
//www.facebook.com/universityofbc?fref=t…	facebook	new tab	Add '(opens in new tab)' to text
//instagram.com/universityofbc	instagram	new tab	Add '(opens in new tab)' to text
//twitter.com/ubc	twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/universi…	Linkedin	new tab	Add '(opens in new tab)' to text
//www.youtube.com/user/ubc	YouTube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@universityofbc	TikTok	new tab	Add '(opens in new tab)' to text

79 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

//www.facebook.com/universityofbc?fref=ts; //instagram.com/universityofbc; //twitter.com/ubc; https://www.linkedin.com/school/universityofbc; //www.youtube.com/user/ubc; https://www.tiktok.com/@universityofbc; //www.facebook.com/universityofbc?fref=ts; //instagram.com/universityofbc; //twitter.com/ubc; https://www.linkedin.com/school/universityofbc (+2 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found (Error 404) | The University of British Columbia ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 22 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Main Menu `div.container > div.span12 > div.navbar > a#ubc-unit-btn`
Audience Menu `div.container > div.span12 > div.navbar > a#ubc-audience-btn`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
News `div.row-fluid > div.span6 > div > a`
Events `div.row-fluid > div.span6 > div > a`
Careers `div.row-fluid > div.span6 > div > a`
Vancouver Campus `div.row-fluid > div.span6 > div > a`
Okanagan Campus `div.row-fluid > div.span6 > div > a`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
UBC Search `div.container > div#ubc7-wordmark-block > div#ubc7-global-utility > button`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.