Skip to content
https://montesgendron.ca

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 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::
4 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 4 <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.
C
Heading Hierarchy
Action
31 headings, 1 skip(s)
REVIEW
31 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 33 Clapperton Street
  • H3 705-553-0111
  • H2 TRUSTED TRIAL ADVOCACY
  • H3 CRIMINAL LAW
  • H3 FAMILY LAW
  • H2 ABOUT US
  • H5 Martin Montes skipped
  • H5 Danielle Gendron
  • H2 Criminal Law
  • H3 Driving
  • H3 drugs
  • H3 Assault
  • H2 Family Law
  • H3 PROPERTY
  • H3 SEPARATION AND DIVORCE
  • H3 CHILDREN
  • H2 OUR CASES
  • H2 MGL IN THE MEDIA
  • H2 Criminal Law FAQs
  • H3 What happens at a bail hearing?
  • H3 How does the court decide whether bail will be granted?
  • H3 What is a surety?
  • H3 What conditions might be imposed on an accused person?
  • H3 Do I need to hire a lawyer for my Loved One’s bail hearing?
  • H2 Family Law FAQs
  • H3 Do spouses need to be living apart to be considered legally separated?
  • H3 How long do spouses need to be separated before they can file for a divorce?
  • H3 What is the difference between a joint divorce and an uncontested divorce?
  • H3 Can spouses settle their separation and divorce without having to go to court?
  • H3 What if my spouse and I can’t agree to terms of our separation?
  • H2 Ready to Discuss Your Case?

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

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
Form Accessibility
2 of 6 controls have issues
REVIEW
2 of 6 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="label-for-id-1">; <input type="text" id="label-for-id-9">
Info::
4 control(s) properly labeled
6 controls
4 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#form-field-input-82c0a6c4-2d3c-4711-2e9b-afd2f1207ac0-comp-m7p4r7fr6-textNamearia-label
#form-field-input-e19f8b32-daae-4c52-6322-c2e7a77e94d7-comp-m7p4r7fr6-textPhonearia-label
#form-field-input-75e89bac-f416-4915-429e-180743359592-comp-m7p4r7fr6-emailEmailaria-label
#form-field-input-6c28e837-12c0-4789-db82-0e7e7b35acc5-comp-m7p4r7fr6-textareaMessagearia-label
#label-for-id-1text(Looking for something?)placeholder only
#label-for-id-9text(Looking for something?)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" id="label-for-id-1">; <input type="text" id="label-for-id-9">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Mobile Keyboard & Autofill
Action
1/2 eligible field(s) missing autocomplete or inputmode
REVIEW
1/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" id="form-field-input-75e89bac-f416-4915-429e-180743359592-comp-m7p4r7fr6-">
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Error: Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
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::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
A
Landmark Structure
22 landmarks
PASS
22 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Site" 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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
9 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 9 all-caps heading(s)
A
Alt Text Quality
3 of 17 images have issues
PASS
3 of 17 images have issues
Warning::
3 image(s) with filename as alt text
Info::
14 image(s) with good alt text
17 images 14 good alt text 3 generic
IssueCount
filename3 image(s)
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 "form-field-input-e19f8b32-daae-4c52-6322-c2e7a77e94d7-comp-m7p4r7fr6-" should use type="tel" (currently type="text")
Field name "form-field-input-e19f8b32-daae-4c52-6322-c2e7a77e94d7-comp-m7p4r7fr6-" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
125 explicit tabindex attribute(s) checked, no anti-patterns
PASS
125 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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 93 visible text node(s) render at >= 12 CSS pixels
PASS
All 93 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
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Criminal Law15.92:13.0:1
#000000
#E0E0E1
Pass
h2 Family Law15.92:13.0:1
#000000
#E0E0E1
Pass
h2 OUR CASES15.92:13.0:1
#000000
#E0E0E1
Pass
h2 Criminal Law FAQs15.92:13.0:1
#000000
#E0E0E1
Pass
h2 Family Law FAQs15.92:13.0:1
#000000
#E0E0E1
Pass
h2 Ready to Discuss You…15.92:13.0:1
#000000
#E0E0E1
Pass
h3 CRIMINAL LAW15.92:13.0:1
#000000
#E0E0E1
Pass
h3 drugs15.92:13.0:1
#000000
#E0E0E1
Pass
h3 PROPERTY15.92:13.0:1
#000000
#E0E0E1
Pass
h3 SEPARATION AND DIVOR…15.92:13.0:1
#000000
#E0E0E1
Pass
h3 CHILDREN15.92:13.0:1
#000000
#E0E0E1
Pass
h3 What happens at a ba…15.92:13.0:1
#000000
#E0E0E1
Pass
h3 How does the court d…15.92:13.0:1
#000000
#E0E0E1
Pass
h3 What is a surety?15.92:13.0:1
#000000
#E0E0E1
Pass
h3 What conditions migh…15.92:13.0:1
#000000
#E0E0E1
Pass
h3 Do I need to hire a …15.92:13.0:1
#000000
#E0E0E1
Pass
h3 Do spouses need to b…15.92:13.0:1
#000000
#E0E0E1
Pass
h3 How long do spouses …15.92:13.0:1
#000000
#E0E0E1
Pass
h3 What is the differen…15.92:13.0:1
#000000
#E0E0E1
Pass
h3 Can spouses settle t…15.92:13.0:1
#000000
#E0E0E1
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+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 28 passed
PASS
95

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.

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
Martin Montes div#comp-m7dgit55 > div#comp-m7dg2e7p > div#comp-m7dfxj7a > h5.font_5

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#comp-kbgakxea_r_comp-lygxy3vi > div.comp-kbgakxea_r_comp-lygxy3vi-container > div#comp-kbgakxea_r_comp-m6tjj0zi > a.IT88M3 div#comp-kbgakxea_r_comp-lygxy3vi > div.comp-kbgakxea_r_comp-lygxy3vi-container > div#comp-kbgakxea_r_comp-m6tjj0zi > a.IT88M3
div.comp-m7jvyel9-container > div#comp-m7jvyelf__item1 > div#comp-m7p6wldu__item1 > a.IT88M3 div.comp-m7jvyel9-container > div#comp-m7jvyelf__item1 > div#comp-m7p6wldu__item1 > a.IT88M3
div.comp-m7jvyel9-container > div#comp-m7jvyelf__item-j9ples3e > div#comp-m7p6wldu__item-j9ples3e > a.IT88M3 div.comp-m7jvyel9-container > div#comp-m7jvyelf__item-j9ples3e > div#comp-m7p6wldu__item-j9ples3e > a.IT88M3
div.comp-lyh3dcad-container > div#comp-lyh3dcah4__item1 > div#comp-mwduremn__item1 > a.IT88M3 div.comp-lyh3dcad-container > div#comp-lyh3dcah4__item1 > div#comp-mwduremn__item1 > a.IT88M3
div.comp-m7kzxacb2-container > div#comp-m7kzxacc11__item-m7dltqgl > div#comp-mwdus7bx__item-m7dltqgl > a.IT88M3 div.comp-m7kzxacb2-container > div#comp-m7kzxacc11__item-m7dltqgl > div#comp-mwdus7bx__item-m7dltqgl > a.IT88M3
div#comp-m7p4r7fm13 > div.comp-m7p4r7fm13-container > div#comp-m7p4r7fn7 > a.IT88M3 div#comp-m7p4r7fm13 > div.comp-m7p4r7fm13-container > div#comp-m7p4r7fn7 > a.IT88M3

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
●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
●`[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.
●Select elements have associated label elements.
●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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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