Accessibility

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-po2uri

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

Got: https://vercel.com/manifest.json

Manifest contains invalid JSON.

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 3 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

B

Mobile-Readable Font Sizes

93% of visible text renders at >= 12 CSS px (10 below threshold)

REVIEW

93% of visible text renders at >= 12 CSS px (10 below threshold)

10 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: <p> 11.0px ("Iss 2026"); <span> 11.0px ("New"); <span> 11.0px ("New"); <span> 11.0px ("New"); <span> 11.0px ("New").

B

Favicon & Branding

11 icon(s) detected

REVIEW

11 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

Landmark Structure

12 landmarks

PASS

12 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Skip link target(s) don't exist on page: #geist-skip-nav

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

30 headings

PASS

30 headings

Single H1 present

H5 Agent Stack
H5 Core Platform
H5 Tools
H5 Learn
H5 Build
H5 Explore
H3 Agent Stack
H3 Core Platform
H3 Tools
H3 Learn
H3 Build
H3 Explore
H1 Agentic Infrastructure
H2 Build agents on infrastructure that thinks like them
H2 Ship apps that scale from zero to millions instantly
H2 Host platforms that serve every customer
H2 Recently shipped
H2 Built by you, or your agents
H2 Agent Stack
H2 Core Platform
H2 Security
H2 Tools
H2 Frameworks
H2 SDKs
H2 Build
H2 Learn
H2 Explore
H2 Company
H2 Legal & Trust
H2 Social

A+

Heading Text Quality

All 30 heading(s) have substantive, well-formed text

PASS

All 30 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

1 decorative image(s) correctly marked

16 image(s) with good alt text

17 images 16 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#theme-switch-system-_R_lb5tj9abqpfivb_	radio	system	aria-label
#theme-switch-light-_R_lb5tj9abqpfivb_	radio	light	aria-label
#theme-switch-dark-_R_lb5tj9abqpfivb_	radio	dark	aria-label

A

Link & Button Quality

166 links, 10 buttons — all OK

PASS

166 links, 10 buttons — all OK

21 link(s) open in new tab without warning

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

Got: https://vercel.com/domains; https://v0.app; https://community.vercel.com/; https://vercel.com/domains; https://v0.app; https://community.vercel.com/; https://vercel.com/blog/dockerfile-on-vercel; https://skills.sh; https://v0.app; https://eve.dev/ (+11 more)

145 link(s) with descriptive text

166 links

0 empty

0 generic text

21 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://vercel.com/domains	Domains↗	new tab	Add '(opens in new tab)' to text
https://v0.app	v0↗	new tab	Add '(opens in new tab)' to text
https://community.vercel.com/	Community↗	new tab	Add '(opens in new tab)' to text
https://vercel.com/domains	Domains↗	new tab	Add '(opens in new tab)' to text
https://v0.app	v0↗	new tab	Add '(opens in new tab)' to text
https://community.vercel.com/	Community↗	new tab	Add '(opens in new tab)' to text
https://vercel.com/blog/dockerfile-on-ve…	▲ vercel deployVercel CLI✓…	new tab	Add '(opens in new tab)' to text
https://skills.sh	Agent Skills	new tab	Add '(opens in new tab)' to text
https://v0.app	v0	new tab	Add '(opens in new tab)' to text
https://eve.dev/	eveNew	new tab	Add '(opens in new tab)' to text
https://streamdown.ai	Streamdown	new tab	Add '(opens in new tab)' to text
https://community.vercel.com	Community	new tab	Add '(opens in new tab)' to text
https://is-agentic.com	Is Agentic	new tab	Add '(opens in new tab)' to text
https://security.vercel.com	Trust Center	new tab	Add '(opens in new tab)' to text
https://vercel-status.com	Status	new tab	Add '(opens in new tab)' to text
https://github.com/vercel	GitHub	new tab	Add '(opens in new tab)' to text
https://x.com/vercel	X	new tab	Add '(opens in new tab)' to text
https://linkedin.com/company/vercel	LinkedIn	new tab	Add '(opens in new tab)' to text
https://youtube.com/@VercelHQ	YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/vercel/	Instagram	new tab	Add '(opens in new tab)' to text
https://vercel-status.com	Loading status…	new tab	Add '(opens in new tab)' to text

155 links and buttons have descriptive text

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

https://vercel.com/domains; https://v0.app; https://community.vercel.com/; https://vercel.com/domains; https://v0.app; https://community.vercel.com/; https://vercel.com/blog/dockerfile-on-vercel; https://skills.sh; https://v0.app; https://eve.dev/ (+11 more)

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+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

16 explicit tabindex attribute(s) checked, no anti-patterns

PASS

16 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: dark light

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta dark light ✓Dark theme-color #fafafa ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

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 Agentic Infrastructu…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Build agents on infr…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Ship apps that scale…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Host platforms that …	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Recently shipped	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Built by you, or you…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Agent Stack	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Core Platform	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Security	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Tools	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Frameworks	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 SDKs	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Build	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Learn	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Explore	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Company	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Legal & Trust	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Social	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Agent Stack	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Core Platform	20.12:1	3.0:1	#000000	#FAFAFA	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 95/100 — 1 failing, 25 passed

PASS

95

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●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

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

○Input buttons have discernible text.

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

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

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