Skip to content
https://concordia.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
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: #912338
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Heading Hierarchy
26 headings
REVIEW
26 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 (empty)
  • H2 (empty)
  • H3 Essential cookies
  • H4 Cassie Banner SyrenisGuid_
  • H4 Concordia Hub
  • H4 Delete Cookie
  • H3 Performance cookies
  • H4 Cassie Banner Performance_Cookie
  • H4 Google Analytics _ga_ custom
  • H3 Marketing cookies
  • H4 Cassie Banner Marketing_Cookie
  • H3 Functional cookies
  • H4 Cassie Banner Functional_Cookie
  • H1 Concordia University Home
  • H1 Didn’t complete high school or CEGEP? duplicate H1
  • H2 Study at Concordia
  • H3 Discover Concordia wherever you are
  • H3 Awards and tuition fee reductions for out-of-province students
  • H2 Find your program
  • H3 Faculties & Schools
  • H2 For future students
  • H3 Undergraduate
  • H3 Graduate
  • H2 News
  • H2 Events
  • H2 Concordia social

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
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
h2 Find your program
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For future students
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h3 Essential cookies
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · mid-page
h3 Faculties & Schools
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
19px · bottom of viewport
title Concordia University
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
p Our site uses cookies. They allow us to …
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Cookie Notice
1.12:1
#000000
on
#1A100B
needs 4.5:1 (normal text)
16px · top of page (header area)

1 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)
ElementRatioRequiredFGBGResult
h1 Concordia University…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Didn’t complete hi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Study at Concordia8.40:13.0:1
#912338
#FFFFFF
Pass
h2 Find your program1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h2 For future students1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h2 News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Events21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Concordia social21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Essential cookies1.02:13.0:1
#000000
#040404
Fail
h3 Performance cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Marketing cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Functional cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Discover Concordia w…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Awards and tuition f…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Faculties & Schools1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h3 Undergraduate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Graduate21.00:13.0:1
#000000
#FFFFFF
Pass
title Concordia University2.45:14.5:1
#000000
#4C4C4C
Fail
p Our site uses cookie…2.45:14.5:1
#000000
#4C4C4C
Fail
a Cookie Notice1.12:14.5:1
#000000
#1A100B
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 27 passed
REVIEW
88

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
APR 23 Living Archives, Moving Tides: Black Feminist Caribbean Thought Tomorrow… div.row > div.parsys_column > div.c-list-featured-events > ul.c-eventbar

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
APR 23 Living Archives, Moving Tides: Black Feminist Caribbean Thought Tomorrow… div.c-list-featured-events > ul.c-eventbar > div.d-flex > li.condensed-item
APR 27 Highlights from a Year of Public Scholarship Monday, 2 p.m. – 5 p.m. div.c-list-featured-events > ul.c-eventbar > div.d-flex > li.condensed-item
APR 29 From Identified Needs to Practical Use Wednesday, 1 p.m. – 4 p.m. div.c-list-featured-events > ul.c-eventbar > div.d-flex > li.condensed-item
APR 30 How are we aging with AI? Thursday, 11 a.m. – 4:30 p.m. div.c-list-featured-events > ul.c-eventbar > div.d-flex > li.condensed-item

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Our site uses cookies. They allow us to remember your preferences, better serve… body.home > div#cassie-widget > div.cassie-cookie-module > div.cassie-pre-banner

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.

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
Virtual events div.c-link-list__container > ul.c-link-list--col-2 > li > a
Sign up for updates div.c-link-list__container > ul.c-link-list--col-2 > li > a
Connect with our team div.c-link-list__container > ul.c-link-list--style-bold-large > li > a
○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
●`[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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○`<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.
A
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <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 "Main navigation" 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+
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
1 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
14 images 13 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#c-site-search__form--input-concordiatextSearch Concordiaaria-label
#c-site-search__form--input-directoriestextSearch Directoriesaria-label
#programFiltertextSearchfor/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Concordia University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Concordia University
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Concordia University ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Concordia University Display Mode standalone Theme Color #932439 Background Color #ffffff Icons 2 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback