Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

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 ✗

Lighthouse Accessibility Audits

Action

Score 61/100 — 13 failing, 19 passed

FIX

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
Residential Business Resources Tools Blog `div.flex > div.flex > div#mobile-menu > ul.flex`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
5G Home Internet Level Up at Home with 5G Speeds and Unlimited Data High-spee… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
5G Home Internet Level Up at Home with 5G Speeds and Unlimited Data High-spee… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
Fiber Internet You Can Count On Unstoppable Speeds for Every Need No bundles,… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
5G Home Internet Level Up at Home with 5G Speeds and Unlimited Data High-spee… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
Your link to hard-to-reach places. Did you know EarthLink is the largest provid… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
Your link to seamless gaming. Leave the connection to us and get your head in t… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
Your link to hard-to-reach places. Did you know EarthLink is the largest provid… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
Your link to working from home. The workplace is changing. So is the internet. … `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
Your link to seamless gaming. Leave the connection to us and get your head in t… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`
Your link to hard-to-reach places. Did you know EarthLink is the largest provid… `div.slick-slider > div.slick-list > div.slick-track > div.slick-slide`

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
Reviews Section `div.amplify-widget > div > span.VisuallyHidden__VisuallyHiddenSpan-sc-jzrqc0-0 > span`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`
star rating 5.0 `div > div > div.Card-sc-1qxwf3a-0 > span.StarRating__Wrapper-sc-1ntr8zq-1`

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
nav.h-full > div.flex > div.flex > button#toggle-btn `nav.h-full > div.flex > div.flex > button#toggle-btn`
div.relative > span > div.flex > button.flex-auto `div.relative > span > div.flex > button.flex-auto`
div.relative > span > div.flex > button.flex `div.relative > span > div.flex > button.flex`

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
div.flex > ul.flex > li.flex > input#business-plans-checkbox `div.flex > ul.flex > li.flex > input#business-plans-checkbox`

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.flex > ul.xl:hidden > li.mob:px-2 > a.inline-block `div.flex > ul.xl:hidden > li.mob:px-2 > a.inline-block`
div.smd:hidden > ul.flex > li.inline-flex > a `div.smd:hidden > ul.flex > li.inline-flex > a`
div.smd:hidden > ul.flex > li.inline-flex > a `div.smd:hidden > ul.flex > li.inline-flex > a`
div.smd:hidden > ul.flex > li.inline-flex > a `div.smd:hidden > ul.flex > li.inline-flex > a`
div.smd:hidden > ul.flex > li.inline-flex > a `div.smd:hidden > ul.flex > li.inline-flex > a`

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Residential `div#mobile-menu > ul.flex > li.group > a#Residential0`

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
Most Popular Super-Fast `section.bg-elnk-gray-300 > div.max-w-elnkcontainer > div.border-2 > h2.text-[1.1rem]`

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
Tired of bait-and-switch offers from providers? Slow speeds, unexpected fees, u… `div.px-6 > div.max-w-elnkcontainer > div.w-[90%] > h4.text-white`
Home Internet `div.px-9 > a.border-2 > div > h4.text-elnk-blue-500`

These are opportunities to improve keyboard navigation in your application.

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
Unlimited streaming, gaming, and remote work No data caps, no credit checks Qui… `div.bg-elnk-blue-600 > div.text-white > div > ul.mb-[24px]`

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
Residential `div.flex > div#mobile-menu > ul.flex > li.group`
Business `div.flex > div#mobile-menu > ul.flex > li.group`
Resources `div.flex > div#mobile-menu > ul.flex > li.group`
Tools `div.flex > div#mobile-menu > ul.flex > li.group`
Blog `div.flex > div#mobile-menu > ul.flex > li.group`
Unlimited streaming, gaming, and remote work `div > ul.mb-[24px] > div.flex > li`
No data caps, no credit checks `div > ul.mb-[24px] > div.flex > li`
Quick, professional installation `div > ul.mb-[24px] > div.flex > li`

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

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 `div.slick-slider > ul.dot__bar > li.slick-active > button`
2 `div.slick-slider > ul.dot__bar > li > button`
1 `div.slick-slider > ul.button__bar > li.slick-active > button`
2 `div.slick-slider > ul.button__bar > li > button`
3 `div.slick-slider > ul.button__bar > li > button`

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.wf-roboto-n4-active `html.wf-roboto-n4-active`

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

●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

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

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

●`[lang]` attributes have a valid value

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●No form fields have multiple labels

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

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

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

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

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

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

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

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

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

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 decorative image(s) correctly marked

1 images 1 decorative

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.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

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 Page not found | EarthLink ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Color Contrast (Screenshot)

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

3 pass

Show all checked elements (3)

Element	Ratio	Required	FG	BG	Result
title Just a moment...	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span EarthLink is checkin…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Verification success…	21.00:1	4.5:1	#000000	#FFFFFF	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.

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