Skip to content
https://www.redis.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 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
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Redis ✓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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #fff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Your App is about to get faster
1.09:1
#000000
on
#050F15
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Works with
1.09:1
#000000
on
#050F15
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start building in
1.09:1
#000000
on
#050F15
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join the Redis community
1.09:1
#000000
on
#050F15
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get started
1.09:1
#000000
on
#050F15
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Think fast.
1.09:1
#000000
on
#050F15
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Deploy
1.09:1
#000000
on
#050F15
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The features you need
1.09:1
#000000
on
#050F15
needs 3.0:1 (large text)
19px · bottom of viewport
title Redis - The Real-time Data Platform
1.23:1
#000000
on
#0D1E27
needs 4.5:1 (normal text)
16px · top of page (header area)
span Skip to:
1.23:1
#000000
on
#0D1E27
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · top of page (header area)
a Content
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · top of page (header area)
a Footer navigation
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · above the fold
p Let’s talk fast, accurate AI at Google…
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · above the fold
span Join us in Vegas on April 22-24.
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · above the fold
span Redis for AI
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · above the fold
span Products
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · above the fold
span Products
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · above the fold
span Redis Cloud
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · above the fold
span Fully managed and integrated with Google…
1.09:1
#000000
on
#050F15
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Your App is about to…1.09:13.0:1
#000000
#050F15
Fail
h2 Works with1.09:13.0:1
#000000
#050F15
Fail
h2 Start building in1.09:13.0:1
#000000
#050F15
Fail
h2 Join the Redis commu…1.09:13.0:1
#000000
#050F15
Fail
h2 Get started1.09:13.0:1
#000000
#050F15
Fail
h3 Think fast.1.09:13.0:1
#000000
#050F15
Fail
h3 Deploy1.09:13.0:1
#000000
#050F15
Fail
h3 The features you nee…1.09:13.0:1
#000000
#050F15
Fail
title Redis - The Real-tim…1.23:14.5:1
#000000
#0D1E27
Fail
span Skip to:1.23:14.5:1
#000000
#0D1E27
Fail
a Home1.09:14.5:1
#000000
#050F15
Fail
a Content1.09:14.5:1
#000000
#050F15
Fail
a Footer navigation1.09:14.5:1
#000000
#050F15
Fail
p Let’s talk fast, a…1.09:14.5:1
#000000
#050F15
Fail
span Join us in Vegas on …1.09:14.5:1
#000000
#050F15
Fail
span Redis for AI1.09:14.5:1
#000000
#050F15
Fail
span Products1.09:14.5:1
#000000
#050F15
Fail
span Products1.09:14.5:1
#000000
#050F15
Fail
span Redis Cloud1.09:14.5:1
#000000
#050F15
Fail
span Fully managed and in…1.09:14.5:1
#000000
#050F15
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 6 failing, 28 passed
REVIEW
85

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
NO YES div.prefPanel > div > div.cookiecat > div.switch
NO YES div.prefPanel > div > div.cookiecat > div.switch
NO YES div.prefPanel > div > div.cookiecat > div.switch

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
View Required Cookies div.prefPanel > div > div.cookiecat > a.viewcookie
Detailed Settings div.prefPanel > div > div.cookiecat > a.viewcookie
Detailed Settings div.prefPanel > div > div.cookiecat > a.viewcookie
View Required Cookies div.prefPanel > div > div.cookiecat > a.viewcookie
Privacy Policy div > div.footer > div.left > a#privacyPolicyAnchor
Powered by: div.wrapper > div > div.footer > div.right

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.__variable_bd0331 > div#pop-div2010163364667647778 > div#pop-div308754556499126427 > div#pop-frame000344789200141582 body.__variable_bd0331 > div#pop-div2010163364667647778 > div#pop-div308754556499126427 > div#pop-frame000344789200141582

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
Think fast. Build faster. section.style_section__Qbg1z > div.styles_container__ImQx_ > div.styles_title__PZyMD > h3.styles_text__Pngqw
Required Cookies div.cookiecat > div > span.gwt-InlineHTML > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer > div.left > a#privacyPolicyAnchor > img.inline-e3jf3l div.footer > div.left > a#privacyPolicyAnchor > img.inline-e3jf3l

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.

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
View Required Cookies div.prefPanel > div > div.cookiecat > a.viewcookie
Detailed Settings div.prefPanel > div > div.cookiecat > a.viewcookie
NO div > div.cookiecat > div.switch > span.gwt-InlineHTML
YES div > div.cookiecat > div.switch > span.gwt-InlineHTML
Detailed Settings div.prefPanel > div > div.cookiecat > a.viewcookie
NO div > div.cookiecat > div.switch > span.gwt-InlineHTML
YES div > div.cookiecat > div.switch > span.gwt-InlineHTML
View Required Cookies div.prefPanel > div > div.cookiecat > a.viewcookie
NO div > div.cookiecat > div.switch > span.gwt-InlineHTML
YES div > div.cookiecat > div.switch > span.gwt-InlineHTML
○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●`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
●ARIA input fields have accessible names
●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 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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Skip to links" 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
Heading Hierarchy
8 headings, 1 skip(s)
PASS
8 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Your App is about to get faster
  • H3 Think fast. Build faster. skipped
  • H3 Deploy anywhere
  • H2 Works with
  • H2 Start building in minutes
  • H3 The features you need all in one place
  • H2 Join the Redis community
  • H2 Get started

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

A+
Alt Text Quality
All 40 images OK
PASS
All 40 images OK
Info::
2 decorative image(s) correctly marked
Info::
38 image(s) with good alt text
40 images 38 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#language-selector-desktopselectSwitch languagearia-label
#language-selector-mobileselectSwitch languagearia-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback