Accessibility

D

Heading Hierarchy

Action

33 headings, 3 skip(s)

FIX

33 headings, 3 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 → H5 (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.

1 empty heading(s)

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

H1 Managed Hosting & Beyond
H2 Intelligent platforms built for your digital future
H2 Power the freedom to create onlineSolutions built for you
H4 Managed Hosting Platform skipped
H4 eCommerce Solution
H4 Newsroom Platform
H2 The WP Engine AdvantageTechnology engineered for growth
H2 Built for your successAn ecosystem that powers your ambition
H5 Enterprise Teams skipped
H5 Agencies
H5 Developers
H5 Media Publishers
H2 Case studySame team. 5x their capacity.
H2 Case studyTransforming digital engagement with AI
H2 Case StudyDecade-long partnership powers agency growth and client retention
H2 Case StudyTransforming an agency business model for growth without growing pains
H2 Case StudyTravel website becomes top traffic destination for frequent fliers
H2 (empty)
H4 Outstanding customer support which is always available to help skipped
H4 We can focus on actually building great websites
H4 The best 24/7 technical support I have ever seen
H2 Let’s get startedReady to migrate today?
H2 Our Company
H2 Products
H2 Solutions
H2 Community & Partners
H2 Resources
H3 Our Company
H3 Products
H3 Solutions
H3 Community & Partners
H3 Resources
H3 Our Brands

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 ▾

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 ▾

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

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

D

Link & Button Quality

Action

4 issue(s) across 133 links and 44 buttons

FIX

4 issue(s) across 133 links and 44 buttons

1 link(s) with no accessible text

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

Got: a#maincontent

3 link(s) with generic text

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

Got: /managed-hosting-platform/ ("Learn More"); /ecommerce-solutions/ ("Learn More"); /newsroom-platform/ ("Learn More")

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/"]

15 link(s) open in new tab without warning

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

Got: https://getflywheel.com/; https://localwp.com/; https://www.advancedcustomfields.com/; https://nitropack.io/; https://www.studiopress.com/; https://deliciousbrains.com/; https://developers.wpengine.com/; https://developers.wpengine.com/docs/managed-hosting-platform/api; https://www.facebook.com/wpengine/; https://x.com/wpengine (+5 more)

113 link(s) with descriptive text

133 links

1 empty

3 generic text

15 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://getflywheel.com/	Flywheel	new tab	Add '(opens in new tab)' to text
https://localwp.com/	Local	new tab	Add '(opens in new tab)' to text
https://www.advancedcustomfields.com/	ACF	new tab	Add '(opens in new tab)' to text
https://nitropack.io/	NitroPack	new tab	Add '(opens in new tab)' to text
https://www.studiopress.com/	StudioPress	new tab	Add '(opens in new tab)' to text
https://deliciousbrains.com/	Delicious brains	new tab	Add '(opens in new tab)' to text
https://developers.wpengine.com/	Developer DocsFind everything …	new tab	Add '(opens in new tab)' to text
https://developers.wpengine.com/docs/man…	Builder APIsLearn how to build…	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
/managed-hosting-platform/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Managed Hosting Platform
/ecommerce-solutions/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Ecommerce Solutions
/newsroom-platform/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Newsroom Platform
/	Home	img no alt	Add alt attribute to the image
https://www.facebook.com/wpengine/	facebook	new tab	Add '(opens in new tab)' to text
https://x.com/wpengine	twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/wpengine/	instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/wpengin…	linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/wpengine	youtube	new tab	Add '(opens in new tab)' to text
https://web-cdn.bsky.app/profile/wpengin…	bluesky	new tab	Add '(opens in new tab)' to text
/feed/	rss	new tab	Add '(opens in new tab)' to text

157 links and buttons have descriptive text

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

a#maincontent

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

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

/managed-hosting-platform/ ("Learn More"); /ecommerce-solutions/ ("Learn More"); /newsroom-platform/ ("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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://getflywheel.com/; https://localwp.com/; https://www.advancedcustomfields.com/; https://nitropack.io/; https://www.studiopress.com/; https://deliciousbrains.com/; https://developers.wpengine.com/; https://developers.wpengine.com/docs/managed-hosting-platform/api; https://www.facebook.com/wpengine/; https://x.com/wpengine (+5 more)

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

D

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: #ffffff

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

13 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 13 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

B

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 | WP Engine® ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

5 icon(s) detected

REVIEW

5 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

B

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: WP Engine

192x192 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name WP Engine ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓

Name WP Engine Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 1 icon(s)

B

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 25 passed

REVIEW

88

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
AI assistant `body > q-focus-sentinel > div`
After AI assistant `body > q-focus-sentinel > div`
AI assistant, start `div#qualified-multimodal-host > div`
AI assistant, end `div#qualified-multimodal-host > div`

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
POWER THE FREEDOM TO CREATE ONLINE `section._55ef9g3 > div._55ef9ga > h2.h9nzq60 > div._55ef9g9`
Power your digital portfolio with the speed, security, and scalability that mis… `div._12bllok1 > div._12bllok6 > div._12bllok8 > p`
Learn More `div._12bllok6 > a._12bllok9 > div._147wu1c0 > span._147wu1c2`
0% `div.zg32ih6 > section._5fwitc0 > div.ridizu0 > div.ridizu1`
support satisfaction `div.zg32ih6 > section._5fwitc0 > div.ridizu0 > p.ridizu2`
0% `div.zg32ih6 > section._5fwitc0 > div.ridizu0 > div.ridizu1`
first contact resolution `div.zg32ih6 > section._5fwitc0 > div.ridizu0 > p.ridizu2`
0X `div.zg32ih6 > section._5fwitc0 > div.ridizu0 > div.ridizu1`
Enterprise Teams `div._13pq1hr0 > div._192p74w0 > div._192p74w8 > h5._192p74wa`
Cut total cost of ownership with an all-inclusive platform. We handle the scali… `div._192p74w0 > div._192p74w8 > div._1wtu5714 > p`
Explore Enterprise `div._192p74w8 > a > div._147wu1c0 > span._147wu1c2`
Agencies `div._13pq1hr0 > div._192p74w0 > div._192p74w8 > h5._192p74wa`
Deliver excellence to your clients without the overhead. Leverage our partner p… `div._192p74w0 > div._192p74w8 > div._1wtu5714 > p`
Explore Agency `div._192p74w8 > a > div._147wu1c0 > span._147wu1c2`
reviewed by G2 `div.ywwdw90 > div.ywwdw91 > div.ywwdw96 > span`
G2 `div.ywwdw91 > div.ywwdw96 > span > strong`
Outstanding customer support which is always available to help `div._13pq1hr0 > div.ywwdw90 > div.ywwdw98 > h4.ywwdw99`
I love WP Engine for their outstanding customer support which is always availab… `div.ywwdw90 > div.ywwdw98 > div.ywwdw9a > p`
Joey B `div.ywwdw98 > div.ywwdw9a > p > strong`
LET’S GET STARTED `section.fwke7f0 > div.fwke7f4 > h2.h9nzq60 > div.fwke7fa`
© 2013–2026 WPEngine, Inc. All rights reserved. WP ENGINE®, VELOCITIZE®, TORQUE… `footer._5qy9kc0 > div._5qy9kc1 > div._5qy9kcj > div._5qy9kck`
1WP Engine is a proud member and supporter of the community of WordPress® users… `div._5qy9kc1 > div._5qy9kcj > div._5qy9kck > div#legal-disclaimer`

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
Managed Hosting Platform `div._13pq1hr0 > div._12bllok1 > div._12bllok6 > h4._12bllok7`
Enterprise Teams `div._13pq1hr0 > div._192p74w0 > div._192p74w8 > h5._192p74wa`
Outstanding customer support which is always available to help `div._13pq1hr0 > div.ywwdw90 > div.ywwdw98 > h4.ywwdw99`

These are opportunities to improve keyboard navigation in your application.

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
Slide 2 `section.bgpbqc1 > div.bgpbqc7 > div.d0ddgk5 > button.d0ddgka`
Slide 3 `section.bgpbqc1 > div.bgpbqc7 > div.d0ddgk5 > button.d0ddgka`
Slide 4 `section.bgpbqc1 > div.bgpbqc7 > div.d0ddgk5 > button.d0ddgka`

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.

●ARIA attributes are used as specified for the element's role

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●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

○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

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

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

A

Landmark Structure

22 landmarks

PASS

22 landmarks

<main> landmark present

13 <nav> landmark(s) found

2 of 13 <nav> elements are unlabeled

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

Skip navigation link present

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

A+

Alt Text Quality

All 76 images OK

PASS

All 76 images OK

7 decorative image(s) correctly marked

69 image(s) with good alt text

76 images 69 good alt text 7 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+

Color Contrast (Screenshot)

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Managed Hosting & Be…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Intelligent platform…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our Company	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Products	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Solutions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Community & Partners	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Trusted Website Host…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to Main Content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Platform	19.53:1	4.5:1	#000000	#F4F7FA	Pass
div Managed Hosting Plat…	18.64:1	4.5:1	#000000	#EDF2F7	Pass
div Fast, secure, & easy…	18.64:1	4.5:1	#000000	#EDF2F7	Pass
div eCommerce Solution	18.64:1	4.5:1	#000000	#EDF2F7	Pass
div Optimized performanc…	18.64:1	4.5:1	#000000	#EDF2F7	Pass
div Newsroom Platform	18.64:1	4.5:1	#000000	#EDF2F7	Pass
div Editorial workflow a…	18.64:1	4.5:1	#000000	#EDF2F7	Pass
div Headless Platform	18.64:1	4.5:1	#000000	#EDF2F7	Pass
div Build & manage sites…	18.64:1	4.5:1	#000000	#EDF2F7	Pass
span Explore the Platform	18.64:1	4.5:1	#000000	#EDF2F7	Pass
div Extensions & Tools	18.64:1	4.5:1	#000000	#EDF2F7	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.