Skip to content
https://www.pestauthority.com/sioux-falls-sd/

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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::
5 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 5 <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
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 4 pass AA only
title Pest Control Services in Sioux Falls | P…
1.33:1
#000000
on
#00253D
needs 4.5:1 (normal text)
16px · top of page (header area)
button Skip to Content
1.33:1
#000000
on
#00253D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Visit Mosquito Authority
2.00:1
#000000
on
#284538
needs 4.5:1 (normal text)
16px · above the fold
a Sioux Falls
1.33:1
#000000
on
#15261F
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Pest Control Service…5.39:13.0:1
#000000
#3C87BD
Pass
h2 Total Year-Round Pro…5.39:13.0:1
#000000
#3C87BD
Pass
h2 Total Protection Sta…5.39:13.0:1
#000000
#3C87BD
Pass
h2 Pest Control Built A…5.39:13.0:1
#000000
#3C87BD
Pass
h2 Pest Control Customi…5.39:13.0:1
#000000
#3C87BD
Pass
h2 Free Retreatments, B…5.39:13.0:1
#000000
#3C87BD
Pass
h2 Community-Based Serv…5.39:13.0:1
#000000
#3C87BD
Pass
h3 The Pest Authority o…5.39:13.0:1
#000000
#3C87BD
Pass
title Pest Control Service…1.33:14.5:1
#000000
#00253D
Fail
button Skip to Content1.33:14.5:1
#000000
#00253D
Fail
a Top4.54:14.5:1
#000000
#267AB6
Pass
span Looking for mosquito…4.54:14.5:1
#000000
#267AB6
Pass
a Visit Mosquito Autho…2.00:14.5:1
#000000
#284538
Fail
a Sioux Falls1.33:14.5:1
#000000
#15261F
Fail
a change location9.14:14.5:1
#000000
#BCA983
Pass
span FAQs4.79:14.5:1
#000000
#84766D
Pass
a (402) 969-47085.25:14.5:1
#000000
#8E7B78
Pass
a About Us10.30:14.5:1
#000000
#CCB0A2
Pass
a Certification Progra…9.63:14.5:1
#000000
#C2ABA0
Pass
a FAQs16.03:14.5:1
#000000
#E5DFE6
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.

C
Lighthouse Accessibility Audits
Action
Score 71/100 — 9 failing, 25 passed
REVIEW
71

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FAQs About Us Services Industries We Serve Bundles Promotions div.flx > div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FAQs nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry
About Us nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry
Services nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry
Industries We Serve nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry
Bundles nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry
Promotions nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > main#MainZone > section#CuratedReviewsF1 > a#ReviewsAnchor body > main#MainZone > section#CuratedReviewsF1 > a#ReviewsAnchor

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Map of Pest Authority of Sioux Falls, SD Services in Sioux Falls and Surroundin… div#SmFranServiceAreasV1Locations > div > figure.map > div.imap

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#CuratedReviewsF1Feed > div#Review-7830412 > div.mn_tn > button.blk div#CuratedReviewsF1Feed > div#Review-7830412 > div.mn_tn > button.blk
div#CuratedReviewsF1Feed > div#Review-7830423 > div.mn_tn > button.blk div#CuratedReviewsF1Feed > div#Review-7830423 > div.mn_tn > button.blk
div#CuratedReviewsF1Feed > div#Review-7830431 > div.mn_tn > button.blk div#CuratedReviewsF1Feed > div#Review-7830431 > div.mn_tn > button.blk
div#CuratedReviewsF1Feed > div#Review-7830421 > div.mn_tn > button.blk div#CuratedReviewsF1Feed > div#Review-7830421 > div.mn_tn > button.blk

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.flx > div.flx > div.flx > a#SmLocalHeaderV1_1 div.flx > div.flx > div.flx > a#SmLocalHeaderV1_1

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.

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
Call ul.ctas > li.cta-item-container > a.call-btn > strong
Text ul.ctas > li.cta-item-container > button.cta-button > strong.cta-label
Email ul.ctas > li.cta-item-container > button.cta-button > strong.cta-label

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FAQs div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt
About Us div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt
Services div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt
Industries We Serve div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt
Bundles div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt
Promotions div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read More li.flx > blockquote.rvw-itm > div > button.lnk-stl
Read More li.flx > blockquote.rvw-itm > div > button.lnk-stl
Read More li.flx > blockquote.rvw-itm > div > button.lnk-stl
Read More li.flx > blockquote.rvw-itm > div > button.lnk-stl
○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
●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
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●No form fields have multiple labels
●Uses ARIA roles only on compatible elements
●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 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
○`<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
○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.
○`[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.
○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.
A+
Heading Hierarchy
8 headings
PASS
8 headings
Info::
Single H1 present
  • H1 Pest Control Services in Sioux Falls
  • H2 Total Year-Round Protection for Your Family and Property
  • H3 The Pest Authority of Sioux Falls, SD Approach
  • H2 Total Protection Starts Before Pests Get Inside
  • H2 Pest Control Built Around Every Season
  • H2 Pest Control Customized to Your Needs
  • H2 Free Retreatments, Because Pests Do Not Always Stay Gone
  • H2 Community-Based Service, Authority-Level Standards
A+
Heading Text Quality
All 8 heading(s) have substantive, well-formed text
PASS
All 8 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 7 images OK
PASS
All 7 images OK
Info::
3 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
7 images 4 good alt text 3 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 7 controls have issues
PASS
1 of 7 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="GoogleAddress">
Info::
6 control(s) properly labeled
7 controls
6 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#SmLocalFormV1Form_ITM0_FirstNametextFirst Name*for/id
#SmLocalFormV1Form_ITM0_LastNametextLast Name*for/id
#SmLocalFormV1Form_ITM0_AddresstextAddressfor/id
#SmLocalFormV1Form_ITM0_PhonetelPhone*for/id
#SmLocalFormV1Form_ITM0_EmailAddressemailEmail*for/id
#SmLocalFormV1Form_ITM0_Consent_0checkboxI agree to receive recurring informational and marketing messages from Pest Authority of Sioux Falls, SD and its affiliates using an automated device at the mobile number listed above. Consent to receive messages is not a condition of any purchase or service. Message frequency may vary. Message and data rates may apply. Privacy Policy. Reply HELP for help. Reply STOP to stop.for/id
#GoogleAddresscheckbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="GoogleAddress">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+
Form Input Types
7 form control(s) checked, no type mismatches
PASS
7 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 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
6 explicit tabindex attribute(s) checked, no anti-patterns
PASS
6 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 115 visible text node(s) render at >= 12 CSS pixels
PASS
All 115 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