Skip to content
https://newrelic.com

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
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
C
Heading Hierarchy
Action
45 headings, 1 skip(s)
REVIEW
45 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Observability that predicts thinks
  • H5 SRE Agent skipped
  • H5 Session replay with AI
  • H5 Understand cloud costs
  • H5 AI and agentic monitoring
  • H5 OpenTelemetry
  • H5 Agentic Platform
  • H2 Observability built to understand AI
  • H2 Platform
  • H2 Intelligent Observability Platform
  • H2 Intelligent Observability Platform
  • H3 Categories
  • H4 Featured
  • H4 Application Performance Monitoring
  • H4 Digital Experience Monitoring
  • H4 AI and Intelligent Automation
  • H4 Infrastructure Monitoring
  • H4 Log Management
  • H4 Platform Capabilities
  • H2 Solutions
  • H2 Solutions
  • H2 Solutions
  • H3 Use Cases
  • H3 Technologies
  • H3 Industries
  • H2 Pricing
  • H2 Pricing
  • H2 For small teams
  • H2 For scaling teams
  • H2 For mission-critical orgs
  • H2 Pricing
  • H2 For small teams
  • H2 For scaling teams
  • H2 For mission-critical orgs
  • H2 Customers
  • H2 Customers
  • H2 Customers
  • H3 Featured
  • H3 Industries
  • H2 Resources
  • H2 Resources
  • H2 Resources
  • H3 Getting Started
  • H3 Guides
  • H3 Events & On-Demand

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

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

B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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 Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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
h2 Observability that
1.20:1
#000000
on
#141A1F
needs 3.0:1 (large text)
24px · mid-page
h2 Platform
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Intelligent Observability Platform
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Intelligent Observability Platform
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Solutions
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Solutions
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Solutions
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Pricing
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pricing
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For small teams
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For scaling teams
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For mission-critical orgs
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pricing
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For small teams
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For scaling teams
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For mission-critical orgs
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Customers
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Customers
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Customers
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Resources
1.10:1
#000000
on
#060E25
needs 3.0:1 (large text)
24px · bottom of viewport

6 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Observability that1.20:13.0:1
#000000
#141A1F
Fail
h2 Platform1.10:13.0:1
#000000
#060E25
Fail
h2 Intelligent Observab…1.10:13.0:1
#000000
#060E25
Fail
h2 Intelligent Observab…1.10:13.0:1
#000000
#060E25
Fail
h2 Solutions1.10:13.0:1
#000000
#060E25
Fail
h2 Solutions1.10:13.0:1
#000000
#060E25
Fail
h2 Solutions1.10:13.0:1
#000000
#060E25
Fail
h2 Pricing1.10:13.0:1
#000000
#060E25
Fail
h2 Pricing1.10:13.0:1
#000000
#060E25
Fail
h2 For small teams1.10:13.0:1
#000000
#060E25
Fail
h2 For scaling teams1.10:13.0:1
#000000
#060E25
Fail
h2 For mission-critical…1.10:13.0:1
#000000
#060E25
Fail
h2 Pricing1.10:13.0:1
#000000
#060E25
Fail
h2 For small teams1.10:13.0:1
#000000
#060E25
Fail
h2 For scaling teams1.10:13.0:1
#000000
#060E25
Fail
h2 For mission-critical…1.10:13.0:1
#000000
#060E25
Fail
h2 Customers1.10:13.0:1
#000000
#060E25
Fail
h2 Customers1.10:13.0:1
#000000
#060E25
Fail
h2 Customers1.10:13.0:1
#000000
#060E25
Fail
h2 Resources1.10:13.0:1
#000000
#060E25
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 86/100 — 4 failing, 25 passed
REVIEW
86

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.

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
div.w-full > div.js-vanilla-carousel > div.flex > button.arrow div.w-full > div.js-vanilla-carousel > div.flex > button.arrow
div.w-full > div.js-vanilla-carousel > div.flex > button.arrow div.w-full > div.js-vanilla-carousel > div.flex > button.arrow
div.relative > div.js-vanilla-carousel > div.flex > button.arrow div.relative > div.js-vanilla-carousel > div.flex > button.arrow
div.relative > div.js-vanilla-carousel > div.flex > button.arrow div.relative > div.js-vanilla-carousel > div.flex > button.arrow
div.view-content > div.js-vanilla-carousel > div.flex > button.arrow div.view-content > div.js-vanilla-carousel > div.flex > button.arrow
div.view-content > div.js-vanilla-carousel > div.flex > button.arrow div.view-content > div.js-vanilla-carousel > div.flex > button.arrow

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 > div.snap-always > div.card-tile > a.group div.flex > div.snap-always > div.card-tile > a.group
div.flex > div.snap-always > div.card-tile > a.group div.flex > div.snap-always > div.card-tile > a.group
div.flex > div.snap-always > div.card-tile > a.group div.flex > div.snap-always > div.card-tile > a.group
div.flex > div.snap-always > div.card-tile > a.group div.flex > div.snap-always > div.card-tile > a.group

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
Accept All div.osano-cm-window > div#2cffb755-bacc-4fa1-87ee-6a589990cff7 > div.osano-cm-dialog__buttons > button.osano-cm-accept-all

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
SRE Agent div.flex > div.h-[101px] > div.medium:flex > h5.p09-carousel-headline

These are opportunities to improve keyboard navigation in your application.

○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.
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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
○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
○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.
○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
○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
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A+
Alt Text Quality
All 56 images OK
PASS
All 56 images OK
Info::
18 decorative image(s) correctly marked
Info::
38 image(s) with good alt text
56 images 38 good alt text 18 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
#header-searchsearchSearchfor/id
#header-searchsearchSearchfor/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title New Relic | Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback