Accessibility

F

Heading Hierarchy

Action

15 headings, 7 skip(s)

FIX

15 headings, 7 skip(s)

Single H1 present

Heading level skipped: H1 → H5 (missing H2)

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 → H5 (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 → H5 (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 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 AI-Powered Observability and Security
H5 EBOOK: MIGRATE TO AWS WITHOUT DISRUPTION skipped
H2 Define and track KPIs for successfully moving your data and applications to AWS
H5 EBOOK: MIGRATE TO AZURE WITHOUT DISRUPTION skipped
H2 Define and track KPIs for successfully moving your data and applications to Azure
H5 EBOOK: MIGRATE TO GOOGLE CLOUD WITHOUT DISRUPTION skipped
H2 Define and track KPIs for successfullymoving your data and applications to GCP
H5 THE FORRESTER WAVE™: AIOPS PLATFORMS skipped
H2 Datadog has been recognized as a Leader in The Forrester Wave™: AIOps Platforms, Q2 2025
H5 2025 GARTNER® MAGIC QUADRANT™ skipped
H2 Datadog has been recognized as a Leader in the Gartner Magic Quadrant™ for Observability Platforms
H5 2025 GARTNER® MAGIC QUADRANT™ skipped
H2 Datadog has been recognized as a Leader in the Gartner Magic Quadrant™ for Digital Experience Monitoring
H2 Products
H6 Request a personalized demo with a Datadog engineer skipped

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

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

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

D

Link & Button Quality

Action

3 issue(s) across 504 links and 17 buttons

FIX

3 issue(s) across 504 links and 17 buttons

1 link(s) with generic text

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

Got: https://www.datadoghq.com/events-webinars/ ("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#transcend-footer-link

4 link(s) open in new tab without warning

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

Got: https://dash.datadoghq.com/?utm_source=hp&utm_medium=internal&utm_campaign=su…; https://careers.datadoghq.com/; https://www.datadoghq.com/legal/privacy/; https://www.datadoghq.com/legal/cookies/

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.ais-SearchBox-submit (#784 on page); button.ais-SearchBox-reset (#786 on page)

498 link(s) with descriptive text

504 links

0 empty

1 generic text

4 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://dash.datadoghq.com/?utm_source=h…	Link to DASH site	new tab	Add '(opens in new tab)' to text
https://careers.datadoghq.com/	Link to careers site	new tab	Add '(opens in new tab)' to text
https://www.datadoghq.com/events-webinar…	learn more	generic text	Replace with descriptive text
Before: learn more Suggested: Events Webinars
#	Your Privacy Choices	img no alt	Add alt attribute to the image
https://www.datadoghq.com/legal/privacy/	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.datadoghq.com/legal/cookies/	Cookie Policy.	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

513 links and buttons have descriptive text

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

https://www.datadoghq.com/events-webinars/ ("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#transcend-footer-link

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://dash.datadoghq.com/?utm_source=hp&utm_medium=internal&utm_campaign=su…; https://careers.datadoghq.com/; https://www.datadoghq.com/legal/privacy/; https://www.datadoghq.com/legal/cookies/

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.ais-SearchBox-submit (#784 on page); button.ais-SearchBox-reset (#786 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

D

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.

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

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Alt Text Quality

2 of 29 images have issues

REVIEW

2 of 29 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 decorative image(s) correctly marked

24 image(s) with good alt text

29 images 24 good alt text 3 decorative 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title White modal up arrow ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

B

Favicon & Branding

3 icon(s) detected

REVIEW

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

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title Cloud Monitoring as a Service | Datadog

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 AI-Powered Observabi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Define and track KPI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Define and track KPI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Define and track KPI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 moving your data and…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Datadog has been rec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Datadog has been rec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Datadog has been rec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Products	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Cloud Monitoring as …	1.00:1	4.5:1	#000000	#000000	Fail
span Join Datadog at DASH…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span DASH NYC, June 9-10 …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Product	20.65:1	4.5:1	#000000	#FDFDFD	Pass
p The integrated platf…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Observability	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Security	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Digital Experience	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Software Delivery	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Service Management	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Platform Capabilitie…	20.47:1	4.5:1	#000000	#FCFCFC	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

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	search	Search	aria-label
#FirstName	text	First Name	for/id
#LastName	text	Last Name	for/id
#Email	email	Business Email	for/id
#Company	text	Company	for/id
#Title	text	Job Title	for/id
#Phone	tel	*Phone Number	for/id
#utmsource	textarea	*How are you currently monitoring your infrastructure and applications?	for/id

A+

Lighthouse Accessibility Audits

Score 98/100 — 2 failing, 25 passed

PASS

98

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
2025 GARTNER® MAGIC QUADRANT™ `div.container > div.row > div.text-container > h5`

These are opportunities to improve keyboard navigation in your application.

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
SAVE THE DATE `div.tw-flex > div.tw-relative > div.tw-relative > a.tw-flex`
LEARN MORE `div.container > div.row > div.text-container > a.rotating-banner-btn`
LEARN MORE `div.tw-flex > div.home-blog-bg > div.tw-container > a.tw-flex`
LEARN MORE `section > div.bg-gray-lightest > div.tw-container > a.tw-flex`

○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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

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

○Identical links have the same purpose.

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