Skip to content
https://www.mcgill.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA
h2 Start something
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 extraordinary.
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 puts you at the centre of the action
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Interested in joining our community?
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 News
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Department and University Information
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 McGill
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Winter doesn’t keep Montrealers indoor…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Internship opportunities in AI, tech and…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Francofête puts French in the spotlight
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 McGill Alumnus Peter Howitt awarded 2025…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 McGill tops Maclean’s rankings
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 UNESCO honours McGill’s Universal Decl…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 McGill launches initiative to strengthen…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Start something1.00:13.0:1
#000000
#000000
Fail
h2 extraordinary.1.00:13.0:1
#000000
#000000
Fail
h2 puts you at the cent…1.00:13.0:1
#000000
#000000
Fail
h2 Interested in joinin…1.00:13.0:1
#000000
#000000
Fail
h2 News1.00:13.0:1
#000000
#000000
Fail
h2 Department and Unive…1.00:13.0:1
#000000
#000000
Fail
h2 McGill1.00:13.0:1
#000000
#000000
Fail
h3 Winter doesn’t kee…1.00:13.0:1
#000000
#000000
Fail
h3 Internship opportuni…1.00:13.0:1
#000000
#000000
Fail
h3 Francofête puts Fre…1.00:13.0:1
#000000
#000000
Fail
h3 McGill Alumnus Peter…1.00:13.0:1
#000000
#000000
Fail
h3 McGill tops Maclean…1.00:13.0:1
#000000
#000000
Fail
h3 UNESCO honours McGil…1.00:13.0:1
#000000
#000000
Fail
h3 McGill launches init…1.00:13.0:1
#000000
#000000
Fail
title McGill University21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
span McGill University21.00:14.5:1
#000000
#FFFFFF
Pass
a Admissions21.00:14.5:1
#000000
#FFFFFF
Pass
a Find an undergraduat…21.00:14.5:1
#000000
#FFFFFF
Pass
a Undergraduate admiss…21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 5 failing, 17 passed
REVIEW
81

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#page > div#header > div.section > button.js-menu-toggle div#page > div#header > div.section > button.js-menu-toggle

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
In an emergency div.field-item > ul > li > h4

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These are opportunities to improve the interpretation of your content by users in different locales.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Admissions div#block-menu-menu-global-menu > div.content > ul.menu > li.first
Research div#block-menu-menu-global-menu > div.content > ul.menu > li.expanded
Student life div#block-menu-menu-global-menu > div.content > ul.menu > li.expanded
Why Montreal div#block-menu-menu-global-menu > div.content > ul.menu > li.expanded
About McGill div#block-menu-menu-global-menu > div.content > ul.menu > li.last

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<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>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
A
Heading Hierarchy
19 headings, 1 skip(s)
PASS
19 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 McGill University
  • H2 Find what moves you. Start something extraordinary.
  • H2 A dynamic, diverse city puts you at the centre of the action
  • H3 Winter doesn’t keep Montrealers indoors
  • H3 Internship opportunities in AI, tech and more
  • H3 Francofête puts French in the spotlight
  • H2 Interested in joining our community?
  • H2 News
  • H3 McGill Alumnus Peter Howitt awarded 2025 Nobel Prize in Economics
  • H3 McGill tops Maclean’s rankings
  • H3 UNESCO honours McGill’s Universal Declaration of Human Rights archives
  • H3 McGill launches initiative to strengthen Canada’s healthcare system
  • H2 Department and University Information
  • H4 In an emergency skipped
  • H4 Visit
  • H4 Get in touch
  • H4 Explore
  • H2 McGill
  • H2 Anthem video ENG NS

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

A+
Alt Text Quality
All 4 images OK
PASS
All 4 images OK
Info::
4 image(s) with good alt text
4 images 4 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 5 controls have issues
PASS
1 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="edit-submit-9">
Info::
4 control(s) properly labeled
5 controls
4 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-keys-9textEnter your keywordsfor/id
#cookie-category-requiredcheckboxEssential cookies that allow our website to functionfor/id
#cookie-category-performancecheckboxPerformance cookies that collect usability datafor/id
#cookie-category-marketingcheckboxMarketing cookies that can personalize your web experiencesfor/id
#edit-submit-9submit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="op" id="edit-submit-9">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

Send Feedback