Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

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.

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

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

6 landmarks

REVIEW

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

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

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 Adyen ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Fintech you can bank on

1.93:1

#000000

#373E40

needs 3.0:1 (large text)

32px · above the fold

h2 Move money across your entire business

2.23:1

#000000

#474647

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Launch payments and financial products u…

2.23:1

#000000

#474647

needs 3.0:1 (large text)

24px · bottom of viewport

h2 When certainty matters, Adyen’s the pl…

2.23:1

#000000

#474647

needs 3.0:1 (large text)

24px · bottom of viewport

h2 If you’re building for scale, there’…

2.23:1

#000000

#474647

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Value Proposition Gallery

2.23:1

#000000

#474647

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Move money across your entire business

2.23:1

#000000

#474647

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Retail

2.23:1

#000000

#474647

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Travel and hospitality

2.23:1

#000000

#474647

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Digital media and content

2.23:1

#000000

#474647

needs 3.0:1 (large text)

19px · bottom of viewport

h3 SaaS platforms and marketplaces

2.23:1

#000000

#474647

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Food and beverage

2.23:1

#000000

#474647

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Financial services

2.23:1

#000000

#474647

needs 3.0:1 (large text)

19px · bottom of viewport

title Adyen: Fintech platform for enterprises …

3.39:1

#000000

#46666E

needs 4.5:1 (normal text)

16px · top of page (header area)

span Products

3.67:1

#000000

#4E6B73

needs 4.5:1 (normal text)

16px · top of page (header area)

span Businesses we serve

3.02:1

#000000

#405E68

needs 4.5:1 (normal text)

16px · top of page (header area)

span About

2.70:1

#000000

#3D5660

needs 4.5:1 (normal text)

16px · top of page (header area)

span Resources

1.96:1

#000000

#30404A

needs 4.5:1 (normal text)

16px · above the fold

span Pricing

1.72:1

#000000

#343631

needs 4.5:1 (normal text)

16px · above the fold

span Contact us

1.63:1

#000000

#30332B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Fintech you can bank…	1.93:1	3.0:1	#000000	#373E40	Fail
h2 Move money across yo…	2.23:1	3.0:1	#000000	#474647	Fail
h2 Launch payments and …	2.23:1	3.0:1	#000000	#474647	Fail
h2 When certainty matte…	2.23:1	3.0:1	#000000	#474647	Fail
h2 If you’re building…	2.23:1	3.0:1	#000000	#474647	Fail
h3 Value Proposition Ga…	2.23:1	3.0:1	#000000	#474647	Fail
h3 Move money across yo…	2.23:1	3.0:1	#000000	#474647	Fail
h3 Retail	2.23:1	3.0:1	#000000	#474647	Fail
h3 Travel and hospitali…	2.23:1	3.0:1	#000000	#474647	Fail
h3 Digital media and co…	2.23:1	3.0:1	#000000	#474647	Fail
h3 SaaS platforms and m…	2.23:1	3.0:1	#000000	#474647	Fail
h3 Food and beverage	2.23:1	3.0:1	#000000	#474647	Fail
h3 Financial services	2.23:1	3.0:1	#000000	#474647	Fail
title Adyen: Fintech platf…	3.39:1	4.5:1	#000000	#46666E	Fail
span Products	3.67:1	4.5:1	#000000	#4E6B73	Fail
span Businesses we serve	3.02:1	4.5:1	#000000	#405E68	Fail
span About	2.70:1	4.5:1	#000000	#3D5660	Fail
span Resources	1.96:1	4.5:1	#000000	#30404A	Fail
span Pricing	1.72:1	4.5:1	#000000	#343631	Fail
span Contact us	1.63:1	4.5:1	#000000	#30332B	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

H1 Fintech you can bank on
H2 Run your business with confidence. Adyen delivers the control, reliability, and expertise global enterprises depend on.
H3 Value Proposition Gallery
H2 Control every aspect of your money. Offer financial products to your customers. All from the same, centralized stack.
H2 Move money across your entire business
H2 Launch payments and financial products under your brand
H3 Move money across your entire business
H2 Different industries. One standard. Businesses across sectors trust Adyen to keep money moving.
H3 Retail
H3 Travel and hospitality
H3 Digital media and content
H3 SaaS platforms and marketplaces
H3 Food and beverage
H3 Financial services
H2 Global scale. Local expertise. Powered by trillions of euros in transaction data.
H2 When certainty matters, Adyen’s the platform of choice
H2 If you’re building for scale, there’s no alternative

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 decorative image(s) correctly marked

5 images 5 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.

Link & Button Quality

43 links, 43 buttons — all OK

PASS

43 links, 43 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://www.facebook.com/AdyenPayments/; https://www.linkedin.com/company/adyen; https://x.com/Adyen

40 link(s) with descriptive text

43 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/AdyenPayments/	Visit our Facebook page	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/adyen	Visit our Linkedin page	new tab	Add '(opens in new tab)' to text
https://x.com/Adyen	Visit our Twitter page	new tab	Add '(opens in new tab)' to text

83 links and buttons have descriptive text

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

https://www.facebook.com/AdyenPayments/; https://www.linkedin.com/company/adyen; https://x.com/Adyen

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

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 25 passed

PASS

100

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.

○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

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

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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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