Skip to content
https://wpbeginner.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
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
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: #ff6200
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.
C
Form Accessibility
Action
4 of 10 controls have issues
REVIEW
4 of 10 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="text" name="wpforms[fields][3]" id="wpforms-241611-field_3">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="wpforms[fields][1]" id="wpforms-241611-field_1">; <input type="email" name="wpforms[fields][2]" id="wpforms-241611-field_2">; <input type="search" name="q">
Info::
6 control(s) properly labeled
10 controls
6 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
#wpforms-241613-field_3textName Layout Emailfor/id
#wpforms-241613-field_1textFull Name *for/id
#wpforms-241613-field_2emailEmail *for/id
#cookie-category-essentialcheckboxnone
#cookie-category-statisticscheckboxnone
#cookie-category-marketingcheckboxnone
#wpforms-241611-field_2email(Your Email Address)placeholder only
#wpforms-241611-field_1text(Full Name)placeholder only
qsearch(Enter your keywords and search WPBeginner…)placeholder only
#wpforms-241611-field_3text(none)none

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

<input type="text" name="wpforms[fields][3]" id="wpforms-241611-field_3">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="wpforms[fields][1]" id="wpforms-241611-field_1">; <input type="email" name="wpforms[fields][2]" id="wpforms-241611-field_2">; <input type="search" name="q">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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::
Search form 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
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
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 WPBeginner - Beginner's Guide for WordPr…
1.40:1
#000000
on
#2D2520
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to primary navigation
1.40:1
#000000
on
#2D2520
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Learn the Ins and Ou…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 How to Build a Produ…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Fewer Returns, More …19.09:13.0:1
#000000
#F4F4F4
Pass
h2 How to Accept Pre-Or…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 How I Built a WordPr…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 WP Payment Pal Revie…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 How to Set Min & Max…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Our content is desig…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Find a topic by its …19.09:13.0:1
#000000
#F4F4F4
Pass
title WPBeginner - Beginne…1.40:14.5:1
#000000
#2D2520
Fail
a Skip to primary navi…1.40:14.5:1
#000000
#2D2520
Fail
a Skip to main content7.00:14.5:1
#000000
#FF6200
Pass
a WPBeginner - WordPre…7.00:14.5:1
#000000
#FF6200
Pass
a Blog7.00:14.5:1
#000000
#FF6200
Pass
p Categories7.00:14.5:1
#000000
#FF6200
Pass
a Beginners Guide7.00:14.5:1
#000000
#FF6200
Pass
a News7.00:14.5:1
#000000
#FF6200
Pass
a Opinion7.32:14.5:1
#000000
#FE6B0C
Pass
a Showcase19.09:14.5:1
#000000
#F4F4F4
Pass
a Themes19.09:14.5:1
#000000
#F4F4F4
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 20 passed
REVIEW
84

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
Trusted WordPress tutorials, when you need them most. div.wpb-top-orange-bar__wrap > div > div.wpb-top-orange-bar__text > div.translate
25 Million+ div.wrap > div.wpb-top-orange-bar__wrap > a.wpb-top-orange-bar__fact > div.wpb-top-orange-bar__fact--value
Websites using our plugins div.wpb-top-orange-bar__wrap > a.wpb-top-orange-bar__fact > div.wpb-top-orange-bar__fact--label > span.translate
16+ div.wrap > div.wpb-top-orange-bar__wrap > a.wpb-top-orange-bar__fact > div.wpb-top-orange-bar__fact--value
Years of WordPress experience div.wpb-top-orange-bar__wrap > a.wpb-top-orange-bar__fact > div.wpb-top-orange-bar__fact--label > span.translate
WordPress tutorials
by experts div.wpb-top-orange-bar__wrap > a.wpb-top-orange-bar__fact > div.wpb-top-orange-bar__fact--label > span.translate
Get Our Free WordPress Training div#wpforms-241611 > form#wpforms-form-241611 > div.wpforms-submit-container > button#wpforms-submit-241611
Download Now div.wpb-block-section > div.wpb-block-recent-posts__sidebar > a.wpb-block-recent-posts__alternative-cta > div.wpb-block-recent-posts__alternative-cta__button
Take the Quiz div.wpb-block-glossary > div > div.wpb-block-glossary__cta > a.wpb-block-glossary__cta-button
View All header.wpb-generic-header > div > a.wpb-generic-header__link > span.translate
Read about our process div.wpb-block-section > div.wpb-block-promise-cta__content > div.wpb-block-promise-cta__action > a.wpb-block-promise-cta__action-link
View All header.wpb-generic-header > div > a.wpb-generic-header__link > span.translate
View All header.wpb-generic-header > div > a.wpb-generic-header__link > span.translate
Subscribe Now! div#wpforms-241613 > form#wpforms-form-241613 > div.wpforms-submit-container > button#wpforms-submit-241613
View All header.wpb-generic-header > div > a.wpb-generic-header__link > span.translate
View All header.wpb-generic-header > div > a.wpb-generic-header__link > span.translate
View this Deal div > div.wpb-generic-item__link > a > span.translate
View this Deal div > div.wpb-generic-item__link > a > span.translate
View this Deal div > div.wpb-generic-item__link > a > span.translate

These are opportunities to improve the legibility of your content.

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
Site Links div.wpb-site-footer-content > div.wpb-site-footer__row > div.wpb-site-footer__column > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#wpforms-form-241611 > div.wpforms-field-container > div#wpforms-241611-field_3-container > input#wpforms-241611-field_3 form#wpforms-form-241611 > div.wpforms-field-container > div#wpforms-241611-field_3-container > input#wpforms-241611-field_3

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.wpb-block-section > div.wpb-block-recent-posts__list > div.wpb-block-recent-posts__large > a div.wpb-block-section > div.wpb-block-recent-posts__list > div.wpb-block-recent-posts__large > a
div.wpb-block-section > div.wpb-block-recent-posts__sidebar > div.wpb-block-recent-posts__cta > a div.wpb-block-section > div.wpb-block-recent-posts__sidebar > div.wpb-block-recent-posts__cta > a

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.

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
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
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.
Image elements do not have `[alt]` attributes that are redundant text.
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
`<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.
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
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.
A+
Landmark Structure
16 landmarks
PASS
16 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 CONTENTINFO footer
A
Heading Hierarchy
17 headings, 1 skip(s)
PASS
17 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Learn the Ins and Outs of WordPress from the Real WordPress Experts
  • H2 How to Build a WooCommerce Sales Funnel That Actually Converts
  • H2 How to Build a Product Quiz in WordPress That Recommends & Converts
  • H2 Fewer Returns, More Sales: How to Add Size Charts in WooCommerce
  • H2 How to Accept Pre-Orders in WooCommerce (Most Stores Miss This)
  • H2 How I Built a WordPress Personality Quiz to Turn Visitors into Subscribers
  • H2 WP Payment Pal Review: The Right PayPal Plugin For You?
  • H2 How to Set Min & Max WooCommerce Order Limits (& Stop Overselling)
  • H3 Find a topic by its first letter
  • H2 Our content is designed to help you make your WordPress site better.
  • H4 Site Links skipped
  • H4 Free Tools
  • H4 Resources
  • H4 Our Brands
  • H4 About WPBeginner®
  • H2 Cookie Consent
  • H2 Cookie Preferences

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 59 images OK
PASS
All 59 images OK
Info::
14 decorative image(s) correctly marked
Info::
45 image(s) with good alt text
59 images 45 good alt text 14 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback