Skip to content
https://otpp.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
5
REVIEW
4
PASS
15
INFO
0
Checks
24
15 PASS 4 REVIEW 5 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
153 headings
REVIEW
153 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H5 About
  • H5 Our story
  • H5 Our purpose and strategy
  • H5 Our history
  • H5 Join us
  • H5 Our locations
  • H5 Our leadership
  • H5 Our plan
  • H5 Governance
  • H5 Our board
  • H5 Funding
  • H5 Funding valuations
  • H5 Our impact
  • H5 Our results
  • H5 2025 Annual Results
  • H5 2026 Annual Meeting
  • H5 Report Archive
  • H5 Investor relations
  • H5 News & insights
  • H5 News Releases
  • H5 Global perspectives
  • H5 Portfolio insights
  • H5 Investments
  • H5 Our advantage
  • H5 Our global presence
  • H5 Americas
  • H5 Europe, Middle East and Africa
  • H5 Asia-Pacific
  • H5 Our performance and track record
  • H5 Our benchmarks
  • H5 Major investments
  • H5 Our portfolio
  • H5 Tax strategy
  • H5 Liquidity
  • H5 Our investments
  • H5 Capital Markets
  • H5 Equities
  • H5 Private Capital
  • H5 Infrastructure & Natural Resources
  • H5 Infrastructure
  • H5 Natural Resources
  • H5 Real Estate
  • H5 Teachers’ Venture Growth
  • H5 TVG insights
  • H5 Our global team
  • H5 Capital Markets
  • H5 Equities
  • H5 Infrastructure & Natural Resources
  • H5 Portfolio Solutions
  • H5 Strategy & Stakeholder Relations
  • H5 Real Estate
  • H5 Teachers' Venture Growth
  • H5 Total Fund Management
  • H5 Regional Teams
  • H5 Asia-Pacific
  • H5 Europe, Middle East and Africa
  • H5 Sustainable Investing
  • H5 Reports, research and comments library
  • H5 Corporate governance
  • H5 Our climate strategy
  • H5 Members
  • H5 Your account
  • H5 Review your pension
  • H5 Update your profile
  • H5 Access the Document Centre
  • H5 Life events
  • H5 Learning about the plan
  • H5 Defined benefit pensions
  • H5 Life's unexpected events
  • H5 Transfer past service
  • H5 Working less than full time
  • H5 Your rights, obligations and appeals process
  • H5 Taking time off work
  • H5 Impact of buying back
  • H5 Cost and payment options
  • H5 Taxes and timing
  • H5 Changing a spousal relationship
  • H5 Are you working?
  • H5 Are you retired?
  • H5 Pre-2012 separation agreements
  • H5 Planning for loved ones
  • H5 If you die before you retire
  • H5 Choosing your survivor pension
  • H5 If you die after you retire
  • H5 Marrying after retirement
  • H5 In the event of your death
  • H5 Quitting teaching
  • H5 Pension benefit options
  • H5 Facing a terminal illness
  • H5 Living in retirement
  • H5 What is considered re-employment
  • H5 Your re-employment limit
  • H5 Re-employment scenarios
  • H5 CPP and your pension
  • H5 Your inflation adjustment
  • H5 Your monthly deposit
  • H5 Filing your income taxes
  • H5 Designating a power of attorney
  • H5 Facing a shortened life expectancy
  • H5 Preparing to retire
  • H5 Do your research
  • H5 Types of pensions
  • H5 Adjustments to your pension
  • H5 Figure out how much you'll need
  • H5 Looking after loved ones
  • H5 Medical and dental insurance
  • H5 Learn about re-employment
  • H5 Pension calculator
  • H5 Start prepping
  • H5 Required documents
  • H5 Review your checklist
  • H5 Your pension application
  • H5 News
  • H5 Plan updates and news
  • H5 Tools & resources
  • H5 Calculators and tools
  • H5 FAQs
  • H5 Working member FAQs
  • H5 Retired member FAQs
  • H5 Resource Centre and forms
  • H5 Working member resources
  • H5 Retired member resources
  • H5 Your pension at work
  • H5 Glossary
  • H5 Participating employers
  • H5 External resources
  • H5 Member Help Centre
  • H5 Careers
  • H5 Life at Teachers'
  • H5 Diversity, equity and inclusion
  • H5 Benefits and wellbeing
  • H5 Meet our team
  • H5 Audit Services
  • H5 Corporate Affairs
  • H5 Enterprise Operations & IT
  • H5 Finance
  • H5 Investments
  • H5 Member Services
  • H5 People & Culture
  • H5 Risk
  • H5 Strategy & Stakeholder Relations
  • H5 Early Talent
  • H5 Interns
  • H5 New graduates
  • H5 How we hire
  • H5 Hiring process
  • H5 Search jobs
  • H5 Join our Talent Community
  • H2 News
  • H2 Insights
  • H2 Our investment approach
  • H2 Our story
  • H2 Our culture

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

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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page not found Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
8 icon(s) detected
REVIEW
8 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 Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 News
1.13:1
#000000
on
#240B15
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Insights
1.13:1
#000000
on
#240B15
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Our investment approach
1.13:1
#000000
on
#240B15
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Our story
1.13:1
#000000
on
#240B15
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Our culture
1.13:1
#000000
on
#240B15
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
title Investing to make a mark
1.13:1
#000000
on
#240B14
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.66:1
#000000
on
#3E2F35
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a About
3.29:1
#000000
on
#5F5F5F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Investments
1.35:1
#000000
on
#242424
needs 4.5:1 (normal text)
16px · top of page (header area)
a Members
1.34:1
#000000
on
#232324
needs 4.5:1 (normal text)
16px · above the fold
a Careers
1.25:1
#000000
on
#1D1D1D
needs 4.5:1 (normal text)
16px · above the fold
span English
1.27:1
#000000
on
#1F1F1F
needs 4.5:1 (normal text)
16px · above the fold
a Français
1.34:1
#000000
on
#232323
needs 4.5:1 (normal text)
16px · above the fold
span Member login
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
a Your pension
1.27:1
#000000
on
#1F1F1F
needs 4.5:1 (normal text)
16px · above the fold
a Your profile
1.20:1
#000000
on
#19191A
needs 4.5:1 (normal text)
16px · above the fold
a Sign out
1.06:1
#000000
on
#0B0A0C
needs 4.5:1 (normal text)
16px · above the fold
a Register
4.31:1
#000000
on
#717173
needs 4.5:1 (normal text)
16px · above the fold
span Menu
1.60:1
#000000
on
#3C2C33
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span Member login
1.13:1
#000000
on
#240B15
needs 4.5:1 (normal text)
16px · mid-page

7 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 News1.13:13.0:1
#000000
#240B15
Fail
h2 Insights1.13:13.0:1
#000000
#240B15
Fail
h2 Our investment appro…1.13:13.0:1
#000000
#240B15
Fail
h2 Our story1.13:13.0:1
#000000
#240B15
Fail
h2 Our culture1.13:13.0:1
#000000
#240B15
Fail
title Investing to make a …1.13:14.5:1
#000000
#240B14
Fail
a Skip to content1.66:14.5:1
#000000
#3E2F35
Fail
a About3.29:14.5:1
#000000
#5F5F5F
Fail
a Investments1.35:14.5:1
#000000
#242424
Fail
a Members1.34:14.5:1
#000000
#232324
Fail
a Careers1.25:14.5:1
#000000
#1D1D1D
Fail
span English1.27:14.5:1
#000000
#1F1F1F
Fail
a Français1.34:14.5:1
#000000
#232323
Fail
span Member login1.32:14.5:1
#000000
#222222
Fail
a Your pension1.27:14.5:1
#000000
#1F1F1F
Fail
a Your profile1.20:14.5:1
#000000
#19191A
Fail
a Sign out1.06:14.5:1
#000000
#0B0A0C
Fail
a Register4.31:14.5:1
#000000
#717173
Fail
span Menu1.60:14.5:1
#000000
#3C2C33
Fail
span Member login1.13:14.5:1
#000000
#240B15
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+
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "primary menu" MAIN ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer
A+
Heading Text Quality
All 153 heading(s) have substantive, well-formed text
PASS
All 153 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
5 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
8 images 3 good alt text 5 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#op-header__search--inputtextEnter your search termaria-label
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
413 explicit tabindex attribute(s) checked, no anti-patterns
PASS
413 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 2 visible text node(s) render at >= 12 CSS pixels
PASS
All 2 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 31 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
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.
`button`, `link`, and `menuitem` elements have accessible names
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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