Skip to content
https://smartscan.tools/scan?id=bdeba2a2-6f71-403e-ad56-24f3bfcc7857

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
4
PASS
15
INFO
0
Checks
24
15 PASS 4 REVIEW 5 FIX
D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" id="feedback-email">
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="feedback-email">
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #0d9488
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 ModePartial Dark Mode
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::
1 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 1 <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
Heading Hierarchy
3 headings
REVIEW
3 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Extracting Data...
  • H3 ✅ Extraction Complete
  • H3 Extraction Failed

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea id="feedback-msg">; <input type="email" id="feedback-email">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#feedback-msgtextarea(Describe what you were looking for or what went wrong...)placeholder only
#feedback-emailemail(Your email (optional, for follow-up))placeholder only

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

<textarea id="feedback-msg">; <input type="email" id="feedback-email">

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-Readable Font Sizes
Action
82% of visible text renders at >= 12 CSS px (33 below threshold)
REVIEW
82% of visible text renders at >= 12 CSS px (33 below threshold)
Warning::
33 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 10.0px ("Scanning"); <button> 10.5px ("📋 Copy"); <span> 10.0px ("shared inbox"); <span> 11.0px ("Category"); <span> 11.0px ("Language").
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV 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
All 3 heading(s) have substantive, well-formed text
PASS
All 3 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: SmartScan
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name SmartScan ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name SmartScan Display Mode standalone Theme Color #0d9488 Background Color #0f172a Icons 2 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
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
h3 Extracting Data...19.25:13.0:1
#000000
#F3F5FA
Pass
h3 ✅ Extraction Compl…19.25:13.0:1
#000000
#F3F5FA
Pass
h3 Extraction Failed19.25:13.0:1
#000000
#F3F5FA
Pass
title jmpplumbingservices.…19.42:14.5:1
#000000
#F4F6FB
Pass
span SmartScan19.42:14.5:1
#000000
#F4F6FB
Pass
a Features19.42:14.5:1
#000000
#F4F6FB
Pass
a FAQ19.25:14.5:1
#000000
#F3F5FA
Pass
button English19.25:14.5:1
#000000
#F3F5FA
Pass
button Deutsch19.25:14.5:1
#000000
#F3F5FA
Pass
button العربية19.42:14.5:1
#000000
#F4F6FB
Pass
button हिन्दी19.42:14.5:1
#000000
#F4F6FB
Pass
button Русский19.25:14.5:1
#000000
#F3F5FA
Pass
button Español19.25:14.5:1
#000000
#F3F5FA
Pass
button Português19.25:14.5:1
#000000
#F3F5FA
Pass
button Français19.25:14.5:1
#000000
#F3F5FA
Pass
button Türkçe19.25:14.5:1
#000000
#F3F5FA
Pass
span 🌙19.25:14.5:1
#000000
#F3F5FA
Pass
a Login19.25:14.5:1
#000000
#F3F5FA
Pass
a Sign Up19.25:14.5:1
#000000
#F3F5FA
Pass
button ☰19.25:14.5:1
#000000
#F3F5FA
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 — 1 failing, 19 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.

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
SCANNING div#scan-header > div.scan-header-row > div.scan-url-block > div.scan-url-label
+ New Scan div#scan-header > div.scan-header-row > div.scan-actions > a#new-scan-btn
📇 Contacts CSV main.main > section#results-section > div.results-header > button#csv-btn
Create Free Account → main.main > section#results-section > div#guest-upgrade-cta > a.btn
✉️ 1 section#results-section > div#summary-grid > div.summary-item > span.summary-count
Emails section#results-section > div#summary-grid > div.summary-item > span.summary-label
📑 32 section#results-section > div#summary-grid > div.summary-item > span.summary-count
Headings section#results-section > div#summary-grid > div.summary-item > span.summary-label
🔬 9 section#results-section > div#summary-grid > div.summary-item > span.summary-count
Tech Stack section#results-section > div#summary-grid > div.summary-item > span.summary-label
admin@jmpps.net div#panel-emails > div.preview-list > div.preview-row > a
shared inbox div#panel-emails > div.preview-list > div.preview-row > span
plumbing div#panel-ai-insights > div.ai-insights-content > div.ai-keywords-row > span.ai-keyword-chip
McKinney div#panel-ai-insights > div.ai-insights-content > div.ai-keywords-row > span.ai-keyword-chip
drain cleaning div#panel-ai-insights > div.ai-insights-content > div.ai-keywords-row > span.ai-keyword-chip
water heater div#panel-ai-insights > div.ai-insights-content > div.ai-keywords-row > span.ai-keyword-chip
sewer repair div#panel-ai-insights > div.ai-insights-content > div.ai-keywords-row > span.ai-keyword-chip
HEADINGS section#results-section > div#preview-section > div#panel-text > div.preview-subtitle
H3 Woman Owned. Family Run. div#preview-section > div#panel-text > div.headings-list > div.heading-item
H3 Flat Pricing. Trip Fee Waived on Repair. div#preview-section > div#panel-text > div.headings-list > div.heading-item
H3 Licensed. Insured. Accountable. div#preview-section > div#panel-text > div.headings-list > div.heading-item
9 technologies detected across 6 categories section#results-section > div#preview-section > div#panel-techstack > div
CMS div#panel-techstack > div > div > div
WordPress div > div > div > span
v4.0.7 div > div > div > span
FRAMEWORK div#panel-techstack > div > div > div
jQuery div > div > div > span
ANALYTICS div#panel-techstack > div > div > div
Google Analytics 4 div > div > div > span
Google Tag Manager div > div > div > span
Fathom div > div > div > span
ADVERTISING div#panel-techstack > div > div > div
Meta Pixel div > div > div > span
FONTS div#panel-techstack > div > div > div
Adobe Fonts div > div > div > span
Font Awesome div > div > div > span
MAPS div#panel-techstack > div > div > div
Google Maps div > div > div > span
⚠️ High broken link rate often means the page links to social media, mobile-app … section#results-section > div#preview-section > div#panel-broken-links > div
https://jmpplumbingservices.com div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/ div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/about-us/ div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/bathroom-plumbing-mckinney-tx/ div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/blog/ div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/careers/ div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/commercial-plumber-mckinney-tx/ div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/contact-us/ div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/drain-cleaning-mckinney-tx/ div#panel-broken-links > div > div > span
https://jmpplumbingservices.com/frisco-plumber/ div#panel-broken-links > div > div > span
Register Free → main.main > section#results-section > div#crawl-upsell-strip > a.btn
📇 Contacts CSV main.main > section#results-section > div.results-actions > button#csv-btn-bottom
Find warm leads → section#results-section > div#sc-cta-results > div > a.btn
Tell us what was missing — we'll try to fix it. main.main > section#results-section > div#scan-feedback-block > p
Send feedback section#results-section > div#scan-feedback-block > div > button#feedback-submit

These are opportunities to improve the legibility of your content.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●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.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○Identical links have the same purpose.
○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