Skip to content
https://jetpack.wordpress.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-1rs4gi
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://jetpack.wordpress.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://jetpack.wordpress.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
C
Landmark Structure
Action
10 landmarks
REVIEW
10 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV 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

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

B
Heading Hierarchy
19 headings
REVIEW
19 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Let’s elevate your site
  • H2 Grow your site, without the grind
  • H2 Speed and SEOwith one click
  • H2 Secure your sitewithout hassle
  • H2 Testimonials
  • H2 See why 27M WordPress sites trust Jetpack
  • H2 Recommended by thebiggest names in WordPress
  • H3 VaultPress Backup
  • H3 Security
  • H3 Complete
  • H2 Let’s get you more visitors,faster pages and strongersecurity with Jetpack
  • H2 Put your site in your pocket
  • H2 (empty)
  • H2 (empty)
  • H3 (empty)
  • H2 Language
  • H1 Search results duplicate H1
  • H2 No results found
  • H2 Filter options

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 80/100 — 7 failing, 18 passed
REVIEW
80

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
per month for the first year, billed yearly div.jetpack-product-card__heading-wrapper > div.jetpack-product-card__price > div.plan-price__values > span.jetpack-product-card__billing-time-frame
per month for the first year, billed yearly div.jetpack-product-card__heading-wrapper > div.jetpack-product-card__price > div.plan-price__values > span.jetpack-product-card__billing-time-frame
per month for the first year, billed yearly div.jetpack-product-card__heading-wrapper > div.jetpack-product-card__price > div.plan-price__values > span.jetpack-product-card__billing-time-frame

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
storage limit div.jetpack-product-card > div.jetpack-product-card__body > p.jetpack-product-card__disclaimer > a

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wp-block-group > div.wp-block-group > figure.wp-block-image > a div.wp-block-group > div.wp-block-group > figure.wp-block-image > a
div.wp-block-group > div.wp-block-group > figure.wp-block-image > a div.wp-block-group > div.wp-block-group > figure.wp-block-image > a

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to main content header.mast > header#jetpack-header > nav.header__content > a.header__skip

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jetpack X account (formerly known as Twitter) li.sitemap__category > ul.sitemap__link-list > li > a.sitemap__link
Jetpack Facebook page li.sitemap__category > ul.sitemap__link-list > li > a.sitemap__link
Jetpack LinkedIn page li.sitemap__category > ul.sitemap__link-list > li > a.sitemap__link
Jetpack Youtube channel li.sitemap__category > ul.sitemap__link-list > li > a.sitemap__link

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.

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
Author / Investor / Podcaster figure > figcaption.testimonial-block__caption > span.testimonial-block__author-position > a
EN div.jetpack-footer__content > div.jetpack-footer__head > div.jetpack-footer__language > button.language-toggle
○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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[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
○`<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.
○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.
○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+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
15 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
22 images 7 good alt text 15 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 6 controls have issues
PASS
1 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit" id="jp-carousel-comment-form-button-submit">
Info::
5 control(s) properly labeled
6 controls
5 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#jp-carousel-comment-form-comment-fieldtextareaWrite a Comment...for/id
#jp-carousel-comment-form-email-fieldtextEmail (Required)for/id
#jp-carousel-comment-form-author-fieldtextName (Required)for/id
#jp-carousel-comment-form-url-fieldtextWebsitefor/id
#jetpack-instant-search__box-input-1searchMagnifying Glassnone
#jp-carousel-comment-form-button-submitsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="submit" id="jp-carousel-comment-form-button-submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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 Let’s elevate your…20.47:13.0:1
#000000
#FCFCFC
Pass
h1 Search results20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Grow your site, with…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Speed and SEO20.47:13.0:1
#000000
#FCFCFC
Pass
h2 with one click20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Secure your site20.47:13.0:1
#000000
#FCFCFC
Pass
h2 without hassle20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Testimonials20.47:13.0:1
#000000
#FCFCFC
Pass
h2 See why 27M WordPres…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Recommended by the20.47:13.0:1
#000000
#FCFCFC
Pass
h2 biggest names in Wo…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Let’s get you more…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 faster pages and str…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 security with Jetpa…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Put your site in you…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Language20.47:13.0:1
#000000
#FCFCFC
Pass
h2 No results found20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Filter options20.47:13.0:1
#000000
#FCFCFC
Pass
h3 VaultPress Backup20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Security20.47:13.0:1
#000000
#FCFCFC
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