Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

Link & Button Quality

1 issue(s) across 125 links and 6 buttons

REVIEW

1 issue(s) across 125 links and 6 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

10 link(s) open in new tab without warning

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

Got: https://indigenous.utoronto.ca/about/land-acknowledgement/; https://twitter.com/uoft; https://www.facebook.com/universitytoronto; https://www.instagram.com/uoft/; https://www.youtube.com/user/universitytoronto; https://www.linkedin.com/school/university-of-toronto/; https://www.tiktok.com/@uoft; https://bsky.app/profile/utoronto.ca; https://www.threads.com/@uoft; /social-media-directory

114 link(s) with descriptive text

125 links

1 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://indigenous.utoronto.ca/about/lan…	Read about U of T’s Statemen…	new tab	Add '(opens in new tab)' to text
https://twitter.com/uoft	Twitter link	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/universitytoron…	Facebook link	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/uoft/	instagram link	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/universityt…	YouTube link	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/universi…	LinkedIn link	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@uoft	Tik tok link	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/utoronto.ca	Bluesky link	new tab	Add '(opens in new tab)' to text
https://www.threads.com/@uoft	Threads link	new tab	Add '(opens in new tab)' to text
/social-media-directory	Social media directory link	new tab	Add '(opens in new tab)' to text

120 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://indigenous.utoronto.ca/about/land-acknowledgement/; https://twitter.com/uoft; https://www.facebook.com/universitytoronto; https://www.instagram.com/uoft/; https://www.youtube.com/user/universitytoronto; https://www.linkedin.com/school/university-of-toronto/; https://www.tiktok.com/@uoft; https://bsky.app/profile/utoronto.ca; https://www.threads.com/@uoft; /social-media-directory

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

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 page not found | University of Toronto ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA

h1 Welcome to University of Toronto

1.79:1

#000000

#1E3765

needs 3.0:1 (large text)

32px · top of page (header area)

h2 Main menu tools

1.79:1

#000000

#1E3765

needs 3.0:1 (large text)

24px · top of page (header area)

title University of Toronto

1.79:1

#000000

#1E3765

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.79:1

#000000

#1E3765

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to Universit…	1.79:1	3.0:1	#000000	#1E3765	Fail
h2 Main menu tools	1.79:1	3.0:1	#000000	#1E3765	Fail
h2 Jump to menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Main navigation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Main menu tools	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Main navigation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Jump to menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 UTogether: Your guid…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest news	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Upcoming events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Main navigation repe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Jump to menu repeate…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Quick links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Quick links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title University of Toront…	1.79:1	4.5:1	#000000	#1E3765	Fail
a Skip to main content	1.79:1	4.5:1	#000000	#1E3765	Fail
a Email	20.68:1	4.5:1	#000000	#FFFDFA	Pass
a Quercus	16.71:1	4.5:1	#000000	#F2E3D4	Pass
a Acorn	16.91:1	4.5:1	#000000	#F4E4D6	Pass
a Campus status	15.78:1	4.5:1	#000000	#EFDCCC	Pass

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

15 landmarks

PASS

15 landmarks

<main> landmark present

11 <nav> landmark(s) found

1 of 11 <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

14 headings

PASS

14 headings

Single H1 present

H1 Welcome to University of Toronto
H2 Main menu tools
H2 Jump to menu
H2 Main navigation
H2 Main menu tools
H2 Main navigation
H2 Jump to menu
H2 UTogether: Your guide to the U of T community
H2 Latest news
H2 Upcoming events
H2 Main navigation repeated
H2 Jump to menu repeated
H2 Quick links
H2 Quick links

A+

Alt Text Quality

All 9 images OK

PASS

All 9 images OK

9 image(s) with good alt text

9 images 9 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-query	text	Search	aria-label
#edit-query	text	Search in mobile	aria-label

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 26 passed

PASS

100

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.

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
U of T News U of T ranked first in Canada, among top 17 globally across all br… `div.paragraph > section.hero-banner-section > div.heading-wrapper > a.container`
April 20, 2026 This Toronto researcher found where memories live. Can she help … `div.container > div.view-content > div.views-row > a.news-grid-item`
April 16, 2026 Study finds evidence of stellar explosions that don't leave behi… `div.view > div.view-content > div.views-row > a.news-grid-item`
April 15, 2026 GLP-1 medicine improves liver health independent of weight loss:… `div.view > div.view-content > div.views-row > a.news-grid-item`
April 28, 2026 Dr. Marguerite (Peggy) Hill Memorial Lecture on Indigenous Health `div.container > div.view-content > div.views-row > a.news-grid-item`
April 22, 2026 Women Driving Health Innovation: Celebrating Excellence in Entre… `div.view > div.view-content > div.views-row > a.news-grid-item`
April 26, 2026 Aki (2025) Film Screening & Panel Discussion `div.view > div.view-content > div.views-row > a.news-grid-item`
U of T Celebrates The University of Toronto is home to some of the world’s top… `div.paragraph > div.celebrates-banner > div.container > a.row`
Questions about change and opportunity run throughout our first-ever student is… `div.field__item > div.paragraph > div.magazine-banner > a.row`

○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

●Elements use only permitted ARIA attributes

●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 are distinguishable without relying on color.

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[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

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○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.

○Identical links have the same purpose.

○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.