Skip to content
https://Lakemount.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 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
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 MAIN CONTENTINFO footer

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
Heading Hierarchy
8 headings, 1 skip(s)
REVIEW
8 headings, 1 skip(s)
Warning::
Multiple H1 headings (7 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Connecting People to the Life-Changing Presence of Jesus Christ
  • H1 Sundays at Lakemount duplicate H1
  • H1 New to faith? Try Alpha duplicate H1
  • H1 Latest Sermons duplicate H1
  • H1 Get in touch duplicate H1
  • H3 Featured events skipped
  • H1 This week duplicate H1
  • H1 Featured duplicate H1

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

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

B
Alt Text Quality
8 of 16 images have issues
REVIEW
8 of 16 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
7 image(s) with generic alt text
Info::
8 image(s) with good alt text
16 images 8 good alt text 7 generic 1 missing
IssueCount
missing1 image(s)
generic7 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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Lakemount Worship Centre ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 9 fail WCAG AA
REVIEW

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

11 pass 9 fail WCAG AA 1 pass AA only
title Lakemount Worship Centre | Grimsby, Onta…
2.66:1
#000000
on
#514E6D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Join us online at 10am
2.91:1
#000000
on
#5C555D
needs 4.5:1 (normal text)
16px · top of page (header area)
span About
3.27:1
#000000
on
#635B72
needs 4.5:1 (normal text)
16px · top of page (header area)
span Our Story
3.85:1
#000000
on
#6B6589
needs 4.5:1 (normal text)
16px · above the fold
span Sundays at Lakemount
3.79:1
#000000
on
#6B6486
needs 4.5:1 (normal text)
16px · above the fold
span Staff and Leadership
4.08:1
#000000
on
#6F698C
needs 4.5:1 (normal text)
16px · above the fold
span Core Values
3.97:1
#000000
on
#6C6888
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Next Steps
3.42:1
#000000
on
#725E4B
needs 4.5:1 (normal text)
16px · above the fold
span Try Alpha
2.96:1
#000000
on
#6A5441
needs 4.5:1 (normal text)
16px · above the fold

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 Connecting People to…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Sundays at Lakemount21.00:13.0:1
#000000
#FFFFFF
Pass
h1 New to faith? Try Al…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Latest Sermons21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Get in touch21.00:13.0:1
#000000
#FFFFFF
Pass
h1 This week21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Featured21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Featured events21.00:13.0:1
#000000
#FFFFFF
Pass
title Lakemount Worship Ce…2.66:14.5:1
#000000
#514E6D
Fail
p Storm Update: Today…4.69:14.5:1
#000000
#747688
Pass
a Join us online at 10…2.91:14.5:1
#000000
#5C555D
Fail
span About3.27:14.5:1
#000000
#635B72
Fail
span Our Story3.85:14.5:1
#000000
#6B6589
Fail
span Sundays at Lakemount3.79:14.5:1
#000000
#6B6486
Fail
span Staff and Leadership4.08:14.5:1
#000000
#6F698C
Fail
span Core Values3.97:14.5:1
#000000
#6C6888
Fail
span What We Believe9.58:14.5:1
#000000
#BBABB2
Pass
span Connect7.30:14.5:1
#000000
#A99580
Pass
span Next Steps3.42:14.5:1
#000000
#725E4B
Fail
span Try Alpha2.96:14.5:1
#000000
#6A5441
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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 21 passed
PASS
90

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
Join us online (9am) a.x-anchor > div.x-anchor-content > div.x-anchor-text > span.x-anchor-text-primary
Plan your visit a.x-anchor > div.x-anchor-content > div.x-anchor-text > span.x-anchor-text-primary
Plan your visit div.x-col > div.x-text > p > a
Learn More div.x-div > div.x-text > p > a
Listen Online div.x-col > div.x-text > p > a
Contact Us div.x-col > div.x-text > p > a
View all events a.x-anchor > div.x-anchor-content > div.x-anchor-text > span.x-anchor-text-primary
Linktree a.x-anchor > div.x-anchor-content > div.x-anchor-text > span.x-anchor-text-primary
e-Bulletin a.x-anchor > div.x-anchor-content > div.x-anchor-text > span.x-anchor-text-primary
Privacy Policy div.x-col > div.x-text > p > a
Give Online div.x-col > div.x-text > p > a
54 North Service Rd Grimsby, ON L3M 1Y8 div.x-row-inner > div.x-col > div.x-text > p
Contact Us div.x-row-inner > div.x-col > div.x-text > a
Phone: 1 (905) 945-8888 div.x-row > div.x-row-inner > div.x-col > div.x-text
Request Prayer div.x-row-inner > div.x-col > div.x-text > a
©2026 Lakemount Worship Centre. All Rights Reserved. · Designed by ADS Media div.x-bar > div.e51-e4 > div.x-bar-container > div.x-text
ADS Media div.e51-e4 > div.x-bar-container > div.x-text > a

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
Featured events div.x-text > div.x-text-content > div.x-text-content-text > h3.x-text-content-text-primary

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.x-row > div.x-row-inner > div.x-col > a.x-anchor div.x-row > div.x-row-inner > div.x-col > a.x-anchor
div.x-row > div.x-row-inner > div.x-col > a.x-anchor div.x-row > div.x-row-inner > div.x-col > a.x-anchor
div.x-row > div.x-row-inner > div.x-col > a.x-anchor div.x-row > div.x-row-inner > div.x-col > a.x-anchor

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.

○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.
●`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
●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.
●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
●Identical links have the same purpose.
○`[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
○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
○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
○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.
○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