Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 33 -1-on-focusable

FIX

0 positive, 33 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

D

Mobile-Readable Font Sizes

Action

69% of visible text renders at >= 12 CSS px (133 below threshold)

FIX

69% of visible text renders at >= 12 CSS px (133 below threshold)

133 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 10.0px ("Pay Roastery"); <div> 10.0px ("Cartsy bezahlen"); <div> 10.0px ("Showflix に支払う"); <div> 10.0px ("Pay Roastery"); <div> 10.0px ("Tap, insert, or swipe to pay").

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

No dark mode signals

FIX

No dark mode signals

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

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

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

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

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.

C

Link & Button Quality

Action

29 issue(s) across 178 links and 29 buttons

REVIEW

29 issue(s) across 178 links and 29 buttons

28 link(s) with no accessible text

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

Got: /newsroom/news/stripe-openai-instant-checkout; /customers/amazon; /newsroom/news/nvidia-collaboration-with-stripe; /newsroom/news/stripe-ford-agreement; /newsroom/news/google-and-stripe; /customers/shopify; /customers/mindbody; /customers/ramp; /customers/figma; /customers/woo (+18 more)

1 link(s) with generic text

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

Got: /payments/link ("Link")

1 link(s) open in new tab without warning

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

Got: https://status.stripe.com

148 link(s) with descriptive text

178 links

28 empty

1 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/newsroom/news/stripe-openai-instant-che…	(empty)	empty	Add link text or aria-label
/customers/amazon	(empty)	empty	Add link text or aria-label
/newsroom/news/nvidia-collaboration-with…	(empty)	empty	Add link text or aria-label
/newsroom/news/stripe-ford-agreement	(empty)	empty	Add link text or aria-label
/newsroom/news/google-and-stripe	(empty)	empty	Add link text or aria-label
/customers/shopify	(empty)	empty	Add link text or aria-label
/customers/mindbody	(empty)	empty	Add link text or aria-label
/customers/ramp	(empty)	empty	Add link text or aria-label
/customers/figma	(empty)	empty	Add link text or aria-label
/customers/woo	(empty)	empty	Add link text or aria-label
/newsroom/news/stripe-and-uber	(empty)	empty	Add link text or aria-label
/customers/anthropic	(empty)	empty	Add link text or aria-label
/customers/lightspeed-terminal	(empty)	empty	Add link text or aria-label
/customers/cursor	(empty)	empty	Add link text or aria-label
/newsroom/news/stripe-openai-instant-che…	(empty)	empty	Add link text or aria-label
/customers/amazon	(empty)	empty	Add link text or aria-label
/newsroom/news/nvidia-collaboration-with…	(empty)	empty	Add link text or aria-label
/newsroom/news/stripe-ford-agreement	(empty)	empty	Add link text or aria-label
/newsroom/news/google-and-stripe	(empty)	empty	Add link text or aria-label
/customers/shopify	(empty)	empty	Add link text or aria-label
/customers/mindbody	(empty)	empty	Add link text or aria-label
/customers/ramp	(empty)	empty	Add link text or aria-label
/customers/figma	(empty)	empty	Add link text or aria-label
/customers/woo	(empty)	empty	Add link text or aria-label
/newsroom/news/stripe-and-uber	(empty)	empty	Add link text or aria-label
/customers/anthropic	(empty)	empty	Add link text or aria-label
/customers/lightspeed-terminal	(empty)	empty	Add link text or aria-label
/customers/cursor	(empty)	empty	Add link text or aria-label
https://status.stripe.com	historical uptime	new tab	Add '(opens in new tab)' to text
/customers/lovable	Lovable grows into a vibe-codi…	img no alt	Add alt attribute to the image
/customers/runway	Runway protects developer time…	img no alt	Add alt attribute to the image
/customers/supabase	Supabase delivers its backend-…	img no alt	Add alt attribute to the image
/customers/linear	Linear partners with Stripe to…	img no alt	Add alt attribute to the image
/customers/elevenlabs	ElevenLabs grows into a $3B AI…	img no alt	Add alt attribute to the image
/customers/browserbase	Browserbase offers usage-based…	img no alt	Add alt attribute to the image
/customers/decagon	Decagon decreases support cost…	img no alt	Add alt attribute to the image
/startups#application	Stripe Startups program.Access…	img no alt	Add alt attribute to the image
https://worksinprogress.co/	Works in Progress	img no alt	Add alt attribute to the image
/payments/link	Link	generic text	Replace with descriptive text
Before: Link Suggested: Link

177 links and buttons have descriptive text

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

/newsroom/news/stripe-openai-instant-checkout; /customers/amazon; /newsroom/news/nvidia-collaboration-with-stripe; /newsroom/news/stripe-ford-agreement; /newsroom/news/google-and-stripe; /customers/shopify; /customers/mindbody; /customers/ramp; /customers/figma; /customers/woo (+18 more)

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.

/payments/link ("Link")

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://status.stripe.com

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

B

Iframe Accessibility

2/2 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/2 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Stripe logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

A

Landmark Structure

14 landmarks

PASS

14 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

Heading Hierarchy

57 headings

PASS

57 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

1 hidden heading(s) (aria-hidden)

H1 Financial infrastructure to grow your revenue. Accept payments, offer financial services, and implement custom revenue models—from your first transaction to your billionth.
H1 Financial infrastructure to grow your revenue. Accept payments, offer financial services, and implement custom revenue models—from your first transaction to your billionth. hidden
H2 Flexible solutions for every business model.
H3 Accept and optimize payments globally—online and in person
H3 Enable any billing model
H3 Monetize through agentic commerce
H3 Create a card issuing program
H3 Access borderless money movement with stablecoins and crypto
H3 Embed payments in your platform
H3 Not sure where to start?
H2 The backbone of global commerce
H2 Powering businesses of all sizes.
H3 Transform your enterprise with agile financial infrastructure
H3 Hertz unifies commerce with Stripe.
H3 URBN consolidates $5 billion in online and in-store revenue onto Stripe.
H3 Instacart powers online grocery delivery with Stripe.
H3 Le Monde improves local and international payments with Stripe.
H4 Professional services.
H4 Stripe-certified experts.
H4 Support plans.
H3 Build a foundation for your startup that enables faster growth
H4 Lovable grows into a vibe-coding juggernaut with Stripe.
H4 Runway protects developer time with no-code solutions from Stripe.
H4 Supabase delivers its backend-as-a-service to 150 countries with Stripe.
H4 Linear partners with Stripe to handle billing and payments.
H4 ElevenLabs grows into a $3B AI audio leader with Stripe.
H4 Browserbase offers usage-based billing for an AI agent browser with Stripe.
H4 Decagon decreases support costs by 65% with Stripe-integrated agents.
H4 Stripe Startups program.
H4 Stripe Atlas.
H3 Make your SaaS platform a complete financial operating system
H4 Get to market faster.
H4 Grow new lines of revenue.
H4 Manage platform risk.
H2 Reliable, extensible infrastructure for every stack.
H3 Connect to existing systems.
H3 Scale with confidence.
H4 500M+
H4 10K+
H4 150K+
H3 Choose an integration path.
H4 Don’t code?
H4 Use a pre-integrated platform.
H4 Build your own integration.
H2 What’s happening
H3 Businesses on Stripe generated $1.9T in 2025.
H3 150K+ users have their best day ever on Stripe.
H3 Tidemark’s vertical and SMB SaaS benchmark report.
H3 Shopify’s Tobi Lütke sits down with John Collison.
H3 New tools to process payments outside app stores.
H3 Crypto.com partners with Stripe to enable better crypto payments.
H3 Make your products shoppable through AI platforms.
H3 How leading retailers unify customer experiences and drive growth.
H3 Book of the week
H4 (empty)
H4 See what you’ll pay
H4 Start building

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A

Alt Text Quality

All 46 images OK

PASS

All 46 images OK

3 image(s) with alt text over 125 characters

38 decorative image(s) correctly marked

5 image(s) with good alt text

46 images 5 good alt text 38 decorative

Issue	Count
too long	3 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

3 mobile-depth signal(s) detected

PASS

3 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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 Flexible solutions f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The backbone of glo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Powering businesses …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Reliable, extensible…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What’s happening	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Accept and optimize …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Enable any billing m…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Monetize through age…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Create a card issuin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Access borderless mo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Embed payments in yo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Not sure where to st…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Transform your enter…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hertz unifies commer…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 URBN consolidates $5…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Instacart powers onl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Le Monde improves lo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Build a foundation f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Make your SaaS platf…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Connect to existing …	21.00:1	3.0:1	#000000	#FFFFFF	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 100/100 — 1 failing, 27 passed

PASS

100

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.

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
Accept and optimize payments globally—online and in person Pay Roastery Cartsy … `div.modular-solutions-bento > div.modular-solutions-bento__content > div.modular-solutions-bento__layout > button.modular-solutions-bento-card`
Enable any billing model Pro Plan Billed monthly Tokens $0.01 per 1,000 units U… `div.modular-solutions-bento > div.modular-solutions-bento__content > div.modular-solutions-bento__layout > button.modular-solutions-bento-card`
Read the story `div#customer-Hertz > div#detail-customer-content-Hertz > div.customer-stories__customer-content--read > a#customer-content-Hertz`
Read the story `div#customer-URBN > div#detail-customer-content-URBN > div.customer-stories__customer-content--read > a#customer-content-URBN`
Read the story `div#customer-Instacart > div#detail-customer-content-Instacart > div.customer-stories__customer-content--read > a#customer-content-Instacart`
Read the story `div#customer-LeMonde > div#detail-customer-content-LeMonde > div.customer-stories__customer-content--read > a#customer-content-LeMonde`

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●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

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

○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

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

○Tables have different content in the summary attribute and `<caption>`.

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