Skip to content
https://tailwindcss.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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 (missing!) 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

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 Tailwind CSS - Rapidly build modern websites without ever leaving your HTML. ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Alt Text Quality
2 of 43 images have issues
REVIEW
2 of 43 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
26 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
43 images 15 good alt text 26 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Favicon & Branding
8 icon(s) detected
REVIEW
8 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 Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Tailwind CSS
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name Tailwind CSS ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name Tailwind CSS Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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 Detected ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 86/100 — 5 failing, 24 passed
REVIEW
86

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
index.html div.flex > div.isolate > div.sticky > button.isolate
Terminal div.flex > div.isolate > div.sticky > button.isolate
build.css div.flex > div.isolate > div.sticky > button.isolate

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.

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
text-4xl text-gray-950 tracking-tighter div.grid > div.grid > div > div.flex
text-4xl div.grid > div > div.flex > span.hidden
text-gray-950 div.grid > div > div.flex > span.inline
text-lg text-gray-950 font-medium div.grid > div.grid > div > div.flex
text-gray-950 div.grid > div > div.flex > span.inline
Quick search Ctrl K div > div.mt-4 > div.flex > button.grid
SPONSORS div.grid > div.relative > div.2xl:before:hidden > p.text-sky-500
text-base text-gray-950 div.grid > div.grid > div.relative > div.flex
text-gray-950 div.grid > div.relative > div.flex > span.inline
WHY TAILWIND CSS? div.grid > div.relative > div.2xl:before:hidden > p.text-pink-500
text-base text-gray-950 div.grid > div.grid > div.relative > div.flex
text-gray-950 div.grid > div.relative > div.flex > span.inline
HOW IT WORKS div.grid > div.relative > div.2xl:before:hidden > p.text-sky-500
text-base text-gray-950 div.grid > div.grid > div.relative > div.flex
text-gray-950 div.grid > div.relative > div.flex > span.inline
text-4xl text-gray-950 tracking-tighter div.grid > div.grid > div.relative > div.h-6
text-gray-950 div.grid > div.relative > div.h-6 > span.inline
TAILWIND IN THE WILD div.grid > div.relative > div.2xl:before:hidden > p.text-fuchsia-500
text-base text-gray-950 div.grid > div.grid > div.relative > div.flex
text-gray-950 div.grid > div.relative > div.flex > span.inline
text-base text-gray-950 div.grid > div.grid > div.relative > div.flex
text-gray-950 div.grid > div.relative > div.flex > span.inline

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.isolate > div.relative > div.col-start-1 > img.absolute div.isolate > div.relative > div.col-start-1 > img.absolute
div.isolate > div.relative > div.col-start-1 > img div.isolate > div.relative > div.col-start-1 > img

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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.inter_6a166f28-module__775SPq__variable html.inter_6a166f28-module__775SPq__variable

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
v4.2 div.bg-white > div.flex > div.flex > button#headlessui-menu-button-_R_ualulb_
○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-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 have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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
●ARIA toggle fields have accessible names
●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
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[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 `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.
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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
16 headings
PASS
16 headings
Info::
Single H1 present
  • H1 Rapidly build modern websites without ever leaving your HTML.
  • H2 Supported by the best.
  • H2 Built for the modern web.
  • H3 Browse properties
  • H3 Redefining real-time performance
  • H2 Ship faster and smaller.
  • H2 Build whatever you want, without touching your CSS file.
  • H2 Move even faster with Tailwind Plus.
  • H3 Tailwind CSS
  • H3 Resources
  • H3 Tailwind Plus
  • H3 Community
  • H3 Tailwind CSS
  • H3 Tailwind Plus
  • H3 Resources
  • H3 Community
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 Rapidly build modern…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Supported by the bes…18.77:13.0:1
#000000
#F2F2F3
Pass
h2 Built for the modern…18.77:13.0:1
#000000
#F2F2F3
Pass
h2 Ship faster and smal…18.77:13.0:1
#000000
#F2F2F3
Pass
h2 Build whatever you w…18.77:13.0:1
#000000
#F2F2F3
Pass
h2 Move even faster wit…18.77:13.0:1
#000000
#F2F2F3
Pass
h3 Browse properties18.77:13.0:1
#000000
#F2F2F3
Pass
h3 Redefining real-time…18.77:13.0:1
#000000
#F2F2F3
Pass
h3 Tailwind CSS18.77:13.0:1
#000000
#F2F2F3
Pass
h3 Resources18.77:13.0:1
#000000
#F2F2F3
Pass
h3 Community18.77:13.0:1
#000000
#F2F2F3
Pass
h3 Tailwind CSS18.77:13.0:1
#000000
#F2F2F3
Pass
h3 Resources18.77:13.0:1
#000000
#F2F2F3
Pass
h3 Community18.77:13.0:1
#000000
#F2F2F3
Pass
title Tailwind CSS - Rapid…21.00:14.5:1
#000000
#FFFFFF
Pass
button 4.221.00:14.5:1
#000000
#FFFFFF
Pass
kbd ⌘K21.00:14.5:1
#000000
#FFFFFF
Pass
kbd Ctrl K21.00:14.5:1
#000000
#FFFFFF
Pass
a Docs21.00:14.5:1
#000000
#FFFFFF
Pass
a Blog21.00:14.5: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