Skip to content
https://umanitoba.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Heading Hierarchy
Action
37 headings, 3 skip(s)
FIX
37 headings, 3 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Functional Menu
  • H2 Call To Action Menu
  • H2 Main Menu
  • H2 What are you looking for?
  • H3 Admissions
  • H3 Academics
  • H3 Research
  • H3 Student supports
  • H3 Community
  • H3 About UM
  • H2 Main Menu
  • H2 Functional Menu
  • H2 Call To Action Menu
  • H2 Get ready for your first year at UM!
  • H2 Study with us
  • H3 Undergraduate studies
  • H3 Graduate studies
  • H3 Extended Education
  • H2 Find a program
  • H2 Why UM?
  • H2 31,900
  • H2 $40M
  • H2 U15
  • H2 40+
  • H4 Learn more about UM skipped
  • H2 Be a part of research at UM
  • H2 UM stories
  • H4 Meet the 2026 ENGAP graduates skipped
  • H4 Study to provide insight on origins of rheumatoid arthritis
  • H4 From Nunavut to new beginnings
  • H4 UM Indigenous Birding Club wins international award for student engagement
  • H2 Keep exploring
  • H4 Experience the UM community skipped
  • H4 Check out our campuses
  • H4 Connect with alumni
  • H4 Browse our libraries
  • H4 Join us at Open House

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
13 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 13 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Alt Text Quality
2 of 13 images have issues
REVIEW
2 of 13 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
13 images 7 good alt text 4 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | University of Manitoba ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h2 What are you looking for?
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Main Menu
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Functional Menu
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Call To Action Menu
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get ready for your first year at UM!
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Study with us
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Find a program
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why UM?
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 31,900
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 $40M
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 U15
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 40+
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Be a part of research at UM
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 UM stories
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Keep exploring
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Undergraduate studies
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Graduate studies
1.33:1
#000000
on
#3E1707
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Functional Menu18.62:13.0:1
#000000
#F4F1EA
Pass
h2 Call To Action Menu21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Main Menu21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What are you looking…1.33:13.0:1
#000000
#3E1707
Fail
h2 Main Menu1.33:13.0:1
#000000
#3E1707
Fail
h2 Functional Menu1.33:13.0:1
#000000
#3E1707
Fail
h2 Call To Action Menu1.33:13.0:1
#000000
#3E1707
Fail
h2 Get ready for your f…1.33:13.0:1
#000000
#3E1707
Fail
h2 Study with us1.33:13.0:1
#000000
#3E1707
Fail
h2 Find a program1.33:13.0:1
#000000
#3E1707
Fail
h2 Why UM?1.33:13.0:1
#000000
#3E1707
Fail
h2 31,9001.33:13.0:1
#000000
#3E1707
Fail
h2 $40M1.33:13.0:1
#000000
#3E1707
Fail
h2 U151.33:13.0:1
#000000
#3E1707
Fail
h2 40+1.33:13.0:1
#000000
#3E1707
Fail
h2 Be a part of researc…1.33:13.0:1
#000000
#3E1707
Fail
h2 UM stories1.33:13.0:1
#000000
#3E1707
Fail
h2 Keep exploring1.33:13.0:1
#000000
#3E1707
Fail
h3 Undergraduate studie…1.33:13.0:1
#000000
#3E1707
Fail
h3 Graduate studies1.33:13.0:1
#000000
#3E1707
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.

A
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
13 <nav> landmark(s) found
Warning::
7 of 13 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "block-functional-menu" MAIN CONTENTINFO footer

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
Form Accessibility
1 of 5 controls have issues
PASS
1 of 5 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="search_keyword">
Info::
4 control(s) properly labeled
5 controls
4 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#filter-selector-allradionone
#filter-selector-undergradradionone
#filter-selector-gradradionone
#filter-selector-gradradionone
#search_keywordtext(Program, degree type, topic)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" id="search_keyword">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 27 passed
PASS
95

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
More than div.figure-list__inner > ul.figure-list__items > li.figure-list__item > p.figure-list__tag
UM awards div.figure-list__inner > ul.figure-list__items > li.figure-list__item > p.figure-list__tag
We are a member of the div.figure-list__inner > ul.figure-list__items > li.figure-list__item > p.figure-list__tag
More than div.figure-list__inner > ul.figure-list__items > li.figure-list__item > p.figure-list__tag

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more about UM ul.cta__list > li.cta__item > a.button > h4.cta__button-title
Meet the 2026 ENGAP graduates li.news-list__item > a.u-link-decoration > article.news-card > h4.news-card__title
Experience the UM community ul.cta__list > li.cta__item > a.button > h4.cta__button-title

These are opportunities to improve keyboard navigation in your application.

○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
●Form elements have associated labels
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●Skip links are focusable.
●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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○Elements with visible text labels have matching accessible names.
○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.

Send Feedback