Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Link & Button Quality

Action

21 issue(s) across 212 links and 44 buttons

FIX

21 issue(s) across 212 links and 44 buttons

3 link(s) with no accessible text

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

Got: /; /; /

13 link(s) with generic text

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

Got: /ai-agents ("AI AgentsSense, analyze, and optimize your data-driven issues 24/7.Learn more"); /mcp-server ("MCPPrompt new Amplitude insights in Claude, Cursor, or any AI platform.Learn more"); /ai-feedback ("AI FeedbackTransform what your customers say anywhere into action.Learn more"); /ai-visibility ("AI VisibilityReveal how LLMs talk about your brand so you can win AI search.Learn more"); /amplitude-analytics ("Learn more →"); /marketing-analytics ("Learn more →"); /session-replay ("Learn more →"); /amplitude-experiment ("Learn more →"); /web-experimentation ("Learn more →"); /guides-and-surveys ("Learn more →") (+3 more)

4 link(s) open in new tab without warning

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

Got: https://app.amplitude.com/login; https://www.linkedin.com/company/amplitude-analytics; https://twitter.com/Amplitude_HQ; https://www.g2.com/products/amplitude-analytics/reviews

5 button(s) with no accessible text

192 link(s) with descriptive text

212 links

3 empty

13 generic text

4 new tab

5 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://app.amplitude.com/login	Login	new tab	Add '(opens in new tab)' to text
/ai-agents	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Agents
/mcp-server	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Mcp Server
/ai-feedback	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Feedback
/ai-visibility	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Visibility
/amplitude-analytics	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Amplitude Analytics
/marketing-analytics	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Marketing Analytics
/session-replay	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Session Replay
/amplitude-experiment	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Amplitude Experiment
/web-experimentation	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Web Experimentation
/guides-and-surveys	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Guides And Surveys
/data-governance	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Data Governance
/integrations	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Integrations
/solutions/product	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Product
https://www.linkedin.com/company/amplitu…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://twitter.com/Amplitude_HQ	Twitter	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/amplitude-an…	G2	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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

231 links and buttons have descriptive text

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

/; /; /

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.

/ai-agents ("AI AgentsSense, analyze, and optimize your data-driven issues 24/7.Learn more"); /mcp-server ("MCPPrompt new Amplitude insights in Claude, Cursor, or any AI platform.Learn more"); /ai-feedback ("AI FeedbackTransform what your customers say anywhere into action.Learn more"); /ai-visibility ("AI VisibilityReveal how LLMs talk about your brand so you can win AI search.Learn more"); /amplitude-analytics ("Learn more →"); /marketing-analytics ("Learn more →"); /session-replay ("Learn more →"); /amplitude-experiment ("Learn more →"); /web-experimentation ("Learn more →"); /guides-and-surveys ("Learn more →") (+3 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

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

https://app.amplitude.com/login; https://www.linkedin.com/company/amplitude-analytics; https://twitter.com/Amplitude_HQ; https://www.g2.com/products/amplitude-analytics/reviews

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.amplitude.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.amplitude.com/manifest.json

Manifest contains invalid JSON.

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: #1e61f0

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

6 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

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

Breadcrumbs

Skip Link

Labeled Navigation 6 <nav> element(s)

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.

Landmark Structure

11 landmarks

REVIEW

11 landmarks

<main> landmark present

6 <nav> landmark(s) found

6 of 6 <nav> elements are unlabeled

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

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

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

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

Heading Hierarchy

69 headings, 2 skip(s)

REVIEW

69 headings, 2 skip(s)

Single H1 present

Heading level skipped: H3 → H6 (missing H4)

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.

H4 AI
H4 Insights
H4 Action
H4 Data
H4 Industry
H4 Use Case
H4 Team
H4 Size
H4 Learn
H4 Connect
H4 Support & Services
H4 Tools
H4 AI
H4 Insights
H4 Action
H4 Data
H4 Industry
H4 Use Case
H4 Team
H4 Size
H4 Learn
H4 Connect
H4 Support & Services
H4 Tools
H1 The AI analytics platform forfaster answerstesting everythingnon-stop optimizationgrowing relentlessly
H2 Trusted by industry leaders
H3 Your unfair AI advantage
H6 AI Agents skipped
H6 MCP
H6 AI Feedback
H6 AI Visibility
H2 Understand what your customers want—and give it to them
H3 Clearer insights
H3 Clearer insights
H4 Product Analytics
H4 Web Analytics
H4 Session Replay
H3 Faster action
H3 Faster action
H4 Feature Experimentation
H4 Web Experimentation
H4 Guides and Surveys
H3 More trustworthy data
H3 More trustworthy data
H4 Data Governance
H4 Integrations
H2 Win together
H3 Product teams
H3 Marketing teams
H3 Data teams
H3 Engineering teams
H3 Get trusted insights about user engagement to build better products.
H2 Outcomes speak louder than words
H3 “Until we looked at Amplitude reports, we didn’t realize what was happening. We immediately took action, saving us revenue.”
H3 How we increased conversions by 27% with behavior insights
H3 “Amplitude allows us to really action our data. Going beyond just the insights, we’re now able to engage users in ways that are most meaningful to them.”
H3 How we boosted activation by 40% with better onboarding
H3 “We saw a 40% increase in new subscribers. Everyone was astounded by the results because it’s not common to see such a significant improvement.”
H3 How we grew subscribers 40% with personalized content
H3 Featured resources
H2 The Product Benchmark Report: How Top Teams Win and Grow
H4 The Forrester Wave™: Digital Analytics Solutions, Q3 2025 skipped
H4 AI Analytics Buyer’s Guide
H4 The Modern Guide to Data Democratization
H4 The Product Benchmark Report: How Top Teams Win and Grow
H4 The Forrester Wave™: Digital Analytics Solutions, Q3 2025
H4 AI Analytics Buyer’s Guide
H4 The Modern Guide to Data Democratization
H2 Connect every action to impact

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 Page not found | Amplitude ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 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

A+

Alt Text Quality

All 72 images OK

PASS

All 72 images OK

28 decorative image(s) correctly marked

44 image(s) with good alt text

72 images 44 good alt text 28 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
h2 Trusted by industry …	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h2 Understand what your…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h2 Win together	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h2 Outcomes speak loude…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h2 The Product Benchmar…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h2 Connect every action…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Your unfair AI advan…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Clearer insights	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Clearer insights	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Faster action	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Faster action	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 More trustworthy dat…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 More trustworthy dat…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Product teams	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Marketing teams	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Data teams	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Engineering teams	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 Get trusted insights…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 “Until we looked a…	20.42:1	3.0:1	#000000	#FAFCFE	Pass
h3 How we increased con…	20.42:1	3.0:1	#000000	#FAFCFE	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.

Lighthouse Accessibility Audits

Score 90/100 — 4 failing, 26 passed

PASS

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
header.pt-[17px] > nav.relative > div.flex > button.h-12.5 `header.pt-[17px] > nav.relative > div.flex > button.h-12.5`
div.fixed > div.relative > div.h-[54px] > button.h-12.5 `div.fixed > div.relative > div.h-[54px] > button.h-12.5`
div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_ `div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_`
div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_ `div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_`
div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_ `div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_`

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
header.pt-[17px] > nav.relative > div.flex > a `header.pt-[17px] > nav.relative > div.flex > a`
div.fixed > div.relative > div.h-[54px] > a `div.fixed > div.relative > div.h-[54px] > a`

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.

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.overflow-hidden > div.flex > div.flex > h4.text-[#868D95]`
AI Agents `div.w-[294px] > div.flex > div.flex > h6.text-white`

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
AI Agents Sense, analyze, and optimize your data-driven issues 24/7. Learn mo… `div.relative > div.w-full > div.flex > a.group`
MCP Prompt new Amplitude insights in Claude, Cursor, or any AI platform. Lear… `div.relative > div.w-full > div.flex > a.group`
Report The Product Benchmark Report: How Top Teams Win and Grow Discover the s… `div.max-w-[1140px] > div.lg:hidden > div.flex > a`
Report The Forrester Wave™: Digital Analytics Solutions, Q3 2025 Forrester nam… `div.max-w-[1140px] > div.lg:hidden > div.flex > a`

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

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

●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"]`

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.