Skip to content
https://moodys.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
F
Heading Hierarchy
Action
57 headings, 6 skip(s)
FIX
57 headings, 6 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 Private credit volatility is intensifying the push for greater transparency as risks rise
  • H6 Moody’s advances decision-grade credit intelligence powered by Microsoft 365 Copilot
  • H6 Moody’s Agentic Solutions now available in AWS Marketplace
  • H6 Falling defaults, rising fragility
  • H6 Moody’s brings credit and compliance workflows directly into Anthropic’s Claude
  • H5 Featured insights
  • H3 US corporate cash pile rises to $2.4 trillion on strong cash flow, borrowing for AI plans
  • H3 Fund Finance: Proposed Methodology
  • H3 Data centers' thirst heightens water management risks for US local governments
  • H3 Global corporate defaults rebounded in March
  • H4 Explore the latest thought leadership from Moody's Ratings
  • H3 US-Iran ceasefire is temporary, but conflict’s credit risks linger
  • H6 Credit risk skipped
  • H6 Compliance
  • H6 Private credit
  • H6 Data
  • H6 Sustainable finance
  • H2 Discover more
  • H6 Moody's RMS™ Global Event Response skipped
  • H5 Lower US bank capital requirements would be credit negative
  • H5 Declining savings capacity and rising funding needs will drive up long-term interest rates
  • H5 Middle East cease fire eases global energy and broader economic risks
  • H5 Latin American sovereigns increase funding options by growing local currency debt markets
  • H2 Maxsight™ for unified risk management
  • H5 Moody’s Maxsight™ unified risk platform brings together thousands of data points to deliver a holistic picture of risk that can be viewed through different lenses. skipped
  • H2 Credit Frontiers 2026 - London
  • H5 Wednesday, 29 April 2026 skipped
  • H5 As private credit evolves, complexity rises. New structures signal a maturing market. This edition explores how risks and returns ripple through Europe’s banks, insurers, and real economy, spotlight
  • H5 India energy shock raises credit risks as fuel costs surge
  • H5 Outlook for global energy sector turns positive as Middle East conflict boosts oil prices
  • H5 Credit quality is eroding among middle-market US companies funded with private credit
  • H5 Risk Reframed celebrates 100 episodes
  • H2 GlobalCapital Bond Awards 2026
  • H2 Credit Frontiers 2026 - New York
  • H5 Thursday, April 23, 2026 skipped
  • H5 Private credit markets face persistent volatility and systemic fragility, forcing investors and lenders to rethink strategies.
  • H3 Moody's makes it possible
  • H3 Innovating with purpose
  • H3 Work with brilliant minds
  • H2 GET IN TOUCH
  • H3 Speak to our team
  • H2 Connect with our solutions specialists
  • H2 Thank you
  • H6 Who We Serve skipped
  • H6 Solutions
  • H6 Capabilities
  • H6 Contact Us
  • H6 Moody's Integrity Hotline
  • H6 Company Information
  • H6 Regulatory
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

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

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

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-vbr106
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
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://moodys.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://moodys.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
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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
4 landmarks
REVIEW
4 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::
No banner (header) landmark
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 (missing!) 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

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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
title Moody's - credit ratings, research, and …
1.09:1
#000000
on
#050932
needs 4.5:1 (normal text)
16px · top of page (header area)
a Who We Serve
1.09:1
#000000
on
#050932
needs 4.5:1 (normal text)
16px · top of page (header area)
a Solutions
1.07:1
#000000
on
#090B19
needs 4.5:1 (normal text)
16px · top of page (header area)
a Capabilities
1.10:1
#000000
on
#0B0E20
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Discover more21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Maxsight™ for unif…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Credit Frontiers 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GlobalCapital Bond A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Credit Frontiers 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GET IN TOUCH21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect with our sol…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Thank you21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 US-Iran ceasefire is…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Moody's makes it pos…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Innovating with purp…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Work with brilliant …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Speak to our team21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage Consent Prefe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title Moody's - credit rat…1.09:14.5:1
#000000
#050932
Fail
a Who We Serve1.09:14.5:1
#000000
#050932
Fail
a Solutions1.07:14.5:1
#000000
#090B19
Fail
a Capabilities1.10:14.5:1
#000000
#0B0E20
Fail

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 80/100 — 7 failing, 24 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 4 5 div#carousel-hero-519106de79 > div.cmp-carousel__content > div.carousel-hero-slider > ol.cmp-carousel__indicators

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item > button#carousel-hero-519106de79-item-7dd4d5c1c2-tab
2 div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item > button#carousel-hero-519106de79-item-fc76f2cb55-tab
3 div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item > button#carousel-hero-519106de79-item-0951d348ab-tab
4 div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item > button#carousel-hero-519106de79-item-3537654599-tab
5 div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item > button#carousel-hero-519106de79-item-b45603dd4a-tab

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Start search div.css-sj91m9 > div.css-to3ihi > div.MuiBox-root > div.css-8atqhb

These are opportunities to improve the usage of ARIA in your application which 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
Credit risk div.card-content > div.copy-container > div.copy > h6
Moody's RMS™ Global Event Response div#card-simple-d86d180578 > div.card-content > div.title-container > h6
Moody’s Maxsight™ unified risk platform brings together thousands of data point… div#card-simple-8e6b9b6300 > div.card-content > div.cmp-teaser__description > h5
Thursday, April 23, 2026 div#card-simple-ebf197c105 > div.card-content > div.cmp-teaser__description > h5
Wednesday, 29 April 2026 div#card-simple-9e70bbf0e8 > div.card-content > div.cmp-teaser__description > h5
Who We Serve div.cmp-column-control-item > div.title > div#title-91e18a3804 > h6.cmp-title__text

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.cmp-carousel__content > div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item
2 div.cmp-carousel__content > div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item
3 div.cmp-carousel__content > div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item
4 div.cmp-carousel__content > div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item
5 div.cmp-carousel__content > div.carousel-hero-slider > ol.cmp-carousel__indicators > li.cmp-carousel__indicator-item

These are opportunities to improve the experience of reading tabular or list data using 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
linkedin div.footer-bottom > div.footer-right > div > a
instagram div.footer-bottom > div.footer-right > div > a

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
Cookie Notice div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●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 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.
○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+
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
8 decorative image(s) correctly marked
Info::
26 image(s) with good alt text
34 images 26 good alt text 8 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie 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
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback