Skip to content
https://vitejs.dev

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 | Vite ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV "main-nav-aria-label" 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

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

C
Heading Hierarchy
Action
18 headings, 3 skip(s)
REVIEW
18 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 The Build Tool for the Web
  • H6 Trusted by the world's best software teams skipped
  • H2 Redefining developer experience
  • H5 Instant Server Start skipped
  • H5 Lightning Fast HMR
  • H5 Rich Features Out of the Box
  • H5 Optimized Build
  • H2 A shared foundation to build upon
  • H5 Flexible Plugin System skipped
  • H5 Fully Typed API
  • H5 First class SSR Support
  • H5 Continuous ecosystem integration
  • H2 Powering your favorite frameworks and tools
  • H3 Loved by the community
  • H2 75k+
  • H2 40m+
  • H3 Free & open source
  • H2 Start building with Vite

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

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

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

B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗Dark theme-color #646cff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
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 The Build Tool for the Web
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Redefining developer experience
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 A shared foundation to build upon
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Powering your favorite frameworks and to…
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 75k+
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 40m+
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start building with Vite
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Loved by the community
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Free & open source
1.17:1
#000000
on
#16171D
needs 3.0:1 (large text)
19px · bottom of viewport
title Vite | Next Generation Frontend Tooling
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Announcing Vite+ Alpha: Open source. Uni…
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Main Navigation
1.39:1
#000000
on
#28252E
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Guide
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Config
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · above the fold
span Plugins
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · above the fold
span Resources
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · above the fold
span Team
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · above the fold
span Blog
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · above the fold
span Releases
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · above the fold
span Acknowledgements
1.17:1
#000000
on
#16171D
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Build Tool for t…1.17:13.0:1
#000000
#16171D
Fail
h2 Redefining developer…1.17:13.0:1
#000000
#16171D
Fail
h2 A shared foundation …1.17:13.0:1
#000000
#16171D
Fail
h2 Powering your favori…1.17:13.0:1
#000000
#16171D
Fail
h2 75k+1.17:13.0:1
#000000
#16171D
Fail
h2 40m+1.17:13.0:1
#000000
#16171D
Fail
h2 Start building with …1.17:13.0:1
#000000
#16171D
Fail
h3 Loved by the communi…1.17:13.0:1
#000000
#16171D
Fail
h3 Free & open source1.17:13.0:1
#000000
#16171D
Fail
title Vite | Next Generati…1.17:14.5:1
#000000
#16171D
Fail
span Announcing Vite+ Alp…1.17:14.5:1
#000000
#16171D
Fail
span Main Navigation1.39:14.5:1
#000000
#28252E
Fail
span Guide1.17:14.5:1
#000000
#16171D
Fail
span Config1.17:14.5:1
#000000
#16171D
Fail
span Plugins1.17:14.5:1
#000000
#16171D
Fail
span Resources1.17:14.5:1
#000000
#16171D
Fail
span Team1.17:14.5:1
#000000
#16171D
Fail
span Blog1.17:14.5:1
#000000
#16171D
Fail
span Releases1.17:14.5:1
#000000
#16171D
Fail
span Acknowledgements1.17:14.5:1
#000000
#16171D
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+
Alt Text Quality
All 39 images OK
PASS
All 39 images OK
Info::
4 decorative image(s) correctly marked
Info::
35 image(s) with good alt text
39 images 35 good alt text 4 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#tab-xp4vn-0radionpmfor/id
#tab-xp4vn-1radioYarnfor/id
#tab-xp4vn-2radiopnpmfor/id
#tab-xp4vn-3radioBunfor/id
#tab-xp4vn-4radioDenofor/id
A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 18 passed
PASS
96

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.

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
Trusted by the world's best software teams div > div > section.wrapper > h6.text-center
Instant Server Start section.wrapper > div.flex > div.p-5 > h5.text-balance
Flexible Plugin System div > section.wrapper > div.p-5 > h5.text-balance

These are opportunities to improve keyboard navigation in your application.

Best practices

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 html

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>`
●`[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
●Touch targets have sufficient size and spacing.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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 have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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.
○No element has a `[tabindex]` value greater than 0
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback