Skip to content
https://www.rescueairtx.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
4
REVIEW
5
PASS
15
INFO
0
Checks
24
15 PASS 5 REVIEW 4 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
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::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
B
Iframe Accessibility
3/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://scheduler.servicetitan.com/?brandId=brand_j37aj3kfearrnp3u3sy9r5pd&api_…")
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.
Warning::
<iframe> missing title attribute (src="https://app.avoca.ai/chat?key=33&demo=false&sessionId=c6247d76-d5fe-42c5-85c2-6…")
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.
Warning::
<iframe> missing title attribute (src="javascript:false")
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.
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color Not set CSS indicators Detected

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 9 fail WCAG AA
REVIEW

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

11 pass 9 fail WCAG AA 1 pass AA only
span Call Us Today!
1.97:1
#000000
on
#1F4062
needs 4.5:1 (normal text)
16px · above the fold
a 972-201-3253
1.54:1
#000000
on
#0F2D59
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Home
1.54:1
#000000
on
#102D59
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a About Us
4.35:1
#000000
on
#5772A4
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Financing
1.30:1
#000000
on
#031F4A
needs 4.5:1 (normal text)
16px · mid-page
a Blog
1.85:1
#000000
on
#1E3C5A
needs 4.5:1 (normal text)
16px · mid-page
a Club Membership
1.55:1
#000000
on
#0F304D
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a 24 Hour Service
1.64:1
#000000
on
#143357
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Careers
2.39:1
#000000
on
#3D4876
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

6 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 Plano & Frisco HVAC …5.68:13.0:1
#000000
#7584AF
Pass
h3 Prompt, Reliable, an…5.68:13.0:1
#000000
#7584AF
Pass
title Heating & Air Condit…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip To Main Content21.00:14.5:1
#000000
#FFFFFF
Pass
p This website is Audi…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to Content21.00:14.5:1
#000000
#FFFFFF
Pass
span Google Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
span Financing21.00:14.5:1
#000000
#FFFFFF
Pass
span GET A FREE QUOTE21.00:14.5:1
#000000
#FFFFFF
Pass
span Book Now21.00:14.5:1
#000000
#FFFFFF
Pass
span Call Us Today!1.97:14.5:1
#000000
#1F4062
Fail
a 972-201-32531.54:14.5:1
#000000
#0F2D59
Fail
a Home1.54:14.5:1
#000000
#102D59
Fail
a About Us4.35:14.5:1
#000000
#5772A4
Fail
a Press Release5.94:14.5:1
#000000
#6F88BE
Pass
a Financing1.30:14.5:1
#000000
#031F4A
Fail
a Blog1.85:14.5:1
#000000
#1E3C5A
Fail
a Club Membership1.55:14.5:1
#000000
#0F304D
Fail
a 24 Hour Service1.64:14.5:1
#000000
#143357
Fail
a Careers2.39:14.5:1
#000000
#3D4876
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.

C
Lighthouse Accessibility Audits
Action
Score 73/100 — 8 failing, 27 passed
REVIEW
73

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
Home About Us Air Conditioning Heating Indoor Air Quality Plumbing Products Ser… div.flx > nav.nv > nav#MblHeaderMobileNav > 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
Home nav#MblHeaderMobileNav > ul > li.selected > a.ato
About Us nav#MblHeaderMobileNav > ul > li.flx > a.ato
Air Conditioning nav#MblHeaderMobileNav > ul > li.flx > a.ato
Heating nav#MblHeaderMobileNav > ul > li.flx > a.ato
Indoor Air Quality nav#MblHeaderMobileNav > ul > li.flx > a.ato
Plumbing nav#MblHeaderMobileNav > ul > li.flx > a.ato
Products nav#MblHeaderMobileNav > ul > li.flx > a.ato
Service Areas nav#MblHeaderMobileNav > ul > li.flx > a.ato
View Exclusive Offers nav#MblHeaderMobileNav > ul > li.flx > a.ato
Get a Free Quote nav#MblHeaderMobileNav > ul > li.flx > a.ato
Contact Us nav#MblHeaderMobileNav > ul > li.flx > a.ato

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
header#HeaderZone > form#Form_HeaderS1 > div#HeaderS1 > a header#HeaderZone > form#Form_HeaderS1 > div#HeaderS1 > a

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
Main Menu div#HeaderS1 > div > div.flx > div.mnu-btn
Open child menu of About Us nav#MblHeaderMobileNav > ul > li.flx > span.el-tab
Open child menu of Air Conditioning nav#MblHeaderMobileNav > ul > li.flx > span.el-tab
Open child menu of Heating nav#MblHeaderMobileNav > ul > li.flx > span.el-tab
Open child menu of Indoor Air Quality nav#MblHeaderMobileNav > ul > li.flx > span.el-tab
Open child menu of Plumbing nav#MblHeaderMobileNav > ul > li.flx > span.el-tab
Open child menu of Products nav#MblHeaderMobileNav > ul > li.flx > span.el-tab
Open child menu of Service Areas nav#MblHeaderMobileNav > ul > li.flx > span.el-tab

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#chat-widget > div > div > button#btn-trigger-chat div#chat-widget > div > div > button#btn-trigger-chat

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

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 Us Today! ul.third > li > div#FooterV1Tagline > span.fnt_t-6
Map & Directions li > div.flx-at-1280 > div.mrg_tp-20 > a

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
Home nav.nv > nav#MblHeaderMobileNav > ul > li.selected
About Us nav.nv > nav#MblHeaderMobileNav > ul > li.flx
Air Conditioning nav.nv > nav#MblHeaderMobileNav > ul > li.flx
Heating nav.nv > nav#MblHeaderMobileNav > ul > li.flx
Indoor Air Quality nav.nv > nav#MblHeaderMobileNav > ul > li.flx
Plumbing nav.nv > nav#MblHeaderMobileNav > ul > li.flx
Products nav.nv > nav#MblHeaderMobileNav > ul > li.flx
Service Areas nav.nv > nav#MblHeaderMobileNav > ul > li.flx
View Exclusive Offers nav.nv > nav#MblHeaderMobileNav > ul > li.flx
Get a Free Quote nav.nv > nav#MblHeaderMobileNav > ul > li.flx
Contact Us nav.nv > nav#MblHeaderMobileNav > ul > li.flx

These are opportunities to improve the experience of reading tabular or list data using 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
`[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.
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
ARIA `tooltip` elements have accessible names
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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 `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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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
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.
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.
A
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE "Accessibility options" 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

A+
Heading Hierarchy
9 headings
PASS
9 headings
Info::
Single H1 present
  • H4 Putting Our Customers First
  • H4 Contact Rescue Air and Plumbing Today!
  • H1 Air Conditioning, Heating, and Plumbing In Dallas
  • H2 Plano & Frisco HVAC Pros Available 24/7/365
  • H3 Prompt, Reliable, and Affordable Services
  • H4 How We Help You
  • H5 Helping You Handle the Weather Changes
  • H4 Customer Reviews
  • H5 Don't Just Take Our Word for It
A+
Heading Text Quality
All 9 heading(s) have substantive, well-formed text
PASS
All 9 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
3 of 18 images have issues
PASS
3 of 18 images have issues
Warning::
3 image(s) with generic alt text
Info::
9 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
18 images 6 good alt text 9 decorative 3 generic
IssueCount
generic3 image(s)
A
Form Accessibility
1 of 9 controls have issues
PASS
1 of 9 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::
8 control(s) properly labeled
9 controls
8 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#MblHeaderSiteSearch_ITM0_CsearchSearchfor/id
#ContactS1Form_ITM0_FirstNametextFirst Namefor/id
#ContactS1Form_ITM0_LastNametextLast Namefor/id
#ContactS1Form_ITM0_PhonetelPhonefor/id
#ContactS1Form_ITM0_EmailAddressemailEmailfor/id
#ContactS1Form_ITM0_AddresstextAddressfor/id
#ContactS1Form_ITM0_LeadTypeIDselectAre you a new customer?for/id
#ContactS1Form_ITM0_MessagetextHow can we help you?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
9 form control(s) checked, no type mismatches
PASS
9 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
9 form control(s) checked, no input-semantic issues
PASS
9 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
8 explicit tabindex attribute(s) checked, no anti-patterns
PASS
8 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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 34 visible text node(s) render at >= 12 CSS pixels
PASS
All 34 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 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback