Skip to content
https://rackspace.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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)
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
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.
B
Heading Hierarchy
38 headings, 1 skip(s)
REVIEW
38 headings, 1 skip(s)
Warning::
Multiple H1 headings (11 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Homepage Mar 10, 2026
  • H1 ISG Provider Lens recognizes Rackspace Technology
  • H2 See how AI-infused delivery, unified governance and outcome-based FinOps set Rackspace apart.
  • H1 The industry’s first Infrastructure to Agents architecture duplicate H1
  • H2 Rackspace and Uniphore partnership delivers full-stack, governed AI operations to accelerate enterprise AI outcomes
  • H1 Rackspace & Palantir partner to accelerate AI outcomes duplicate H1
  • H2 Strategic partnership brings Palantir Foundry and AIP to production through a governed operating model from Rackspace
  • H1 Facing VMware uncertainty? duplicate H1
  • H2 Navigate VMware program changes with one of the world's largest partners - trusted for mission-critical environments.
  • H1 New research: What separates healthcare Cloud Leaders? duplicate H1
  • H2 Survey results show how cloud maturity shapes security, resilience and progress with AI across healthcare.
  • H1 ISG Provider Lens recognizes Rackspace Technology duplicate H1
  • H2 See how AI-infused delivery, unified governance and outcome-based FinOps set Rackspace apart.
  • H1 The industry’s first Infrastructure to Agents architecture duplicate H1
  • H2 Rackspace and Uniphore partnership delivers full-stack, governed AI operations to accelerate enterprise AI outcomes
  • H1 Rackspace & Palantir partner to accelerate AI outcomes duplicate H1
  • H2 Strategic partnership brings Palantir Foundry and AIP to production through a governed operating model from Rackspace
  • H1 Facing VMware uncertainty? duplicate H1
  • H2 Navigate VMware program changes with one of the world's largest partners - trusted for mission-critical environments.
  • H1 New research: What separates healthcare Cloud Leaders? duplicate H1
  • H2 Survey results show how cloud maturity shapes security, resilience and progress with AI across healthcare.
  • H1 ISG Provider Lens recognizes Rackspace Technology duplicate H1
  • H2 See how AI-infused delivery, unified governance and outcome-based FinOps set Rackspace apart.
  • H2 Where enterprise AI runs and outcomes scale
  • H4 AI skipped
  • H4 Private cloud
  • H4 Public cloud
  • H4 Hybrid cloud
  • H2 Decades of expertise matched with thousands of experts
  • H2 Strategic Partnerships
  • H3 We partner with the world's leading innovators to solve our customers' biggest challenges, combining the best technologies to create high-performing solutions.
  • H2 Recognized leadership
  • H2 Latest insights
  • H3 The AI Acceleration Gap: Why Some Enterprises Are Surging Ahead
  • H3 The 2025 State of Cloud Report
  • H3 The Impact of AI on the BFSI Industry
  • H3 Unlocking Agility: Why Hybrid Cloud is the New Normal
  • H2 Ready to start the conversation?

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: File not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Primary Navigation" MAIN CONTENTINFO footer

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 44 images OK
PASS
All 44 images OK
Info::
12 decorative image(s) correctly marked
Info::
32 image(s) with good alt text
44 images 32 good alt text 12 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="search-text-field">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-text-fieldtext(Search here)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q" id="search-text-field">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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)
ElementRatioRequiredFGBGResult
h1 ISG Provider Lens re…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 The industry’s fir…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Rackspace & Palantir…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Facing VMware uncert…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 New research: What s…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 ISG Provider Lens re…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 The industry’s fir…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Rackspace & Palantir…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Facing VMware uncert…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 New research: What s…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 ISG Provider Lens re…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 See how AI-infused d…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rackspace and Unipho…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Strategic partnershi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Navigate VMware prog…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Survey results show …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 See how AI-infused d…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rackspace and Unipho…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Strategic partnershi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Navigate VMware prog…21.00:13.0: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.

A+
Lighthouse Accessibility Audits
Score 95/100 — 4 failing, 30 passed
PASS
95

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.

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
AI div.layout__column > div.solutions__squares > a.solutions__square > h4.h4

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
Support Portal nav > ul.footer__links--list > li.footer__links--item > a.footer__links--link
Careers nav > ul.footer__links--list > li.footer__links--item > a.footer__links--link
Investors nav > ul.footer__links--list > li.footer__links--item > a.footer__links--link

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
Learn More div.slide__content > div.slide__constrained > div.slide__caption > a.button_slick
See the case study div.layout__container > div.layout__column > div.quote > a.button
Let's talk div.ctaRiver > div.ctaRiver__container > div.ctaRiver__column > a.ctaRiverButton

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
                                              … section.layout > div.block > div > table
○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.
●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
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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 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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback