Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 2 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA 1 pass AA only

h1 Reliable AC Repair, Maintenance, & Insta…

1.69:1

#000000

#003174

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Residential HVAC Repair

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Commercial HVAC Repair

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Emergency HVAC Repair

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get A Quote

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Expert HVAC Services in North Texas

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trusted HVAC Services Near Princeton, TX

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 24/7 Emergency HVAC Repair When You Need…

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Areas We Serve in North Texas

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Schedule Your HVAC Service Today!

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Blog

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact Info

1.69:1

#000000

#003174

needs 3.0:1 (large text)

24px · bottom of viewport

span Air Conditioning

1.37:1

#000000

#282608

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a AC Installation

1.81:1

#000000

#383A29

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a AC Repair

2.55:1

#000000

#4B4F55

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

3 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)

Element	Ratio	Required	FG	BG	Result
h1 Reliable AC Repair, …	1.69:1	3.0:1	#000000	#003174	Fail
h2 Residential HVAC Rep…	1.69:1	3.0:1	#000000	#003174	Fail
h2 Commercial HVAC Repa…	1.69:1	3.0:1	#000000	#003174	Fail
h2 Emergency HVAC Repai…	1.69:1	3.0:1	#000000	#003174	Fail
h2 Get A Quote	1.69:1	3.0:1	#000000	#003174	Fail
h2 Expert HVAC Services…	1.69:1	3.0:1	#000000	#003174	Fail
h2 Trusted HVAC Service…	1.69:1	3.0:1	#000000	#003174	Fail
h2 24/7 Emergency HVAC …	1.69:1	3.0:1	#000000	#003174	Fail
h2 Areas We Serve in No…	1.69:1	3.0:1	#000000	#003174	Fail
h2 Schedule Your HVAC S…	1.69:1	3.0:1	#000000	#003174	Fail
h2 Blog	1.69:1	3.0:1	#000000	#003174	Fail
h2 Contact Info	1.69:1	3.0:1	#000000	#003174	Fail
title Texas AC Services \| …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span (469) 905-2665	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Request Service	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	6.21:1	4.5:1	#000000	#8C8D7B	Pass
span Air Conditioning	1.37:1	4.5:1	#000000	#282608	Fail
a AC Installation	1.81:1	4.5:1	#000000	#383A29	Fail
a AC Repair	2.55:1	4.5:1	#000000	#4B4F55	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

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

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 Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 Reliable AC Repair, Maintenance, & Installation
H2 Residential HVAC Repair
H2 Commercial HVAC Repair
H2 Emergency HVAC Repair
H2 Get A Quote
H2 Expert HVAC Services in North Texas
H3 Air Conditioning Repair
H3 Heating Repair
H3 HVAC Installation
H3 Emergency HVAC
H3 Preventative Maintenance
H3 Duct Cleaning
H3 Indoor Air Quality
H3 Commercial HVAC
H2 Trusted HVAC Services Near Princeton, TX
H2 24/7 Emergency HVAC Repair When You Need It Most
H2 Areas We Serve in North Texas
H2 Schedule Your HVAC Service Today!
H2 Blog
H2 Contact Info

A+

Heading Text Quality

All 20 heading(s) have substantive, well-formed text

PASS

All 20 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

4 image(s) with good alt text

4 images 4 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 7 controls have issues

PASS

1 of 7 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

6 control(s) properly labeled

7 controls

6 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#input_1_6	text	URL	for/id
#input_1_3_3	text	First	for/id
#input_1_3_6	text	Last	for/id
#input_1_5	email	Email*	for/id
#input_1_4	tel	Phone*	for/id
#input_1_1	textarea	How Can We Help You?	for/id
#g-recaptcha-response-100000	textarea	(none)	none

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

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

Link & Button Quality

84 links, 12 buttons — all OK

PASS

84 links, 12 buttons — all OK

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://localleap.com; https://www.facebook.com/profile.php?id=100095435401252; https://x.com/TexasACServices; https://www.instagram.com/txacpro; https://www.google.com/maps/place/Texas+AC+Services/@33.4692194,-96.5810855,1…; https://www.youtube.com/@TexasACServices; https://www.linkedin.com/company/texas-ac-services/

77 link(s) with descriptive text

84 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://localleap.com	Local Leap Marketing	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/TexasACServices	X	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/txacpro	Instagram	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps/place/Texas+…	Google Reviews	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@TexasACServices	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/texas-a…	Linkedin	new tab	Add '(opens in new tab)' to text

89 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://localleap.com; https://www.facebook.com/profile.php?id=100095435401252; https://x.com/TexasACServices; https://www.instagram.com/txacpro; https://www.google.com/maps/place/Texas+AC+Services/@33.4692194,-96.5810855,1…; https://www.youtube.com/@TexasACServices; https://www.linkedin.com/company/texas-ac-services/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

7 form control(s) checked, no type mismatches

PASS

7 form control(s) checked, no type mismatches

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

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.)

Iframe Accessibility

1/2 iframe(s) missing title; 0 placeholder(s)

PASS

1/2 iframe(s) missing title; 0 placeholder(s)

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 96 visible text node(s) render at >= 12 CSS pixels

PASS

All 96 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Scroll to top ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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 97/100 — 2 failing, 26 passed

PASS

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
CALL US TODAY! `div.wp-block-kadence-infobox > a.kt-blocks-info-box-link-wrap > div.kt-infobox-textcontent > p.kt-blocks-info-box-title`

These are opportunities to improve the legibility of your content.

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
CALL US TODAY! (469) 905-2665 `div.wp-block-kadence-column > div.kt-inside-inner-col > div.wp-block-kadence-infobox > a.kt-blocks-info-box-link-wrap`

○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

●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 are distinguishable without relying on color.

●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

●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

○`[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

○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.

○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.