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

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

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

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #2e578b

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

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

2 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 2 <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

6 landmarks

REVIEW

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

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

1 headings

REVIEW

1 headings

No H1 heading found

Every page should have one H1 that describes the page content.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 (empty)

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Link & Button Quality

2 issue(s) across 2 links and 0 buttons

REVIEW

2 issue(s) across 2 links and 0 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; /

2 links

2 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label

Links without text are announced as raw URLs by screen readers.

/; /

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Favicon & Branding

8 icon(s) detected

REVIEW

8 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 Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: HostGator Web Hosting

192x192 icon present

PWA Install Criteria Not Installable

Name HostGator Web Hosting ✓192×192 icon ✓512×512 icon ✗Start URL /?utm_source=homescreen&launcher=true ✓Display Mode browser ✗

Name HostGator Web Hosting Display Mode browser Theme Color #4077B5 Background Color #4077B5 Icons 3 icon(s)

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Color Contrast (Screenshot)

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

11 pass

Show all checked elements (11)

Element	Ratio	Required	FG	BG	Result
title Just a moment...	19.77:1	4.5:1	#000000	#F8F8F8	Pass
span If you are using ass…	19.77:1	4.5:1	#000000	#F8F8F8	Pass
span If you are using ass…	12.33:1	4.5:1	#000000	#ADCBDA	Pass
div Please complete the …	15.39:1	4.5:1	#000000	#B8E3F9	Pass
div Verification success…	16.10:1	4.5:1	#000000	#C2E7FA	Pass
b Why do you have to c…	16.70:1	3.0:1	#000000	#CBEAFB	Pass
div Completing the captc…	17.43:1	4.5:1	#000000	#D4EEFC	Pass
span HostGator	18.07:1	4.5:1	#000000	#DDF1FD	Pass
p Copyright	18.86:1	4.5:1	#000000	#E6F5FE	Pass
span 2016	19.31:1	4.5:1	#000000	#ECF7FF	Pass
p HostGator.com LLC. A…	19.31:1	4.5:1	#000000	#ECF7FF	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.

Lighthouse Accessibility Audits

Score 91/100 — 4 failing, 31 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.

ARIA

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
Chat us `div.cmp-itl > div.cmp-itl__content > div.itl__contentHeight > p`

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.

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
Need help choosing a plan? Call our sales team at (877) 828-5278 `div.header__topbar > div.container > div.header__topbarContainer-center > p`
Call our sales team at (877) 828-5278 `div.container > div.header__topbarContainer-center > p > span`
(877) 828-5278 `div.header__topbarContainer-center > p > span > a`
Now 66% off! `div.card__container > div > h4.card__percent > p`
66 `div > h4.card__percent > p > span.save-percent`
Recommended `div#baby-plan > div.card > div.card__container--spacer > span.card__recommended`
Now 73% off! `div.card__container > div > h4.card__percent > p`
73 `div > h4.card__percent > p > span.save-percent`
Now 72% off! `div.card__container > div > h4.card__percent > p`
72 `div > h4.card__percent > p > span.save-percent`
Now 53% off! `div.card__container > div > h4.card__percent > p`
53 `div > h4.card__percent > p > span.save-percent`
of customers are web pros. `p > a.rte-modal-link > span.hg-lightBlue > span.rte__18px--400`
websites currently hosted. `div.cmp-text > p > a.rte-modal-link > span.rte__18px--400`
See terms - Free domain `div.cmp-text > p > span.rte__15px--300 > a.rte-modal-link`
See terms - Unmetered bandwidth `div.cmp-text > p > span.rte__15px--300 > a.rte-modal-link`
Learn more - about ssl certificates `div.cmp-text > p > span.rte__15px--300 > a`
(866) 964-2867 `div.cmp-itl__content > div.itl__contentHeight > p > a`
Live Chat `div.itl__contentHeight > p > a.genesysChat > span.genesysChat`
@HGSupport `div.cmp-itl__content > div.itl__contentHeight > p > a`
KnowledgeBase `div.cmp-itl__content > div.itl__contentHeight > p > a`
HostGator Blog `div.cmp-itl__content > div.itl__contentHeight > p > a`
Learn more about what web hosting is `div.cmp-text > p > span.rte__15px--300 > a`
different hosting options available `div.cmp-text > p > span.rte__15px--300 > a`
Get more info `div.cmp-text > p > span.rte__15px--300 > a`
See the benefits of building with WordPress `div.cmp-text > p > span.rte__15px--300 > a`
transfer your domain `div.cmp-text > p > span.rte__15px--300 > a.basic-link`
See our KnowledgeBase `div.cmp-text > p > a.rte__18px--400 > span.rte__18px--400`
Visit our blog `div.cmp-text > p > span.rte__18px--400 > a`
*Prices reflect discount on first term `p > span.hg-lightBlue > a.rte-modal-link > span.rte__15px--300`
Chat `body#page-e1c8224f7e > div.GlobalLinkNoTx > div#nf-chat-button > div.text`

These are opportunities to improve the legibility of your content.

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
Products Web Hosting WordPress Hosting eCommerce Hosting Reseller Hosting VPS … `div.container > div.footer__col > div.linklist > ul.link-list`
Services Web Design PPC SEO `div.container > div.footer__col > div.linklist > ul.link-list`
Programs Become An Affiliate Affiliate Portal `div.container > div.footer__col > div.linklist > ul.link-list`
Support Customer Portal Support Portal Video tutorials Live chat Report Abuse … `div.container > div.footer__col > div.linklist > ul.link-list`
Company About HostGator Reviews Company Blog Contact us Careers Privacy Terms … `div.container > div.footer__col > div.linklist > ul.link-list`

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

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
Cookie Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●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

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●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

●ARIA IDs are unique

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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