Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 3 REVIEW 3 FIX

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.

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

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Plaid

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Plaid ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name Plaid Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Landmark Structure

21 landmarks

PASS

21 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

20 headings

PASS

20 headings

Single H1 present

H1 Open a world of financial solutions
H2 The gold standard in account linking
H2 The gold standard in account linking
H2 Low-cost, secure payments in an instant
H2 Low-cost, secure payments in an instant
H2 Clean, organised financial data
H2 Clean, organised financial data
H2 Cash flow data for smarter underwriting
H2 Cash flow data for smarter underwriting
H2 A network that getsmore powerful daily
H2 A network that getsmore powerful daily
H2 Want access to 12K banks?We’ve got the API keys.
H2 Want access to 12K banks?We’ve got the API keys.
H3 See what’s possible with Plaid
H2 More customers.Fewer fraudsters.Higher revenue.
H3 Let’s get started
H2 Products
H2 Use cases
H2 Resources
H2 Developers

A+

Alt Text Quality

1 of 46 images have issues

PASS

1 of 46 images have issues

1 image(s) with generic alt text

1 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

43 image(s) with good alt text

46 images 43 good alt text 1 decorative 1 generic

Issue	Count
generic	1 image(s)
too long	1 image(s)

Form Accessibility

1 of 8 controls have issues

PASS

1 of 8 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">

7 control(s) properly labeled

8 controls

7 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#FirstName-:R6j6n6ll6ladal56:	text	First name	for/id
#LastName-:Raj6n6ll6ladal56:	text	Last name	for/id
#Company-:R6l6n6ll6ladal56:	text	Company name	for/id
#Email-:Ral6n6ll6ladal56:	text	Company email	for/id
#EU_Employee_Estimate_Size__c-:Rel6n6ll6ladal56:-input	text	Employee count	for/id
#Country-:R1mn6n6ll6ladal56:-input	text	Country	for/id
#Phone-:Ran6n6ll6ladal56:	text	Phone number (optional)	for/id
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+

Link & Button Quality

1 issue(s) across 84 links and 24 buttons

PASS

1 issue(s) across 84 links and 24 buttons

1 link(s) with generic text

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

Got: /en-eu/plaid-link/ ("Link")

83 link(s) with descriptive text

84 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/en-eu/plaid-link/	Link	generic text	Replace with descriptive text
Before: Link Suggested: Plaid Link

107 links and buttons have descriptive text

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

/en-eu/plaid-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

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
h1 Open a world of fina…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 The gold standard in…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 The gold standard in…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Low-cost, secure pay…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Low-cost, secure pay…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Clean, organised fin…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Clean, organised fin…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Cash flow data for s…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Cash flow data for s…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 A network that gets	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 more powerful daily	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 A network that gets	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 more powerful daily	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Want access to 12K b…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 We’ve got the API …	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Want access to 12K b…	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 We’ve got the API …	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 More customers.	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Fewer fraudsters.	13.29:1	3.0:1	#000000	#3CE5CE	Pass
h2 Higher revenue.	13.29:1	3.0:1	#000000	#3CE5CE	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 — 0 failing, 29 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

●Form elements have associated labels

●`[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 are distinguishable without relying on color.

●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

●ARIA IDs are unique

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○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

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

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