Skip to content
https://credly.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Heading Hierarchy
Action
25 headings, 3 skip(s)
FIX
25 headings, 3 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.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 (empty)
  • H3 The Future of White Paper Work
  • H1 Unlock the Power of Your People
  • H3 For Learning & Training Providers skipped
  • H3 Workforce Planning
  • H2 The Power of the Network
  • H2 Digital Credentials & Verified Skills Transform the Talent Marketplace
  • H2 The Numbers Don’t Lie
  • H4 Industry-Leading Technology skipped
  • H4 Unmatched Customer Support
  • H4 Enterprise Class Security
  • H5 Kevin Streater, Vice President
  • H2 Featured Resources
  • H4 PVH: Creating a Culture of Learning skipped
  • H4 Empowering the Tech Workforce of the Future: A Guide for Identifying, Mapping, and Bridging the Skills Gap
  • H4 Johnson Controls: Building Brand Confidence
  • H2 Ready to get started?
  • H2 Privacy and cookies
  • H2 Pearson Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H3 Vendors List

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

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

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

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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
No navigation patterns
FIX
No navigation patterns
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
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.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "Navigation Menu" MAIN CONTENTINFO footer

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Alt Text Quality
Action
9 of 33 images have issues
REVIEW
9 of 33 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
33 images 23 good alt text 1 decorative 9 missing
IssueCount
missing9 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 - Credly ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA 8 pass AA only
h1 Unlock the Power of Your People
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
32px · bottom of viewport
h2 The Power of the Network
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Digital Credentials & Verified Skills Tr…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Numbers Don’t Lie
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Resources
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy and cookies
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pearson Privacy Preference Center
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h3 The Future of White Paper Work
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 For Learning & Training Providers
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Workforce Planning
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Manage Consent Preferences
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Vendors List
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Unlock the Power of …1.66:13.0:1
#000000
#333333
Fail
h2 The Power of the Net…1.66:13.0:1
#000000
#333333
Fail
h2 Digital Credentials …1.66:13.0:1
#000000
#333333
Fail
h2 The Numbers Don’t …1.66:13.0:1
#000000
#333333
Fail
h2 Featured Resources1.66:13.0:1
#000000
#333333
Fail
h2 Privacy and cookies1.66:13.0:1
#000000
#333333
Fail
h2 Pearson Privacy Pref…1.66:13.0:1
#000000
#333333
Fail
h3 The Future of White…1.66:13.0:1
#000000
#333333
Fail
h3 For Learning & Train…1.66:13.0:1
#000000
#333333
Fail
h3 Workforce Planning1.66:13.0:1
#000000
#333333
Fail
h3 Manage Consent Prefe…1.66:13.0:1
#000000
#333333
Fail
h3 Vendors List1.66:13.0:1
#000000
#333333
Fail
title Credly by Pearson5.24:14.5:1
#000000
#7F7F7F
Pass
span Current Inquiry Type5.24:14.5:1
#000000
#7F7F7F
Pass
span First Name5.24:14.5:1
#000000
#7F7F7F
Pass
span Last Name5.24:14.5:1
#000000
#7F7F7F
Pass
span Work Email5.24:14.5:1
#000000
#7F7F7F
Pass
span Phone Number5.24:14.5:1
#000000
#7F7F7F
Pass
span Organization Name5.24:14.5:1
#000000
#7F7F7F
Pass
span Profession5.24:14.5:1
#000000
#7F7F7F
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 — 4 failing, 27 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.

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
div.header__container > div.header__top-content > div.header__search-container > button.input-btn div.header__container > div.header__top-content > div.header__search-container > button.input-btn
header.header > div.header__container > div.header__top-content > button#menu-btn header.header > div.header__container > div.header__top-content > button#menu-btn

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#hs_cos_wrapper_widget_1673012467954 > section.quote > div.quote_bg-top-left > img.d-md-none div#hs_cos_wrapper_widget_1673012467954 > section.quote > div.quote_bg-top-left > img.d-md-none
div#hs_cos_wrapper_widget_1673012467954 > section.quote > div.quote_bg-bottom-right > img.d-md-none div#hs_cos_wrapper_widget_1673012467954 > section.quote > div.quote_bg-bottom-right > img.d-md-none
div#hs_cos_wrapper_widget_1673012759862 > div.position-relative > section.conversion-panel > img.conversion-panel__bg-left div#hs_cos_wrapper_widget_1673012759862 > div.position-relative > section.conversion-panel > img.conversion-panel__bg-left

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.col-12 > div.card-deck__card-wrapper > div.card-deck__content > a.mask-link div.col-12 > div.card-deck__card-wrapper > div.card-deck__content > a.mask-link
div.col-12 > div.card-deck__card-wrapper > div.card-deck__content > a.mask-link div.col-12 > div.card-deck__card-wrapper > div.card-deck__content > a.mask-link
div.col-12 > div.card-deck__card-wrapper > div.card-deck__content > a.mask-link div.col-12 > div.card-deck__card-wrapper > div.card-deck__content > a.mask-link

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.

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
For Learning & Training Providers div.container > div.row > div.col-12 > h3.display-xs
Industry-Leading Technology div.container > div.row > div.col-12 > h4.heading-sm
PVH: Creating a Culture of Learning div.col-12 > div.card-deck__card-wrapper > div.card-deck__content > h4.heading-sm

These are opportunities to improve keyboard navigation in your application.

○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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[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
●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.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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
Form Accessibility
1 of 20 controls have issues
PASS
1 of 20 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">
Info::
19 control(s) properly labeled
20 controls
19 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#firstname-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266textFirst Name*for/id
#lastname-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266textLast Name*for/id
#email-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266emailWork Email*for/id
#phone-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266telPhone Number*for/id
#company-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266textOrganization Name*for/id
#hs_persona-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266selectProfession*for/id
#how_can_we_help_you_0-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266radionone
#how_can_we_help_you_1-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266radionone
#how_can_we_help_you_2-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266radionone
#LEGAL_CONSENT.subscription_type_1230495-290f7323-7dbb-46af-a9e6-ef42e25b132b_7266checkboxnone
#module_16711315160582-inputsearchThis is a search field with an auto-suggest feature attached.aria-label
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextVendor list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
inputsubmit(none)none

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

<input type="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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback