Skip to content
https://youradchoices.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 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
No navigation patterns
FIX
No navigation patterns
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 6 <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.
B
Landmark Structure
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
6 of 6 <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 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

B
Alt Text Quality
9 of 13 images have issues
REVIEW
9 of 13 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
8 image(s) with filename as alt text
Info::
1 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
13 images 3 good alt text 1 decorative 8 generic 1 missing
IssueCount
missing1 image(s)
filename8 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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

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

17 pass 3 fail WCAG AA
title AdChoices in Canada - Learn about the bl…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span About the Program
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Tools
3.68:1
#000000
on
#436D75
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

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 What is9.17:13.0:1
#000000
#70B6C3
Pass
h1 Interest-Based Adver…9.17:13.0:1
#000000
#70B6C3
Pass
h1 The Icon and9.17:13.0:1
#000000
#70B6C3
Pass
h1 How It Works9.17:13.0:1
#000000
#70B6C3
Pass
h1 Managing9.17:13.0:1
#000000
#70B6C3
Pass
h1 What You Share9.17:13.0:1
#000000
#70B6C3
Pass
h2 All advertising seek…9.17:13.0:1
#000000
#70B6C3
Pass
h2 When you see the blu…9.17:13.0:1
#000000
#70B6C3
Pass
h2 Serving online ads b…9.17:13.0:1
#000000
#70B6C3
Pass
h2 The AdChoices icon i…9.17:13.0:1
#000000
#70B6C3
Pass
h2 In Canada, you have …9.17:13.0:1
#000000
#70B6C3
Pass
h2 Through the AdChoice…9.17:13.0:1
#000000
#70B6C3
Pass
h2 Companies registered…9.17:13.0:1
#000000
#70B6C3
Pass
h2 Digital Advertising …9.17:13.0:1
#000000
#70B6C3
Pass
h2 Associations of DAAC9.17:13.0:1
#000000
#70B6C3
Pass
h2 Associations de DAAC9.17:13.0:1
#000000
#70B6C3
Pass
h2 Subscribe to the DAA…9.17:13.0:1
#000000
#70B6C3
Pass
title AdChoices in Canada …1.00:14.5:1
#000000
#000000
Fail
span About the Program1.00:14.5:1
#000000
#000000
Fail
a Tools3.68:14.5:1
#000000
#436D75
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
Warning::
Multiple H1 headings (7 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 What is Interest-Based Advertising?
  • H2 All advertising seeks to show the right products to the right audience at the right time.
  • H1 Why am I seeing that blue icon? duplicate H1
  • H2 When you see the blue triangular icon in ads or on websites and apps, it is meant to alert and inform you that interest-based advertising data is being collected or used on that device.
  • H1 How Your Information is Used duplicate H1
  • H2 Serving online ads based on predicted interests relies on recognizing cookies stored by web browsers, advertising IDs set on mobile devices, or token identifiers.
  • H1 The Icon and How It Works duplicate H1
  • H2 The AdChoices icon is there to inform you that data is being collected or used for interest-based advertising on your device by a company.
  • H1 The Icon is Your Beacon duplicate H1
  • H2 In Canada, you have privacy rights that companies need to adhere to - and that’s why you see the blue icon - it’s there to inform and empower you to take control.
  • H1 Managing What You Share duplicate H1
  • H2 Through the AdChoices self-regulatory program, you can opt out of interest-based advertising and report any issues with it.
  • H1 Report a Complaint duplicate H1
  • H2 Companies registered in the AdChoices self-regulatory program are held accountable.
  • H2 Digital Advertising Alliance of Canada
  • H2 Associations of DAAC
  • H2 Associations de DAAC
  • H2 Subscribe to the DAAC Newsletter

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

A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#email-yui_3_17_2_1_1757428862302_10722-fieldemailEmail Addressfor/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

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 AdChoices in Canada Custom Styling Navigation Homepage Link Search Form
A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 22 passed
PASS
91

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.intrinsic > div.intrinsic-inner > div#yui_3_17_2_1_1776805156864_408 > img.loaded div.intrinsic > div.intrinsic-inner > div#yui_3_17_2_1_1776805156864_408 > img.loaded

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.

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
Association of Canadian Advertisers div.sqs-block-content > div.sqs-html-content > p > a
Canadian Marketing Association div.sqs-block-content > div.sqs-html-content > p > a
Institute of Canadian Agencies div.sqs-block-content > div.sqs-html-content > p > a
Association canadienne des annonceurs div.sqs-block-content > div.sqs-html-content > p > a
Association canadienne du marketing div.sqs-block-content > div.sqs-html-content > p > a
Canadian Media Directors' Council div.sqs-block-content > div.sqs-html-content > p > a

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
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
ARIA attributes are used as specified for the element's role
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
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
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 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
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.

Send Feedback