Skip to content
https://docusaurus.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
2
REVIEW
5
PASS
6
INFO
0
Checks
13
6 PASS 5 REVIEW 2 FIX
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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
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 | Docusaurus ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
11 icon(s) detected
REVIEW
11 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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 rgb(37, 194, 160) ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

9 pass 11 fail WCAG AA
h2 Check it out in the intro video
1.60:1
#000000
on
#2B3137
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Loved by many engineers
1.60:1
#000000
on
#2B3137
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Powered by MDX
1.60:1
#000000
on
#2B3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Built Using React
1.60:1
#000000
on
#2B3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ready for Translations
1.60:1
#000000
on
#2B3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Document Versioning
1.60:1
#000000
on
#2B3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Content Search
1.60:1
#000000
on
#2B3137
needs 3.0:1 (large text)
19px · bottom of viewport
a Blog
1.60:1
#000000
on
#2B3137
needs 4.5:1 (normal text)
16px · above the fold
a Showcase
1.60:1
#000000
on
#2B3137
needs 4.5:1 (normal text)
16px · above the fold
a Community
1.60:1
#000000
on
#2B3137
needs 4.5:1 (normal text)
16px · above the fold
a 3.9.2
1.60:1
#000000
on
#2B3137
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Check it out in the …1.60:13.0:1
#000000
#2B3137
Fail
h2 Loved by many engine…1.60:13.0:1
#000000
#2B3137
Fail
h3 Powered by MDX1.60:13.0:1
#000000
#2B3137
Fail
h3 Built Using React1.60:13.0:1
#000000
#2B3137
Fail
h3 Ready for Translatio…1.60:13.0:1
#000000
#2B3137
Fail
h3 Document Versioning1.60:13.0:1
#000000
#2B3137
Fail
h3 Content Search1.60:13.0:1
#000000
#2B3137
Fail
title Build optimized webs…16.91:14.5:1
#000000
#F6E2E3
Pass
a Skip to main content18.71:14.5:1
#000000
#F6EFFF
Pass
div 🎉️21.00:14.5:1
#000000
#FFFFFF
Pass
a Docusaurus v3.920.65:14.5:1
#000000
#FDFDFD
Pass
b is out!21.00:13.0:1
#000000
#FFFFFF
Pass
div 🥳️21.00:14.5:1
#000000
#FFFFFF
Pass
b Docusaurus21.00:13.0:1
#000000
#FFFFFF
Pass
a Docs21.00:14.5:1
#000000
#FFFFFF
Pass
a API9.31:14.5:1
#000000
#AAADAF
Pass
a Blog1.60:14.5:1
#000000
#2B3137
Fail
a Showcase1.60:14.5:1
#000000
#2B3137
Fail
a Community1.60:14.5:1
#000000
#2B3137
Fail
a 3.9.21.60:14.5:1
#000000
#2B3137
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+
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main" MAIN CONTENTINFO footer
A
Heading Hierarchy
8 headings, 1 skip(s)
PASS
8 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Build optimized websites quickly, focus on your content
  • H3 Powered by MDX skipped
  • H3 Built Using React
  • H3 Ready for Translations
  • H3 Document Versioning
  • H3 Content Search
  • H2 Check it out in the intro video
  • H2 Loved by many engineers

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 20 images OK
PASS
All 20 images OK
Info::
2 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
20 images 18 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Docusaurus
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Docusaurus ✓192×192 icon ✓512×512 icon ✓Start URL ./index.html ✓Display Mode standalone ✓
Name Docusaurus Display Mode standalone Theme Color #2196f3 Background Color #424242 Icons 8 icon(s)
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 22 passed
PASS
98

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
Powered by MDX div.container > div.row > div.col > h3.featureHeading_TLGJ

These are opportunities to improve keyboard navigation in your application.

○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
●`[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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○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