Skip to content
https://uqam.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
Heading Hierarchy
Action
14 headings, 3 skip(s)
FIX
14 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.
  • H3 Search
  • H3 Search
  • H2 Actualités
  • H4 Chargement... skipped
  • H4 Chargement...
  • H4 Chargement...
  • H4 Chargement...
  • H2 Événements
  • H2 Diplômés
  • H4 Chargement... skipped
  • H2 Balados
  • H2 UQAM.tv
  • H4 Chargement... skipped
  • H2 Nous joindre

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

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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
10 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs aria-label navigation
Search
Skip Link
Labeled Navigation 10 <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
Landmark Structure
46 landmarks
REVIEW
46 landmarks
Info::
<main> landmark present
Info::
10 <nav> landmark(s) found
Warning::
9 of 10 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE 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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

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
h3 Search
1.05:1
#000000
on
#070807
needs 3.0:1 (large text)
19px · above the fold
title UQAM | Université du Québec à Montré…
4.48:1
#000000
on
#0079BE
needs 4.5:1 (normal text)
16px · top of page (header area)
a Raccourci vers le contenu
2.72:1
#000000
on
#005789
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Raccourci vers le menu principal
1.31:1
#000000
on
#002439
needs 4.5:1 (normal text)
16px · top of page (header area)
a Raccourci vers le contenu
1.59:1
#000000
on
#492802
needs 4.5:1 (normal text)
16px · above the fold
a Raccourci vers le menu principal
1.15:1
#000000
on
#211208
needs 4.5:1 (normal text)
16px · above the fold
a Raccourci vers la recherche
1.09:1
#000000
on
#100F0A
needs 4.5:1 (normal text)
16px · above the fold
span Université du Québec à Montréal
2.30:1
#000000
on
#5C432F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Chercher dans :
1.05:1
#000000
on
#070908
needs 4.5:1 (normal text)
16px · above the fold
a Tout uqam.ca
1.04:1
#000000
on
#0A0604
needs 4.5:1 (normal text)
16px · above the fold
a Répertoire des services et ressources
2.16:1
#000000
on
#524134
needs 4.5:1 (normal text)
16px · above the fold
span Chercher dans :
3.75:1
#000000
on
#766552
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Tout uqam.ca
1.27:1
#000000
on
#161F2C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Répertoire des services et ressources
1.42:1
#000000
on
#092947
needs 4.5:1 (normal text)
16px · mid-page

4 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
h2 Nous joindre21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Search1.05:13.0:1
#000000
#070807
Fail
h3 Search21.00:13.0:1
#000000
#FFFFFF
Pass
title UQAM | Université d…4.48:14.5:1
#000000
#0079BE
Fail
a Raccourci vers le co…2.72:14.5:1
#000000
#005789
Fail
a Raccourci vers le me…1.31:14.5:1
#000000
#002439
Fail
a Raccourci vers la re…14.90:14.5:1
#000000
#EFD5BA
Pass
a Raccourci vers le co…1.59:14.5:1
#000000
#492802
Fail
a Raccourci vers le me…1.15:14.5:1
#000000
#211208
Fail
a Raccourci vers la re…1.09:14.5:1
#000000
#100F0A
Fail
span Université du Québ…2.30:14.5:1
#000000
#5C432F
Fail
span Chercher dans :1.05:14.5:1
#000000
#070908
Fail
a Tout uqam.ca1.04:14.5:1
#000000
#0A0604
Fail
a Répertoire des serv…2.16:14.5:1
#000000
#524134
Fail
span Chercher dans :3.75:14.5:1
#000000
#766552
Fail
a Tout uqam.ca1.27:14.5:1
#000000
#161F2C
Fail
a Répertoire des serv…1.42:14.5:1
#000000
#092947
Fail
span Université du Québ…12.28:14.5:1
#000000
#CCC5BC
Pass
a Université du Québ…21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.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.

A+
Alt Text Quality
All 37 images OK
PASS
All 37 images OK
Info::
13 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
37 images 24 good alt text 13 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtextChercheraria-label
qtextChercheraria-label
qtextChercheraria-label
qtextChercheraria-label
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 Page non trouvée | Université du Québec à Montréal | UQAM ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 23 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
21 avril div.GoldenRetriever-wrapper > article.GoldenRetriever-item > div.GoldenRetriever-content > div.GoldenRetriever-date
21 avril div.GoldenRetriever-wrapper > article.GoldenRetriever-item > div.GoldenRetriever-content > div.GoldenRetriever-date
21 avril div.GoldenRetriever-wrapper > article.GoldenRetriever-item > div.GoldenRetriever-content > div.GoldenRetriever-date
21 avril div.GoldenRetriever-wrapper > article.GoldenRetriever-item > div.GoldenRetriever-content > div.GoldenRetriever-date

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
Neuf Uqamiennes et Uqamiens au Conseil des ministres div.GoldenRetriever-wrapper > article.GoldenRetriever-item > div.GoldenRetriever-content > h4.GoldenRetriever-titre
La politique municipale vue par Stéphane Boyer div.GoldenRetriever-wrapper > article.GoldenRetriever-item > div.GoldenRetriever-content > h4.GoldenRetriever-titre
Le recteur vous répond div.GoldenRetriever-wrapper > article.GoldenRetriever-item > div.GoldenRetriever-content > h4.GoldenRetriever-titre

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
●`[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 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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○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.
○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.
○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