Skip to content
https://plunketts.net

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
10
REVIEW
3
PASS
11
INFO
0
Checks
24
11 PASS 3 REVIEW 10 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Alt Text Quality
Action
9 of 17 images have issues
FIX
9 of 17 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
17 images 7 good alt text 1 decorative 9 missing
IssueCount
missing9 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Document Language
Action
Missing <html lang> attribute (WCAG 3.1.1)
FIX
Missing <html lang> attribute (WCAG 3.1.1)
Critical::
Missing <html lang> attribute (WCAG 3.1.1)
Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.
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::
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.
D
Lighthouse Accessibility Audits
Action
Score 56/100 — 6 failing, 7 passed
FIX
56

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
Buy Online Today! body.light > div#current-banner > div.banner-view > div.title
Select your preferred arrival time. Schedule Your Appointment Right Now! div#current-banner > div.banner-view > div.body > p
Buy Now div#current-banner > div.banner-view > div.action-container > a#banner-buy-now
FOR YOUR HOME div.page-block > div.container > a.button > span
FOR YOUR BUSINESS div.page-block > div.container > a.button > span
866-906-1780 div.page-block > div.container > a.button > span
CONTACT US div.page-block > div.container > a.button > span

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
Your search for local pest control stops here. We offer pest control services f… div#834d9582-7487-4977-b170-ee130125bda8 > div.page-block > div.container > h4
Whether you’ve got a rodent problem in your restaurant or you need ant control … div#5597e76c-354b-49cb-9584-d4498421f6e8 > div.page-block > div.container > h4
There are a lot of pest control companies out there. None are as attentive and … div#3c2df838-7cba-4078-9ca2-31487c369554 > div.page-block > div.container > h4

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.crjs html.crjs

These are opportunities to improve the interpretation of your content by users in different locales.

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#logo-container > div.all-columns > a#logo > img div#logo-container > div.all-columns > a#logo > img
div.footer-badges > div.column > a > img div.footer-badges > div.column > a > img
div.footer-badges > div.column > a > img div.footer-badges > div.column > a > img
div.footer-badges > div.column > a > img div.footer-badges > div.column > a > img
div.footer-badges > div.column > a > img div.footer-badges > div.column > a > img
div.footer-badges > div.column > a > img div.footer-badges > div.column > a > img
div.footer-badges > div.column > a > img div.footer-badges > div.column > a > img

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#header-bottom > div.all-columns > div.nav-list > a.nav div#header-bottom > div.all-columns > div.nav-list > a.nav
div#header-bottom > div.all-columns > div.nav-list > a.nav div#header-bottom > div.all-columns > div.nav-list > a.nav
div#header-bottom > div.all-columns > div.nav-list > a.nav div#header-bottom > div.all-columns > div.nav-list > a.nav
div#header-bottom > div.all-columns > div.nav-list > a.nav div#header-bottom > div.all-columns > div.nav-list > a.nav
div#header-bottom > div.all-columns > div.nav-list > a.nav div#header-bottom > div.all-columns > div.nav-list > a.nav
body.light > div.footer-badges > div.column > a body.light > div.footer-badges > div.column > a
body.light > div.footer-badges > div.column > a body.light > div.footer-badges > div.column > a
body.light > div.footer-badges > div.column > a body.light > div.footer-badges > div.column > a
body.light > div.footer-badges > div.column > a body.light > div.footer-badges > div.column > a
body.light > div.footer-badges > div.column > a body.light > div.footer-badges > div.column > a
body.light > div.footer-badges > div.column > a body.light > div.footer-badges > div.column > a
div#footer > div.all-columns > div.column > a div#footer > div.all-columns > div.column > a

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.crjs html.crjs

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-hidden="true"]` is not present on the document `<body>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●Links are distinguishable without relying on color.
●Touch targets have sufficient size and spacing.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<html>` element has a valid value for its `[lang]` attribute
○`<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.
○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.
C
Heading Hierarchy
Action
17 headings, 3 skip(s)
REVIEW
17 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 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Local Pest Control & Extermination Experts Near MePlunkett's Pest Control. Over 100 Years Strong!Keeping Pests In Their Place... Not Yours
  • H2 We Provide the Best Pest Control Services in Your Area!
  • H2 Local Pest Control Near Me
  • H2 Residential Exterminators Near Me
  • H4 Your search for local pest control stops here. We offer pest control services for your home, cabin, or other residential space. We provide one-time pest control services for an existing problem as wel skipped
  • H2 Commercial Exterminators Near Me
  • H4 Whether you’ve got a rodent problem in your restaurant or you need ant control for your manufacturing line, we can solve your commercial pest problem. skipped
  • H2 Common Local Pests: Got Bugs?
  • H2 Not Sure What Bug is Bugging You? Use Our Pest ID Form!
  • H2 Service Areas: Find Pest Removal in Your Area
  • H2 Reviews: How Do I Choose Between Pest Control Companies?
  • H4 There are a lot of pest control companies out there. None are as attentive and effective as Plunkett’s! See why our customers say we’re the best local pest control company: skipped
  • H2 Ready to Get Started With Reliable & Effective Pest Control?
  • H3 Contact Us for a No-obligation Estimate!
  • H2 Now Hiring, Join Plunkett's Today!
  • H2 Frequently Asked Questions:
  • H2 Need Help with an Existing Pest Control Service?Email Client Services today!

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

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 404 Page Not Found - Plunkett's Pest Control ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 7 pass AA only
title Pest Control Minneapolis, MN & Midwest …
2.78:1
#000000
on
#275F37
needs 4.5:1 (normal text)
16px · top of page (header area)
span For Your Home
2.78:1
#000000
on
#275F37
needs 4.5:1 (normal text)
16px · top of page (header area)
span For Your Business
2.78:1
#000000
on
#275F37
needs 4.5:1 (normal text)
16px · top of page (header area)
span Pests
2.78:1
#000000
on
#275F37
needs 4.5:1 (normal text)
16px · top of page (header area)
i In Their Place
3.23:1
#000000
on
#86503D
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span Schedule Now
3.88:1
#000000
on
#5F6B7C
needs 4.5:1 (normal text)
16px · mid-page · 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 Local Pest Control N…3.75:13.0:1
#000000
#6B6764
Pass
title Pest Control Minneap…2.78:14.5:1
#000000
#275F37
Fail
span For Your Home2.78:14.5:1
#000000
#275F37
Fail
span For Your Business2.78:14.5:1
#000000
#275F37
Fail
span Pests2.78:14.5:1
#000000
#275F37
Fail
span Why Plunkett's5.65:14.5:1
#000000
#5C9242
Pass
span Locations8.53:14.5:1
#000000
#7FB449
Pass
div Request A Free Estim…8.53:14.5:1
#000000
#7FB449
Pass
span 866-906-17808.53:14.5:1
#000000
#7FB449
Pass
div Buy Online Today!8.53:14.5:1
#000000
#7FB449
Pass
p Select your preferre…7.32:14.5:1
#000000
#929E69
Pass
a Buy Now6.69:14.5:1
#000000
#9E8F7F
Pass
span Local Pest Control &…6.54:14.5:1
#000000
#9D8D7E
Pass
span Plunkett's Pest Cont…9.97:14.5:1
#000000
#C4AF9D
Pass
span Over 100 Years Stron…5.70:14.5:1
#000000
#AE7960
Pass
span Keeping Pests5.13:14.5:1
#000000
#AF6D51
Pass
i In Their Place3.23:14.5:1
#000000
#86503D
Fail
span ... Not Yours5.96:14.5:1
#000000
#948586
Pass
span Schedule Now3.88:14.5:1
#000000
#5F6B7C
Fail
span Now Hiring!7.75:14.5:1
#000000
#939EAF
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
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H1: 139 chars - H4: 200 chars - H4: 150 chars
Got: 3 >120-char heading(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/3 iframe(s) missing title; 0 placeholder(s)
PASS
1/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://16389647.fls.doubleclick.net/activityi;src=16389647;type=coxme0;cat=pag…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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 82 visible text node(s) render at >= 12 CSS pixels
PASS
All 82 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback