https://www.charlotteroofing.com/?utm_source=g-local&utm_medium=organic&utm_campaign=GMB

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 8 REVIEW 4 FIX

404 Error Page

Action

HTTP 202, bare page

FIX

HTTP 202, bare page

Unexpected status code: HTTP 202

Expected HTTP 404 but received 202. This may confuse search engine crawlers.

Got: HTTP 202

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 202 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

15 landmarks

REVIEW

15 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Heading Hierarchy

18 headings, 2 skip(s)

REVIEW

18 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Protect Your Most Valuable Asset & Those Who Live In It.
H2 OUR ROOFING CREDENTIALS
H2 Industry Leading
H2 Roofing Services
H2 request a
H2 free estimate
H2 WORK WE HAVE DONE
H2 testimonials
H4 Nancy B. skipped
H4 Davis P.
H4 Charles T.
H4 Martha R.
H4 Tim C.
H2 What is a Real Roofing Contractor?
H4 About Us skipped
H4 Join our newsletter
H4 Quick Links
H4 Contact Us

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Form Accessibility

Action

3 of 16 controls have issues

REVIEW

3 of 16 controls have issues

3 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">; <input type="submit">; <input type="submit">

13 control(s) properly labeled

16 controls

13 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
s	text	Enter your search	aria-label
input	submit	Search	aria-label
first-name	text		none
last-name	text		none
email-address	email		none
phone-number	tel		none
input	search	Services Requested Roof ReplacementRoof RepairGutter CleaningOther	none
your-message	textarea		none
#alt_s	text	Alternative:	for/id
odgnzc2591	text	WPA	none
your-email	email		none
#alt_s	text	Alternative:	for/id
odgnzc2591	text	WPA	none
input	submit	(none)	none
input	submit	(none)	none
#g-recaptcha-response	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

Iframe Accessibility

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

REVIEW

2/4 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.

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.

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

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 #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h1 Protect Your

1.12:1

#000000

#0F1214

needs 3.0:1 (large text)

32px · top of page (header area)

h1 & Those Who Live In It.

1.14:1

#000000

#111517

needs 3.0:1 (large text)

32px · above the fold

h2 OUR ROOFING CREDENTIALS

1.21:1

#000000

#161B1E

needs 3.0:1 (large text)

24px · above the fold

h2 Industry Leading

2.73:1

#000000

#39566D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Roofing Services

2.73:1

#000000

#39566D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 request a

2.73:1

#000000

#39566D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 free estimate

2.73:1

#000000

#39566D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WORK WE HAVE DONE

2.73:1

#000000

#39566D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 testimonials

2.73:1

#000000

#39566D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What is a Real Roofing Contractor?

2.73:1

#000000

#39566D

needs 3.0:1 (large text)

24px · bottom of viewport

title Professional Roofers Charlotte NC | Char…

1.39:1

#000000

#262626

needs 4.5:1 (normal text)

16px · top of page (header area)

a Call Us (704) 389-2687

1.06:1

#000000

#080A0B

needs 4.5:1 (normal text)

16px · top of page (header area)

span ✕

1.09:1

#000000

#0D0F11

needs 4.5:1 (normal text)

16px · top of page (header area)

span Request A Free Estimate

1.12:1

#000000

#0E1215

needs 4.5:1 (normal text)

16px · above the fold

p Over time we have proven ourselves to be

1.28:1

#000000

#1D2023

needs 4.5:1 (normal text)

16px · above the fold

a exceptional installers of these companie…

1.29:1

#000000

#1B2124

needs 4.5:1 (normal text)

16px · above the fold

p Home Builders

1.39:1

#000000

#222729

needs 4.5:1 (normal text)

16px · above the fold

p BBB

1.27:1

#000000

#1A2023

needs 4.5:1 (normal text)

16px · mid-page

p Charlotte’s Best 2024 winner

1.32:1

#000000

#1D2326

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Protect Your	1.12:1	3.0:1	#000000	#0F1214	Fail
h1 & Those Who Live In …	1.14:1	3.0:1	#000000	#111517	Fail
h2 OUR ROOFING CREDENTI…	1.21:1	3.0:1	#000000	#161B1E	Fail
h2 Industry Leading	2.73:1	3.0:1	#000000	#39566D	Fail
h2 Roofing Services	2.73:1	3.0:1	#000000	#39566D	Fail
h2 request a	2.73:1	3.0:1	#000000	#39566D	Fail
h2 free estimate	2.73:1	3.0:1	#000000	#39566D	Fail
h2 WORK WE HAVE DONE	2.73:1	3.0:1	#000000	#39566D	Fail
h2 testimonials	2.73:1	3.0:1	#000000	#39566D	Fail
h2 What is a Real Roofi…	2.73:1	3.0:1	#000000	#39566D	Fail
title Professional Roofers…	1.39:1	4.5:1	#000000	#262626	Fail
a Call Us (704) 389-26…	1.06:1	4.5:1	#000000	#080A0B	Fail
span ✕	1.09:1	4.5:1	#000000	#0D0F11	Fail
span Most Valuable Asset	10.00:1	4.5:1	#9EC2C9	#0E1012	Pass
span Request A Free Estim…	1.12:1	4.5:1	#000000	#0E1215	Fail
p Over time we have pr…	1.28:1	4.5:1	#000000	#1D2023	Fail
a exceptional installe…	1.29:1	4.5:1	#000000	#1B2124	Fail
p Home Builders	1.39:1	4.5:1	#000000	#222729	Fail
p BBB	1.27:1	4.5:1	#000000	#1A2023	Fail
p Charlotte’s Best 2…	1.32:1	4.5:1	#000000	#1D2326	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.

Lighthouse Accessibility Audits

Action

Score 79/100 — 7 failing, 26 passed

REVIEW

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
REQUEST A FREE ESTIMATE `div.column > div.mcb-column-inner > a.button > span.button_label`
exceptional installers of these companies' high-quality products `div.mcb-column-inner > div.column_attr > p > a`
REQUEST A FREE ESTIMATE `div.column > div.mcb-column-inner > a.button > span.button_label`
div#wpcf7-f49-p25-o1 > form.wpcf7-form > p > input.wpcf7-form-control `div#wpcf7-f49-p25-o1 > form.wpcf7-form > p > input.wpcf7-form-control`
VIEW ALL OUR WORKS `div.column > div.mcb-column-inner > a.button > span.button_label`
SEE ALL TESTIMONIALS `div.column > div.mcb-column-inner > a.button > span.button_label`
LEARN MORE `div.column > div.mcb-column-inner > a.button > span.button_label`

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
Nancy B. `div.testimonials_list > div.item > div.desc > h4.title`
About Us `div.column > div.mcb-column-inner > aside#text-2 > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
p > label > span.wpcf7-form-control-wrap > input.wpcf7-form-control `p > label > span.wpcf7-form-control-wrap > input.wpcf7-form-control`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
previous slide `div.column > div.mcb-column-inner > div.content_slider > ul.content_slider_ul`
previous slide `div.column > div.mcb-column-inner > div.content_slider > ul.content_slider_ul`

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
charlottes-best-roofer-2024 `div.slick-track > div#slick-slide00 > div > li.content_slider_li`
charlotte-roofing-gallery-1-min `div.slick-track > div#slick-slide10 > div > li.content_slider_li`

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

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 (704) 850-5813 `div.column > ul.contact_details > li.phone > a`

○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

●Input buttons have discernible text.

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●No form fields have multiple labels

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

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

○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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

○Skip links are focusable.

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

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

○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 Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 2 all-caps heading(s)

Alt Text Quality

4 of 40 images have issues

PASS

4 of 40 images have issues

4 image(s) with generic alt text

3 decorative image(s) correctly marked

33 image(s) with good alt text

40 images 33 good alt text 3 decorative 4 generic

Issue	Count
generic	4 image(s)

A+

Link & Button Quality

1 issue(s) across 70 links and 3 buttons

PASS

1 issue(s) across 70 links and 3 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.charlotteroofing.com/charlotte-roofing-contractor/ ("Learn More")

69 link(s) with descriptive text

70 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.charlotteroofing.com/charlot…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Charlotte Roofing Contractor

72 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://www.charlotteroofing.com/charlotte-roofing-contractor/ ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "s" should use type="search" (currently type="text")

Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

16 form control(s) checked, no input-semantic issues

PASS

16 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 <select>

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

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 71 visible text node(s) render at >= 12 CSS pixels

PASS

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

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

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.