Skip to content
https://jestjs.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
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: #fff
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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
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::
1 <nav> landmark(s) found
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
Heading Hierarchy
14 headings
REVIEW
14 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Zero config
  • H2 Snapshots
  • H2 Isolated
  • H2 Great api
  • H2 Fast and safe
  • H2 Code coverage
  • H2 Easy Mocking
  • H2 Great Exceptions
  • H2 Philosophy
  • H2 Docs and talks
  • H2 Open Collective
  • H3 Gold Sponsors
  • H3 Featured Sponsors
  • H2 Who uses Jest?

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Alt Text Quality
Action
4 of 15 images have issues
REVIEW
4 of 15 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
11 image(s) with good alt text
15 images 11 good alt text 4 missing
IssueCount
missing4 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
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 · Jest ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Jest · 🃏 Delightful JavaScript Testi…
1.34:1
#000000
on
#20232A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.34:1
#000000
on
#20232A
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Philosophy18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Docs and talks18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Open Collective18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Who uses Jest?18.76:13.0:1
#000000
#F2F2F2
Pass
h3 Gold Sponsors18.76:13.0:1
#000000
#F2F2F2
Pass
h3 Featured Sponsors18.76:13.0:1
#000000
#F2F2F2
Pass
title Jest · 🃏 Delight…1.34:14.5:1
#000000
#20232A
Fail
a Skip to main content1.34:14.5:1
#000000
#20232A
Fail
div Support Ukraine 🇺…21.00:14.5:1
#000000
#FFFFFF
Pass
a Help Provide Humanit…21.00:14.5:1
#000000
#FFFFFF
Pass
b Jest21.00:13.0:1
#000000
#FFFFFF
Pass
a 30.021.00:14.5:1
#000000
#FFFFFF
Pass
a Next21.00:14.5:1
#000000
#FFFFFF
Pass
a 30.021.00:14.5:1
#000000
#FFFFFF
Pass
a 29.721.00:14.5:1
#000000
#FFFFFF
Pass
a 29.621.00:14.5:1
#000000
#FFFFFF
Pass
a 29.521.00:14.5:1
#000000
#FFFFFF
Pass
a 29.421.00:14.5:1
#000000
#FFFFFF
Pass
a 29.321.00:14.5:1
#000000
#FFFFFF
Pass
a 29.221.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.

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: Jest
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Jest ✓192×192 icon ✓512×512 icon ✓Start URL ./index.html ✓Display Mode standalone ✓
Name Jest Display Mode standalone Theme Color #15c213 Background Color #424242 Icons 3 icon(s)
A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 21 passed
PASS
91

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
JEST div.navbar__inner > div.theme-layout-navbar-left > a.navbar__brand > b.navbar__title
JEST div.jest-card-hitslop > div.jest-card > div.jest-card-front > div.jest-card-label
JEST div.jest-card-hitslop > div.jest-card > div.jest-card-front > div.jest-card-label
zero config h2 > div > span > p
snapshots h2 > div > span > p
isolated h2 > div > span > p
great api h2 > div > span > p
FAST AND SAFE h2 > div > span > p
CODE COVERAGE h2 > div > span > p
--coverage span > p > a > code
Mock Functions div > span > p > a
GREAT EXCEPTIONS h2 > div > span > p
toBeCloseTo div.blockElement > div.blockContent > p.buttons-wrapper > a.button
toEqual div.blockElement > div.blockContent > p.buttons-wrapper > a.button
toStrictEqual div.blockElement > div.blockContent > p.buttons-wrapper > a.button
toHaveProperty div.blockElement > div.blockContent > p.buttons-wrapper > a.button
toMatchSnapshot div.blockElement > div.blockContent > p.buttons-wrapper > a.button
toThrowError div.blockElement > div.blockContent > p.buttons-wrapper > a.button
PHILOSOPHY div.wrapperV1 > div.blockElement > div.blockContent > h2
Jest and Delightful JavaScript Testing div > span > p > a
Building High-Quality JavaScript Tools div > span > p > a
Jest as a Platform div > span > p > a
OPEN COLLECTIVE div.wrapperV1 > div.yellow > div.blockContent > h2
gold sponsors div.yellow > div.blockContent > div.opencollective > h3
featured sponsors div.yellow > div.blockContent > div.opencollective > h3
Join 600+ donors div.blockContent > div.opencollective > p > a
opencollective.com div.blockContent > div.opencollective > p > a
WHO USES JEST? div.wrapperV1 > div.yellow > div.blockContent > h2
100m+ million div > span > p > a
15,000,000 div > span > p > a
OpenJS Foundation div.footer__bottom > div.footer__copyright > p > a
OpenJS Foundation div.footer__bottom > div.footer__copyright > p > a
OpenJS Foundation div.footer__bottom > div.footer__copyright > p > a
Trademark Policy div.footer__bottom > div.footer__copyright > p > a
Trademark List div.footer__bottom > div.footer__copyright > p > a
list of OpenJS Foundation trademarks div.footer__bottom > div.footer__copyright > p > a
The OpenJS Foundation div.footer__bottom > div.footer__copyright > p > a
Terms of Use div.footer__bottom > div.footer__copyright > p > a
Privacy Policy div.footer__bottom > div.footer__copyright > p > a
Bylaws div.footer__bottom > div.footer__copyright > p > a
Code of Conduct div.footer__bottom > div.footer__copyright > p > a
Trademark Policy div.footer__bottom > div.footer__copyright > p > a
Trademark List div.footer__bottom > div.footer__copyright > p > a
Cookie Policy div.footer__bottom > div.footer__copyright > p > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OpenJS Foundation div.footer__bottom > div.footer__copyright > p > a
OpenJS Foundation div.footer__bottom > div.footer__copyright > p > a
OpenJS Foundation div.footer__bottom > div.footer__copyright > p > a
Trademark Policy div.footer__bottom > div.footer__copyright > p > a
Trademark List div.footer__bottom > div.footer__copyright > p > a
list of OpenJS Foundation trademarks div.footer__bottom > div.footer__copyright > p > a

These are opportunities to improve the legibility of your content.

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.plugin-pages html.plugin-pages

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
●`[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
●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.
●Heading elements appear in a sequentially-descending order
●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
○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