Skip to content
https://www.vercel.com/templates

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-ue2xtk
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
Warning::
Manifest contains invalid JSON
Manifest at https://www.vercel.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://www.vercel.com/manifest.json

Manifest contains invalid JSON.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main" MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

B
Favicon & Branding
10 icon(s) detected
REVIEW
10 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 21 passed
REVIEW
84

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
Get started with Next.js and React in seconds. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An image gallery built on Next.js and Cloudinary. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Simple, powerful and flexible markdown-powered docs site. Built with Next.js. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Deploy Hono backends using the Bun runtime. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
This template creates a voice chat using Hume AI's Empathic Voice Interface. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Starter kit for high-performance commerce with Shopify. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An inbound lead qualification and research agent built with Next.js, AI SDK, Wo… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Examples of many Next.js App Router features. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Easily create a portfolio with Next.js and Markdown. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An Incremental Static Regeneration Blog Example Using Next.js and WordPress div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Enterprise-grade Next.js boilerplate built with Tailwind CSS, Radix UI, TypeScr… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A statically generated blog example using Next.js and Markdown. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A blog template with Next.js 13 App Router, Contentlayer, Tailwind CSS and dark… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Use a Large Language Model to summarize customer feedback. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A Nuxt.js 3 app, bootstrapped with create-nuxt-app. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An AI chatbot template to build your own chatbot powered by Nuxt MDC and Vercel… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
AI answer engine with Generative UI. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A personal website built with Next.js and Sanity featuring visual editing, live… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A clean Next.js + Sanity starter with visual editing, drag-and-drop page builde… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A Next.js starter chatbot using Vercel's AI SDK and implements the Retrieval-Au… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Real-time collaborative product starter kit built with Next.js and Liveblocks div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A link-in-bio SaaS built with Nuxt.js, where the data lives in the URL – no dat… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
The all-in-one subscription starter kit for high-performance SaaS applications,… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
QrGPT is an AI tool for you to generate beautiful QR codes using AI with one cl… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A SvelteKit app including nested routes, layouts, and page endpoints. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A Next.js App Router template configured with cookie-based auth using Supabase,… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Next.js Boilerplate a.link-module__Q1NRQq__link > div.flex > div.flex > h3.text-heading-16

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Vercel logo nav > div.grid > div > ul.list-none

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.geist_mono_98cac566-module__bcNCwW__className html.geist_mono_98cac566-module__bcNCwW__className

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
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
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.
Deprecated ARIA roles were not used
ARIA IDs are unique
`[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
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.
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.
A
Heading Hierarchy
59 headings, 1 skip(s)
PASS
59 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 AI Cloud
  • H5 Core Platform
  • H5 Security
  • H5 Company
  • H5 Learn
  • H5 Open Source
  • H5 Use Cases
  • H5 Tools
  • H5 Users
  • H1 Find your Template
  • H4 Filter Templates skipped
  • H4 Use Case
  • H4 Framework
  • H4 CSS
  • H4 Database
  • H4 CMS
  • H4 Authentication
  • H4 Experimentation
  • H3 Next.js Boilerplate
  • H3 Image Gallery Starter
  • H3 Chatbot
  • H3 Nextra: Docs Starter Kit
  • H3 Express on Bun
  • H3 Hono on Bun
  • H3 Hume AI - Empathic Voice Interface Starter
  • H3 Next.js Commerce
  • H3 Lead Agent
  • H3 Next.js App Router Playground
  • H3 Platforms Starter Kit
  • H3 Portfolio Starter Kit
  • H3 Slack Agent Template
  • H3 ISR Blog with Next.js and WordPress
  • H3 Next.js Enterprise Boilerplate
  • H3 Blog Starter Kit
  • H3 Next.js Contentlayer Blog Starter
  • H3 Customer Reviews AI Summary
  • H3 Nuxt.js 3 Boilerplate
  • H3 Nuxt AI Chatbot
  • H3 Morphic: AI-powered answer engine
  • H3 Sanity + Next.js Personal Website
  • H3 Sanity + Next.js Clean App
  • H3 Pinecone - Vercel AI SDK Starter
  • H3 Liveblocks Starter Kit
  • H3 Onelink
  • H3 Stripe Subscription Starter
  • H3 qrGPT – AI QR Code Generator
  • H3 SvelteKit Boilerplate
  • H3 Supabase Starter
  • H2 Get Started
  • H2 Build
  • H2 Scale
  • H2 Secure
  • H2 Resources
  • H2 Learn
  • H2 Frameworks
  • H2 SDKs
  • H2 Use Cases
  • H2 Company
  • H2 Community

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Alt Text Quality
All 32 images OK
PASS
All 32 images OK
Info::
32 image(s) with good alt text
32 images 32 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 29 controls labeled
PASS
All 29 controls labeled
Info::
29 control(s) properly labeled
29 controls
29 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#input-_R_1bfiram_searchSearcharia-label
#checkbox-_R_ccvfiram_checkboxnone
#checkbox-_R_kcvfiram_checkboxnone
#checkbox-_R_scvfiram_checkboxnone
#checkbox-_R_14cvfiram_checkboxnone
#checkbox-_R_1ccvfiram_checkboxnone
#checkbox-_R_1kcvfiram_checkboxnone
#checkbox-_R_1scvfiram_checkboxnone
#checkbox-_R_24cvfiram_checkboxnone
#checkbox-_R_2ccvfiram_checkboxnone
#checkbox-_R_2kcvfiram_checkboxnone
#checkbox-_R_2scvfiram_checkboxnone
#checkbox-_R_34cvfiram_checkboxnone
#checkbox-_R_3ccvfiram_checkboxnone
#checkbox-_R_3kcvfiram_checkboxnone
#checkbox-_R_3scvfiram_checkboxnone
#checkbox-_R_44cvfiram_checkboxnone
#checkbox-_R_4ccvfiram_checkboxnone
#checkbox-_R_4kcvfiram_checkboxnone
#checkbox-_R_4scvfiram_checkboxnone
#checkbox-_R_54cvfiram_checkboxnone
#checkbox-_R_5ccvfiram_checkboxnone
#checkbox-_R_5kcvfiram_checkboxnone
#checkbox-_R_5scvfiram_checkboxnone
#checkbox-_R_64cvfiram_checkboxnone
#checkbox-_R_6ccvfiram_checkboxnone
#theme-switch-system-_R_aniram_radiosystemaria-label
#theme-switch-light-_R_aniram_radiolightaria-label
#theme-switch-dark-_R_aniram_radiodarkaria-label
A+
Dark Mode Support
Full dark mode support
PASS
Full dark mode support
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 Detected Dark theme-color #ffffff CSS indicators Detected

Detection limited to meta tags and inline styles.

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 Find your Template21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get Started21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Build21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Scale21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secure21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Learn21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Frameworks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SDKs21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Use Cases21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Community21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Next.js Boilerplate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Image Gallery Starte…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Chatbot21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nextra: Docs Starter…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Express on Bun21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hono on Bun21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hume AI - Empathic V…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Next.js Commerce21.00:13.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback