Skip to content
https://mindtools.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
8
PASS
1
INFO
0
Checks
13
1 PASS 8 REVIEW 4 FIX
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::
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
3 landmarks
REVIEW
3 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 (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
18 headings
REVIEW
18 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Refresh your skills
  • H3 Which Tier are you?
  • H3 7 day free trial
  • H2 Better managers, stronger teams, lasting success.
  • H2 Better managers, stronger teams, lasting success.
  • H2 Personal growth with purpose.
  • H3 Join thousands of employees in hundreds of companies flourishing at work.
  • H2 Meaningful change starts here.
  • H2 Introducing the M: Suite
  • H2 Develop your skills. Grow your career.
  • H2 Engaging non-desktop workers in learning
  • H2 Proven impact, straight from our clients
  • H2 Latest Research Report
  • H2 Sign up to our newsletter
  • H3 Useful Links
  • H3 Solutions
  • H3 Products & Services
  • H4 Sign up today and enjoy 7 days free!

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
23 of 33 images have issues
REVIEW
23 of 33 images have issues
Critical::
23 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
5 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
33 images 5 good alt text 5 decorative 23 missing
IssueCount
missing23 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
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="s">; <input type="email" name="email">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
stext(Search our Content Hub)placeholder only
stext(Search our Content Hub)placeholder only
emailemail(Your email)placeholder only

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

<input type="text" name="s">; <input type="text" name="s">; <input type="email" name="email">

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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page not found - Mindtools Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Better managers, str…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Better managers, str…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Personal growth with5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Meaningful change st…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Introducing the5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Develop your skills.5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Grow your career.5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Engaging non-desktop…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Proven impact, strai…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Latest Research Repo…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Sign up to our newsl…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Refresh your skills5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Which Tier are you?5.24:13.0:1
#000000
#7F7F7F
Pass
h3 7 day free trial5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Join thousands of em…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Useful Links5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Solutions5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Products & Services5.24:13.0:1
#000000
#7F7F7F
Pass
title Leadership & Managem…4.83:14.5:1
#000000
#7F7967
Pass
span Start 7-Day Free Tri…5.09:14.5:1
#000000
#7F7D75
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 88/100 — 3 failing, 26 passed
REVIEW
88

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.bb-unstyled > li.menu-item > a > button.js-expander ul.bb-unstyled > li.menu-item > a > button.js-expander
ul.bb-unstyled > li.menu-item > a > button.js-expander ul.bb-unstyled > li.menu-item > a > button.js-expander
ul.bb-unstyled > li.menu-item > a.js-expander-proxy > button.js-expander ul.bb-unstyled > li.menu-item > a.js-expander-proxy > button.js-expander
ul.bb-unstyled > li.menu-item > a.js-expander-proxy > button.js-expander ul.bb-unstyled > li.menu-item > a.js-expander-proxy > button.js-expander

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.bb-header > div.bb-header__right > div > a.bb-search-header-toggle div.bb-header > div.bb-header__right > div > a.bb-search-header-toggle
div.bb-header > div.bb-header__right > div > a.bb-profile div.bb-header > div.bb-header__right > div > a.bb-profile
header.header > div.bb-header > div.bb-header__right__mobile > a.bb-search-header-toggle header.header > div.bb-header > div.bb-header__right__mobile > a.bb-search-header-toggle
header.header > div.bb-header > div.bb-header__right__mobile > a.bb-profile header.header > div.bb-header > div.bb-header__right__mobile > a.bb-profile

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
Go to slide 1 div.bb-service-promo-slider > div.bb-service-promo-slider--sliders > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.bb-service-promo-slider > div.bb-service-promo-slider--sliders > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.bb-service-promo-slider > div.bb-service-promo-slider--sliders > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div#bb-testimonial-carousel-1418656921 > div.bb-testimonial-carousel__swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div#bb-testimonial-carousel-1418656921 > div.bb-testimonial-carousel__swiper > div.swiper-pagination > span.swiper-pagination-bullet
FAQs div.menu-footer-useful-links-container > ul#menu-footer-useful-links > li#menu-item-43627 > a
Talk to the Team div.menu-footer-useful-links-container > ul#menu-footer-useful-links > li#menu-item-42021 > a
Subscribe to Mindtools div.menu-footer-useful-links-container > ul#menu-footer-useful-links > li#menu-item-42049 > a
Contact Us div.menu-footer-useful-links-container > ul#menu-footer-useful-links > li#menu-item-43628 > a
Join the Team div.menu-footer-useful-links-container > ul#menu-footer-useful-links > li#menu-item-43771 > a
Organizations div.menu-footer-solutions-container > ul#menu-footer-solutions > li#menu-item-61701 > a
Individuals div.menu-footer-solutions-container > ul#menu-footer-solutions > li#menu-item-43634 > a
For Partners div.menu-footer-solutions-container > ul#menu-footer-solutions > li#menu-item-43632 > a
For Public Sector div.menu-footer-solutions-container > ul#menu-footer-solutions > li#menu-item-43633 > a
Ask M: Coach div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60847 > a
AI Skills Practice div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60858 > a
Content Hub div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60853 > a
The Content Hub div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60851 > a
Custom Learning div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60862 > a
Insights and Analyst Services div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60861 > a
Ask M Coach div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60854 > a
Manager Skills Assessment div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60857 > a
Manager Skill Builder div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60859 > a
Off the Shelf div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60856 > a
Onboarding & Support div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60860 > a
Playlists div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60848 > a
Quizzes div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60849 > a
Skill Bites div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60850 > a
Workshops div.menu-footer-products-services-container > ul#menu-footer-products-services > li#menu-item-60855 > a
Mindtools Policies div.bb-footer__sole-menu > ul.bb-unstyled > li.menu-item > a
Terms of Website Sale div.bb-footer__sole-menu > ul.bb-unstyled > li.menu-item > a
Privacy Policy div.bb-footer__sole-menu > ul.bb-unstyled > li.menu-item > a
Cookie Policy div.bb-footer__sole-menu > ul.bb-unstyled > li.menu-item > a

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
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
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 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
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
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.
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Mindtools
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Mindtools 192×192 icon 512×512 icon Start URL . Display Mode standalone
Name Mindtools Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 3 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback