Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 4 REVIEW 3 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

9 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 9 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Landmark Structure

Action

12 landmarks

REVIEW

12 landmarks

No <main> landmark found

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

9 <nav> landmark(s) found

7 of 9 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

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

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

Form Accessibility

Action

6 of 24 controls have issues

REVIEW

6 of 24 controls have issues

6 control(s) without accessible label

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

Got: <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

18 control(s) properly labeled

24 controls

18 labeled

0 placeholder only

6 unlabeled

Control	Type	Label	Method
#query	text	Search	for/id
#find_yes	radio		none
#find_no	radio		none
#find_very_dissatisfied	radio		none
#find_dissatisfied	radio		none
#find_neutral	radio		none
#find_satisfied	radio		none
#find_very_satisfied	radio		none
#issue_broken	checkbox		none
#issue_typo	checkbox		none
#issue_difficult	checkbox		none
#issue_outdated	checkbox		none
#issue_technical	checkbox		none
#issue_pdf	checkbox		none
#issue_aoda	checkbox		none
#issue_other	checkbox		none
#issue_specify	textarea	Please specify. Do not include personal information, such as email address or date of birth.	for/id
select	select	Widget Language Translate	aria-label
#goog-gt-votingInputSrcLang	text	(none)	none
#goog-gt-votingInputTrgLang	text	(none)	none
#goog-gt-votingInputSrcText	text	(none)	none
#goog-gt-votingInputTrgText	text	(none)	none
#goog-gt-votingInputVote	text	(none)	none
#g-recaptcha-response-100000	textarea	(none)	none

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

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 1 pass AA only

button I want to...

2.75:1

#000000

#165788

needs 4.5:1 (normal text)

16px · top of page (header area)

span Navigation Menu

2.75:1

#000000

#165788

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Home Carousel	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What's New	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 I want to...	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Community Environmen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Declarations Due Soo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Affordable Golf	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Ontario Fire Code Ch…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Did you find what yo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How satisfied are yo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Did you encounter an…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Apply	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pay	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Register	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Report	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Request	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title City of Toronto	15.91:1	4.5:1	#000000	#E0E0E0	Pass
span Skip to content	6.60:1	4.5:1	#000000	#6B95B6	Pass
button I want to...	2.75:1	4.5:1	#000000	#165788	Fail
span Navigation Menu	2.75:1	4.5:1	#000000	#165788	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+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

1 empty heading(s)

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

H1 (empty)
H2 Home Carousel
H2 What's New
H3 Community Environment Days
H3 Declarations Due Soon
H3 Affordable Golf
H3 Ontario Fire Code Changes
H2 Services
H2 Page Feedback
H3 Did you find what you were looking for?
H3 How satisfied are you with the information on this page?
H3 Did you encounter any of the following issues on this page? Select all that apply. (Optional)
H2 I want to...
H3 Apply
H3 Pay
H3 Register
H3 Report
H3 Request

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

A+

Alt Text Quality

All 23 images OK

PASS

All 23 images OK

8 decorative image(s) correctly marked

15 image(s) with good alt text

23 images 15 good alt text 8 decorative

All images have appropriate alt text.

Link & Button Quality

1 issue(s) across 128 links and 24 buttons

PASS

1 issue(s) across 128 links and 24 buttons

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://translate.google.com

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#query-search

127 link(s) with descriptive text

128 links

0 empty

0 generic text

1 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.toronto.ca/home/social-media…	VIEW ALL Toronto.ca so…	img no alt	Add alt attribute to the image
https://translate.google.com	Translate	new tab	Add '(opens in new tab)' to text
#header	Back to Top	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label

150 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://translate.google.com

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button#query-search

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found – City of Toronto ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://www.toronto.ca/wp-content/themes/cot/print.css

Print Stylesheet ✓ Print Optimized

Print stylesheet https://www.toronto.ca/wp-content/themes/cot/print.css ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 22 passed

PASS

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
© City of Toronto 1998 - 2026 `div > div.container-fluid > p > a`
Privacy `div > div.container-fluid > p > a`
Accessibility at the City of Toronto `div > div.container-fluid > p > a`

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.hydrated `html.hydrated`

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-*]` 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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[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

○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

○`<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.

○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.

○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.