Skip to content
https://www.stripe.dev

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
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
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
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
BANNER (missing!) NAV MAIN CONTENTINFO (missing!)

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

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 Stripe Dot Dev ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Heading Hierarchy
8 headings
PASS
8 headings
Info::
Single H1 present
  • H1 stripe.dev - Stripe Developer hub
  • H2 Feed(20)
  • H2 Get help(4)
  • H2 Router(12)
  • H3 Accept a payment
  • H3 Ship a Stripe App
  • H3 Build a platform
  • H3 Upgrade your Stripe SDK
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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)
ElementRatioRequiredFGBGResult
h1 stripe.dev - Stripe …17.14:13.0:1
#000000
#E8E8E8
Pass
h2 Feed17.14:13.0:1
#000000
#E8E8E8
Pass
h2 Get help17.14:13.0:1
#000000
#E8E8E8
Pass
h2 Router17.14:13.0:1
#000000
#E8E8E8
Pass
h3 Accept a payment17.14:13.0:1
#000000
#E8E8E8
Pass
h3 Ship a Stripe App17.14:13.0:1
#000000
#E8E8E8
Pass
h3 Build a platform17.14:13.0:1
#000000
#E8E8E8
Pass
h3 Upgrade your Stripe …17.14:13.0:1
#000000
#E8E8E8
Pass
title Stripe Dot Dev14.17:14.5:1
#000000
#D4D4D4
Pass
a Blog16.21:14.5:1
#000000
#E2E2E2
Pass
a Events17.14:14.5:1
#000000
#E8E8E8
Pass
a Docs17.14:14.5:1
#000000
#E8E8E8
Pass
a Youtube17.14:14.5:1
#000000
#E8E8E8
Pass
a Github17.14:14.5:1
#000000
#E8E8E8
Pass
a Meetups17.14:14.5:1
#000000
#E8E8E8
Pass
button ] Console17.14:14.5:1
#000000
#E8E8E8
Pass
span Welcome17.14:14.5:1
#000000
#E8E8E8
Pass
span Stripe17.14:14.5:1
#000000
#E8E8E8
Pass
span Dot17.14:14.5:1
#000000
#E8E8E8
Pass
p Learn how to build w…17.14:14.5:1
#000000
#E8E8E8
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 96/100 — 1 failing, 22 passed
PASS
96

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.

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
Event (5) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(5) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Video (5) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(5) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Blog (10) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(10) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Agentic (2) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(2) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
AI (5) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(5) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Best Practices (2) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(2) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
CLI (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Crypto (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Developer Productivity (2) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(2) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Engineering (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Event Destinations (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Getting Started (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Infrastructure (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
LLMs (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Meetup (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Partners (2) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(2) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Payments (4) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(4) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Tour (3) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(3) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Workflows (2) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(2) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count
Workshop (1) ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span
(1) li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count

These are opportunities to improve the legibility of your content.

○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.
●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
●Document has a `<title>` element
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○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.
○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.
○`<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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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.

Send Feedback