Skip to content
https://www.myrescueplumbing.com/locations/mccormick-blvd-lincolnwood/

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
4
REVIEW
5
PASS
15
INFO
0
Checks
24
15 PASS 5 REVIEW 4 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
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Heading Hierarchy
Action
37 headings, 3 skip(s)
REVIEW
37 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Plumber in Lincolnwood – McCormick Blvd Office
  • H2 Serving Lincolnwood, Skokie, and Sauganash
  • H4 Location: skipped
  • H4 Address:
  • H4 Phone:
  • H4 Hours:
  • H4 Dispatching Info:
  • H4 Other Locations
  • H2 Our Lincolnwood Operations
  • H4 Residents Rescued Every Month skipped
  • H4 Neighborhoods We Proudly Serve
  • H4 Top Ranked Plumbers
  • H4 Years of combined experience
  • H2 Get a Free Estimate for Your Plumbing Needs
  • H2 Trusted by Over +1000 Chicago Homeowners Every Month
  • H2 Neighborhoods Served by Our Lincolnwood Team
  • H3 Emergency Plumbing Services
  • H4 24-Hour Plumbing Services
  • H3 Residential Plumbing Services
  • H4 Protect Your Home from Plumbing Issues
  • H3 Commercial Plumbing Services
  • H4 Safeguard Your Business
  • H3 Plumbing Repair Services in Lincolnwood
  • H4 Quality Plumbing
  • H3 Plumbing and Sewer Services
  • H4 Reliable Plumbing
  • H3 Plumbing Solutions
  • H4 Free Plumbing Estimates
  • H2 Emergency Plumbing Problem?
  • H5 Plumbing Services skipped
  • H5 Emergency Services
  • H5 Water Damage Restoration
  • H5 Chicago Locations
  • H5 Illinois Locations
  • H5 Plumbing License #055-044523
  • H5 Contact Us
  • H5 Connect With Us

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

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

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

C
Tap Target Adequacy
Action
6 tap target(s) too small or too close together
REVIEW
6 tap target(s) too small or too close together
Warning::
6 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
title Lincolnwood Plumber - McCormick Blvd Off…
3.15:1
#000000
on
#495E77
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
3.28:1
#000000
on
#4F6079
needs 4.5:1 (normal text)
16px · top of page (header area)
span Residential
3.60:1
#000000
on
#57667C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Clogged Sewer Line
3.67:1
#000000
on
#5A677C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Dishwasher Installation
3.89:1
#000000
on
#5F6B7D
needs 4.5:1 (normal text)
16px · above the fold
a Drain Cleaning
4.12:1
#000000
on
#656F7D
needs 4.5:1 (normal text)
16px · above the fold
a Faucet Repair
4.32:1
#000000
on
#6A727E
needs 4.5:1 (normal text)
16px · above the fold
a Garbage Disposal Repair
4.38:1
#000000
on
#6C737B
needs 4.5:1 (normal text)
16px · above the fold
a Leak Repair
2.21:1
#000000
on
#3C4750
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Plumbing Pipes
2.96:1
#000000
on
#5B5852
needs 4.5:1 (normal text)
16px · above the fold
a Sewer Line Repair
1.76:1
#000000
on
#303747
needs 4.5:1 (normal text)
16px · above the fold
a Shower Repair
1.94:1
#000000
on
#333E4E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 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 Get a Free Estimate …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by Over +100…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Emergency Plumbing P…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Emergency Plumbing S…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Residential Plumbing…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Commercial Plumbing …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Plumbing and Sewer S…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Plumbing Solutions21.00:13.0:1
#000000
#FFFFFF
Pass
title Lincolnwood Plumber …3.15:14.5:1
#000000
#495E77
Fail
a Skip to content3.28:14.5:1
#000000
#4F6079
Fail
span Residential3.60:14.5:1
#000000
#57667C
Fail
a Clogged Sewer Line3.67:14.5:1
#000000
#5A677C
Fail
a Dishwasher Installat…3.89:14.5:1
#000000
#5F6B7D
Fail
a Drain Cleaning4.12:14.5:1
#000000
#656F7D
Fail
a Faucet Repair4.32:14.5:1
#000000
#6A727E
Fail
a Garbage Disposal Rep…4.38:14.5:1
#000000
#6C737B
Fail
a Leak Repair2.21:14.5:1
#000000
#3C4750
Fail
a Plumbing Pipes2.96:14.5:1
#000000
#5B5852
Fail
a Sewer Line Repair1.76:14.5:1
#000000
#303747
Fail
a Shower Repair1.94:14.5:1
#000000
#333E4E
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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #main
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+
Heading Text Quality
All 37 heading(s) have substantive, well-formed text
PASS
All 37 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
1 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
11 images 10 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#kb_field_38139_094ec0-4d_0textYour Name*for/id
#kb_field_38139_094ec0-4d_1emailEmail Address*for/id
#kb_field_38139_094ec0-4d_2textSubjectfor/id
#kb_field_38139_094ec0-4d_3textareaMessage*for/id
#kb_field_19238_12318a-8d_0textName*for/id
#kb_field_19238_12318a-8d_1emailEmail*for/id
#kb_field_19238_12318a-8d_2textPhone*for/id
#kb_field_19238_12318a-8d_3selectWhat is Your Plumbing Emergency?*for/id
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 "kb_field_2" should use type="tel" (currently type="text")
Field name "kb_field_2" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
A+
Form Input Quality
8 form control(s) checked, no input-semantic issues
PASS
8 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-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A
Tabindex Anti-Patterns
0 positive, 3 -1-on-focusable
PASS
0 positive, 3 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="kt-scroll-up">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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+
Mobile-Readable Font Sizes
All 245 visible text node(s) render at >= 12 CSS pixels
PASS
All 245 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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 Search ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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 95/100 — 2 failing, 25 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
Location: div.kt-row-column-wrap > div.wp-block-kadence-column > div.kt-inside-inner-col > h4.kt-adv-heading38139_d837fc-e7
Residents Rescued Every Month div.wp-block-kadence-column > div.kt-inside-inner-col > div.wp-block-kadence-countup > h4.kb-count-up-title
Plumbing Services div.kt-row-column-wrap > div.wp-block-kadence-column > div.kt-inside-inner-col > h5.kt-adv-heading27568_57bfa6-64

These are opportunities to improve keyboard navigation in your application.

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
📍 div.wp-block-kadence-column > div.kt-inside-inner-col > div.kt-adv-heading27568_bc9a43-d3 > a
📍 div.wp-block-kadence-column > div.kt-inside-inner-col > div.kt-adv-heading27568_dd3a23-0d > a
📍 div.wp-block-kadence-column > div.kt-inside-inner-col > div.kt-adv-heading27568_3cce09-26 > a
📍 div.wp-block-kadence-column > div.kt-inside-inner-col > div.kt-adv-heading27568_a54dec-fd > a
📍 div.wp-block-kadence-column > div.kt-inside-inner-col > div.kt-adv-heading27568_bfd9aa-eb > a
📍 div.wp-block-kadence-column > div.kt-inside-inner-col > div.kt-adv-heading27568_b80d53-02 > 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
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○No element has a `[tabindex]` value greater than 0
○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