Skip to content
https://econsultancy.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
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: #e4003b
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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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
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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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 Missing
✓ 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 11 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Real world training.…3.21:13.0:1
#000000
#BB0C33
Pass
h2 Delivering best prac…3.21:13.0:1
#000000
#BB0C33
Pass
h3 Sign in3.21:13.0:1
#000000
#BB0C33
Pass
h3 Team Engagement3.21:13.0:1
#000000
#BB0C33
Pass
h3 Practical Applicatio…3.21:13.0:1
#000000
#BB0C33
Pass
h3 Measurable Impact3.21:13.0:1
#000000
#BB0C33
Pass
h3 Flexible Customisati…3.21:13.0:1
#000000
#BB0C33
Pass
h3 Ecommerce3.21:13.0:1
#000000
#BB0C33
Pass
h3 Marketing3.21:13.0:1
#000000
#BB0C33
Pass
h3 Data & Analytics3.21:13.0:1
#000000
#BB0C33
Pass
h3 Customer Experience …3.21:13.0:1
#000000
#BB0C33
Pass
title Econsultancy - learn…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
p Econsultancy21.00:14.5:1
#000000
#FFFFFF
Pass
span Learning Solutions18.07:14.5:1
#000000
#EBEEF4
Pass
span Upskilling21.00:14.5:1
#000000
#FFFFFF
Pass
span Custom Training Solu…21.00:14.5:1
#000000
#FFFFFF
Pass
span Ready-To-Go Learning21.00:14.5:1
#000000
#FFFFFF
Pass
span Capability Framework…21.00:14.5:1
#000000
#FFFFFF
Pass
span Skills Gap discovery21.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.

B
Lighthouse Accessibility Audits
Score 86/100 — 5 failing, 23 passed
REVIEW
86

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
Book a Consultation div.hero-banner__wrap > div.hero-banner__content > div.hero-banner__links > a.hero-banner__button
Learn more div.features-widget > div.features-widget__wrap > div.features-widget__header > a.features-widget__button
Learn more div.features-widget__list > div.features-widget__feature > div.features-widget__feature-content > a.features-widget__feature-link
Learn more div.features-widget__list > div.features-widget__feature > div.features-widget__feature-content > a.features-widget__feature-link
Learn more div.features-widget__list > div.features-widget__feature > div.features-widget__feature-content > a.features-widget__feature-link
Learn more div.features-widget__list > div.features-widget__feature > div.features-widget__feature-content > a.features-widget__feature-link
Learn more div.image-and-text-widget__wrap > div.image-and-text-widget__text > div.image-and-text-widget__button-container > a.image-and-text-widget__button
Learn more div.image-and-text-widget__wrap > div.image-and-text-widget__text > div.image-and-text-widget__button-container > a.image-and-text-widget__button
Learn more div.image-and-text-widget__wrap > div.image-and-text-widget__text > div.image-and-text-widget__button-container > a.image-and-text-widget__button
Book a Consultation div.cta-widget > div.cta-widget__wrap > div.cta-widget__links > a.cta-widget__button
Discover the latest div.widget > div.widget-container > div.widget-header > a.widget-link
Book a Consultation div.cta-widget > div.cta-widget__wrap > div.cta-widget__links > a.cta-widget__button
Cookies div#onetrust-group-container > div#onetrust-policy > span.ot-b-addl-desc > a
Privacy Policy div#onetrust-group-container > div#onetrust-policy > span.ot-b-addl-desc > a
List of Partners (vendors) div.ot-dpd-container > div.ot-dpd-content > p.ot-dpd-desc > button.ot-link-btn
Consent to All Cookies div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-accept-btn-handler
Reject All div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-reject-all-handler
Manage Preferences div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler

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
Transforming learning outcomes for the world’s biggest organisations div.widget > div.logo-showcase > div.logo-showcase__wrap > h3.logo-showcase__title

These are opportunities to improve keyboard navigation in your application.

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.master-header__user-menu > ul.nav__user > li.nav__toggle > a.toggle div.master-header__user-menu > ul.nav__user > li.nav__toggle > a.toggle

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
About Us nav.footer-nav > ul#menu-footer-menu > li#menu-item-539006 > a
Privacy nav.footer-nav > ul#menu-footer-menu > li#menu-item-559618 > a

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.js html.js

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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○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.
○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
Heading Hierarchy
25 headings, 1 skip(s)
PASS
25 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.
  • H3 Sign in
  • H4 Need help signing in?
  • H1 Engage your team Elevate their capabilities Accelerate growth
  • H3 Transforming learning outcomes for the world’s biggest organisations skipped
  • H2 Leading global businesses choose Econsultancy
  • H2 Real world training. Real business change.
  • H3 Team Engagement
  • H3 Practical Application
  • H3 Measurable Impact
  • H3 Flexible Customisation
  • H2 Learn your way with Custom Training Solutions
  • H2 Move fast with Ready-To-Go Learning
  • H2 Benchmark current capabilities with Skills Gap Discovery
  • H3 Highly awarded, highly recognised training programs
  • H2 Delivering best practice expertise since 1999
  • H3 Ecommerce
  • H3 Marketing
  • H3 Data & Analytics
  • H3 Customer Experience (CX)
  • H2 Ready to start accelerating growth?
  • H3 Discover the latest trends & insights
  • H2 AI can be “springboard for productivity”, but not if brand-building fundamentals are broken
  • H2 Eight digital and marketing trends for 2025
  • H2 AI skills in demand as marketers wrestle with uncertainty into 2025
  • H2 Tailor your training with a learning consultation

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 37 images OK
PASS
All 37 images OK
Info::
33 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
37 images 4 good alt text 33 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+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://econsultancy.com/content/themes/econsultancy.com/css/print.min.css
Print Stylesheet ✓ Print Optimized
Print stylesheet https://econsultancy.com/content/themes/econsultancy.com/css/print.min.css ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback