Skip to content
https://nuxt.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ 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::
2 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 2 <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.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 CONTENTINFO footer

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #020420
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 Not set ✗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 Full-Stack
1.04:1
#000000
on
#020618
needs 3.0:1 (large text)
32px · above the fold
h2 Chosen by leading companies worldwide
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Everything you need, nothing you don't
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted by developers worldwide
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Deploy anywhere
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built by developers around the world
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Real-world Web Applications built with N…
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sponsors
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Community
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Explore
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enterprise
1.10:1
#000000
on
#090F22
needs 3.0:1 (large text)
19px · bottom of viewport
title Nuxt: The Full-Stack Vue Framework
1.04:1
#000000
on
#010518
needs 4.5:1 (normal text)
16px · top of page (header area)
span v4.4.2
1.04:1
#000000
on
#010518
needs 4.5:1 (normal text)
16px · top of page (header area)
span Docs
1.31:1
#000000
on
#022628
needs 4.5:1 (normal text)
16px · top of page (header area)
span Modules
1.06:1
#000000
on
#020A1A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Templates
1.04:1
#000000
on
#020618
needs 4.5:1 (normal text)
16px · above the fold
span Resources
1.04:1
#000000
on
#020618
needs 4.5:1 (normal text)
16px · above the fold
span Enterprise
1.04:1
#000000
on
#020618
needs 4.5:1 (normal text)
16px · above the fold
span Updates
1.04:1
#000000
on
#020618
needs 4.5:1 (normal text)
16px · above the fold
span Search…
1.04:1
#000000
on
#020618
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Full-Stack1.04:13.0:1
#000000
#020618
Fail
h2 Chosen by leading co…1.10:13.0:1
#000000
#090F22
Fail
h2 Everything you need,…1.10:13.0:1
#000000
#090F22
Fail
h2 Trusted by developer…1.10:13.0:1
#000000
#090F22
Fail
h2 Deploy anywhere1.10:13.0:1
#000000
#090F22
Fail
h2 Built by developers …1.10:13.0:1
#000000
#090F22
Fail
h2 Real-world Web Appli…1.10:13.0:1
#000000
#090F22
Fail
h2 Sponsors1.10:13.0:1
#000000
#090F22
Fail
h3 Community1.10:13.0:1
#000000
#090F22
Fail
h3 Explore1.10:13.0:1
#000000
#090F22
Fail
h3 Enterprise1.10:13.0:1
#000000
#090F22
Fail
title Nuxt: The Full-Stack…1.04:14.5:1
#000000
#010518
Fail
span v4.4.21.04:14.5:1
#000000
#010518
Fail
span Docs1.31:14.5:1
#000000
#022628
Fail
span Modules1.06:14.5:1
#000000
#020A1A
Fail
span Templates1.04:14.5:1
#000000
#020618
Fail
span Resources1.04:14.5:1
#000000
#020618
Fail
span Enterprise1.04:14.5:1
#000000
#020618
Fail
span Updates1.04:14.5:1
#000000
#020618
Fail
span Search…1.04:14.5:1
#000000
#020618
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
13 headings
PASS
13 headings
Info::
Single H1 present
  • H1 The Full-StackVue Framework
  • H2 Chosen by leading companies worldwide
  • H2 Everything you need, nothing you don't
  • H2 Built on proven tools
  • H2 Trusted by developers worldwide
  • H2 Extend Nuxt with plug & play modules
  • H2 Deploy anywhere
  • H2 Built by developers around the world
  • H2 Real-world Web Applications built with Nuxt
  • H2 Sponsors
  • H3 Community
  • H3 Explore
  • H3 Enterprise
A
Alt Text Quality
2 of 39 images have issues
PASS
2 of 39 images have issues
Warning::
2 image(s) with generic alt text
Info::
37 image(s) with good alt text
39 images 37 good alt text 2 generic
IssueCount
generic2 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtextnone
#v-0-0-4emailSubscribe to our newsletterfor/id
A+
Lighthouse Accessibility Audits
Score 95/100 — 1 failing, 28 passed
PASS
95

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Minimal div.relative > div.flex > div.relative > button#reka-tabs-v-0-0-14-0-trigger-0

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

○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
●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
●`[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
●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 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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback