Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 1 <nav> element(s)

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

No contentinfo (footer) landmark

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

9 headings, 2 skip(s)

REVIEW

9 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

H1 Experience You Can Trust
H2 Raptor Email Security
H2 cPanel Hosting + Raptor Email Security
H2 IT & Phishing Prevention Training
H2 Client Reviews
H2 Need More Information?
H5 Company skipped
H2 Resources
H5 Get in Touch skipped

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

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - PCCC ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h1 Experience You Can Trust

1.80:1

#000000

#293A4A

needs 3.0:1 (large text)

32px · mid-page

title Industry Leading Computer IT Support | P…

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Services

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Raptor Email Security

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Phishing Prevention Testing and Training

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · top of page (header area)

a IT & Phishing Prevention Training

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · above the fold

a cPanel Hosting + Raptor Email Security

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · above the fold

a PCCC TLC

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · above the fold

a Support

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · above the fold

a Raptor Dashboard

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · above the fold

a Raptor Continuity

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · above the fold

a Raptor Documentation

1.80:1

#000000

#293A4A

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Experience You Can T…	1.80:1	3.0:1	#000000	#293A4A	Fail
h2 Raptor Email Securit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 cPanel Hosting +	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Raptor Email Securit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 IT & Phishing	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Prevention Training	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Client Reviews	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Need More Informatio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Industry Leading Com…	1.80:1	4.5:1	#000000	#293A4A	Fail
a Services	1.80:1	4.5:1	#000000	#293A4A	Fail
a Raptor Email Securit…	1.80:1	4.5:1	#000000	#293A4A	Fail
a Phishing Prevention …	1.80:1	4.5:1	#000000	#293A4A	Fail
a IT & Phishing Preven…	1.80:1	4.5:1	#000000	#293A4A	Fail
a cPanel Hosting + Rap…	1.80:1	4.5:1	#000000	#293A4A	Fail
a PCCC TLC	1.80:1	4.5:1	#000000	#293A4A	Fail
a Support	1.80:1	4.5:1	#000000	#293A4A	Fail
a Raptor Dashboard	1.80:1	4.5:1	#000000	#293A4A	Fail
a Raptor Continuity	1.80:1	4.5:1	#000000	#293A4A	Fail
a Raptor Documentation	1.80:1	4.5:1	#000000	#293A4A	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.

A+

Alt Text Quality

All 21 images OK

PASS

All 21 images OK

21 image(s) with good alt text

21 images 21 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

3 issue(s) across 30 links and 1 buttons

PASS

3 issue(s) across 30 links and 1 buttons

3 link(s) with generic text

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

Got: https://raptoremailsecurity.com ("Learn More"); /cpanel-hosting ("Learn More"); /training ("Learn More")

27 link(s) with descriptive text

30 links

0 empty

3 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://raptoremailsecurity.com	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Raptoremailsecurity.Com
/cpanel-hosting	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Cpanel Hosting
/training	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Training

28 links and buttons have descriptive text

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

https://raptoremailsecurity.com ("Learn More"); /cpanel-hosting ("Learn More"); /training ("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

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 23 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
Learn More `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
Learn More `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
Learn More `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
Client Reviews `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title`
Need More Information? `div.elementor-widget-container > div.elementor-cta > div.elementor-cta__content > h2.elementor-cta__title`
Contact Us `div.elementor-cta > div.elementor-cta__content > div.elementor-cta__button-wrapper > a.elementor-cta__button`

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
Company `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h5.elementor-heading-title`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●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 have a discernible name

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

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

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