Skip to content
https://ontario.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
3
REVIEW
3
PASS
7
INFO
0
Checks
13
7 PASS 3 REVIEW 3 FIX
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::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 8 <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
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title We can’t find that page | ontario.ca ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Ontario.ca
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Ontario.ca ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Name Ontario.ca Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA 3 pass AA only
h2 Sign-in Menu EN
1.97:1
#000000
on
#443E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sign-in Menu EN
1.97:1
#000000
on
#443E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Questions or comments
1.97:1
#000000
on
#443E28
needs 3.0:1 (large text)
24px · bottom of viewport
title Government of Ontario | ontario.ca
2.46:1
#000000
on
#4D4F21
needs 4.5:1 (normal text)
16px · top of page (header area)
span Government of Ontario home page
1.52:1
#000000
on
#2D2F08
needs 4.5:1 (normal text)
16px · top of page (header area)
a Français
2.15:1
#000000
on
#414725
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Search
4.45:1
#000000
on
#6D7A20
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Menu
2.24:1
#000000
on
#47491C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Sign in
1.43:1
#000000
on
#2A291B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Benefits and taxes
3.70:1
#000000
on
#666B2B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

5 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 Sign-in Menu EN1.97:13.0:1
#000000
#443E28
Fail
h2 Sign-in Menu EN1.97:13.0:1
#000000
#443E28
Fail
h2 Questions or comment…1.97:13.0:1
#000000
#443E28
Fail
title Government of Ontari…2.46:14.5:1
#000000
#4D4F21
Fail
a Skip to main content11.90:14.5:1
#000000
#BCCD29
Pass
span Government of Ontari…1.52:14.5:1
#000000
#2D2F08
Fail
label Search5.33:14.5:1
#000000
#748915
Pass
a Français2.15:14.5:1
#000000
#414725
Fail
span Search4.45:14.5:1
#000000
#6D7A20
Fail
span Topics5.92:14.5:1
#000000
#828F32
Pass
span Menu2.24:14.5:1
#000000
#47491C
Fail
span Sign in1.43:14.5:1
#000000
#2A291B
Fail
span close4.79:14.5:1
#000000
#757E32
Pass
span Benefits and taxes3.70:14.5:1
#000000
#666B2B
Fail
span Business and economy7.65:14.5:1
#000000
#A79D64
Pass
span Courts, justice and …7.05:14.5:1
#000000
#9C9585
Pass
span Driving and road saf…8.76:14.5:1
#000000
#B5A591
Pass
span Education and appren…10.17:14.5:1
#000000
#C0B2A8
Pass
span Environment and ener…13.90:14.5:1
#000000
#DAD0CF
Pass
span Family and social se…16.65:14.5:1
#000000
#E9E4E1
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
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
6 of 8 <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 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+
Heading Hierarchy
5 headings
PASS
5 headings
Info::
Single H1 present
  • H2 Sign-in Menu EN
  • H2 Sign-in Menu EN
  • H1 Government of Ontario
  • H2 Government of Ontario
  • H2 Questions or comments
A+
Alt Text Quality
All 3 images OK
PASS
All 3 images OK
Info::
2 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
3 images 1 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-input-fieldinputSearchfor/id
#search-resetresetClear fieldaria-label
A
Favicon & Branding
10 icon(s) detected
PASS
10 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 22 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.

○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
●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 have a discernible name
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
○`[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
○Buttons have an accessible name
○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
○Heading elements appear in a sequentially-descending order
○`<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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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