Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-tden91

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://fitchratings.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://fitchratings.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Heading Hierarchy

Action

13 headings, 1 skip(s)

REVIEW

13 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 01Insights
H3 Global Economic Outlook
H2 Japan’s Major Insurers Well-Prepared for New Regulatory Regime
H3 Join our Talent Community
H2 02Videos
H2 03Podcasts
H3 Financial Training Courses
H2 04Events
H4 About skipped
H4 Regulatory
H4 Product
H4 Region
H4 Fitch Group

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

Link & Button Quality

2 issue(s) across 38 links and 2 buttons

REVIEW

2 issue(s) across 38 links and 2 buttons

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /global-economic-outlook-excerpt ("Learn More"); /videos/japans-major-insurers-well-prepared-for-new-regulatory-regime-09-04-2026 ("Learn More")

9 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.fitchlearning.com/course-listing?utm_source=FitchRatings&utm_medi…; https://fitchgroup.alertline.com/gcs/welcome; https://secure.ethicspoint.com/domain/media/en/gui/79361/index.html; https://www.fitch.group/; https://www.fitchratings.com/; https://www.fitchsolutions.com/?utm_campaign=fr-footer-fs&utm_medium=Referral…; https://www.fitchbohua.cn/; https://www.fitchlearning.com/; https://www.hearst.com/

27 link(s) with descriptive text

38 links

0 empty

2 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/global-economic-outlook-excerpt	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Global Economic Outlook Excerpt
/videos/japans-major-insurers-well-prepa…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Japans Major Insurers Well Prepared For New Regulatory Regime 09 04 2026
https://www.fitchlearning.com/course-lis…	View upcoming courses	new tab	Add '(opens in new tab)' to text
https://fitchgroup.alertline.com/gcs/wel…	Feedback	new tab	Add '(opens in new tab)' to text
https://secure.ethicspoint.com/domain/me…	Report an Issue / Whistleblowi…	new tab	Add '(opens in new tab)' to text
https://www.fitch.group/	Fitch Group	new tab	Add '(opens in new tab)' to text
https://www.fitchratings.com/	Fitch Ratings	new tab	Add '(opens in new tab)' to text
https://www.fitchsolutions.com/?utm_camp…	Fitch Solutions	new tab	Add '(opens in new tab)' to text
https://www.fitchbohua.cn/	Fitch Bohua	new tab	Add '(opens in new tab)' to text
https://www.fitchlearning.com/	Fitch Learning	new tab	Add '(opens in new tab)' to text
https://www.hearst.com/	Owned by Hearst	new tab	Add '(opens in new tab)' to text

29 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/global-economic-outlook-excerpt ("Learn More"); /videos/japans-major-insurers-well-prepared-for-new-regulatory-regime-09-04-2026 ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://www.fitchlearning.com/course-listing?utm_source=FitchRatings&utm_medi…; https://fitchgroup.alertline.com/gcs/welcome; https://secure.ethicspoint.com/domain/media/en/gui/79361/index.html; https://www.fitch.group/; https://www.fitchratings.com/; https://www.fitchsolutions.com/?utm_campaign=fr-footer-fs&utm_medium=Referral…; https://www.fitchbohua.cn/; https://www.fitchlearning.com/; https://www.hearst.com/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

Action

9 icon(s) detected

REVIEW

9 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Insights

2.06:1

#000000

#424235

needs 3.0:1 (large text)

24px · mid-page

h2 Japan’s Major Insurers Well-Prepared f…

2.74:1

#000000

#5C5240

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Videos

2.74:1

#000000

#5C5240

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Podcasts

2.74:1

#000000

#5C5240

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Events

2.74:1

#000000

#5C5240

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Global Economic Outlook

1.84:1

#000000

#3C3A2F

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

h3 Join our Talent Community

2.74:1

#000000

#5C5240

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Financial Training Courses

2.74:1

#000000

#5C5240

needs 3.0:1 (large text)

19px · bottom of viewport

title Fitch Ratings: Credit Ratings & Analysis…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

3.33:1

#000000

#56635C

needs 4.5:1 (normal text)

16px · top of page (header area)

span Ratings

3.44:1

#000000

#59655B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Sectors

3.62:1

#000000

#5F685D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Insights

3.72:1

#000000

#64695D

needs 4.5:1 (normal text)

16px · above the fold

a Events

3.87:1

#000000

#676C5B

needs 4.5:1 (normal text)

16px · above the fold

span Subscriptions

3.93:1

#000000

#6C6C5A

needs 4.5:1 (normal text)

16px · above the fold

span About Us

4.01:1

#000000

#6F6D59

needs 4.5:1 (normal text)

16px · above the fold

span English

3.98:1

#000000

#716C57

needs 4.5:1 (normal text)

16px · above the fold

span 中文简体

3.82:1

#000000

#716856

needs 4.5:1 (normal text)

16px · above the fold

span 中文繁體

3.62:1

#000000

#6B6555

needs 4.5:1 (normal text)

16px · above the fold

span 日本語

1.95:1

#000000

#403E33

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Insights	2.06:1	3.0:1	#000000	#424235	Fail
h2 Japan’s Major Insu…	2.74:1	3.0:1	#000000	#5C5240	Fail
h2 Videos	2.74:1	3.0:1	#000000	#5C5240	Fail
h2 Podcasts	2.74:1	3.0:1	#000000	#5C5240	Fail
h2 Events	2.74:1	3.0:1	#000000	#5C5240	Fail
h3 Global Economic Outl…	1.84:1	3.0:1	#000000	#3C3A2F	Fail
h3 Join our Talent Comm…	2.74:1	3.0:1	#000000	#5C5240	Fail
h3 Financial Training C…	2.74:1	3.0:1	#000000	#5C5240	Fail
title Fitch Ratings: Credi…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to main content	3.33:1	4.5:1	#000000	#56635C	Fail
span Ratings	3.44:1	4.5:1	#000000	#59655B	Fail
span Sectors	3.62:1	4.5:1	#000000	#5F685D	Fail
span Insights	3.72:1	4.5:1	#000000	#64695D	Fail
a Events	3.87:1	4.5:1	#000000	#676C5B	Fail
span Subscriptions	3.93:1	4.5:1	#000000	#6C6C5A	Fail
span About Us	4.01:1	4.5:1	#000000	#6F6D59	Fail
span English	3.98:1	4.5:1	#000000	#716C57	Fail
span 中文简体	3.82:1	4.5:1	#000000	#716856	Fail
span 中文繁體	3.62:1	4.5:1	#000000	#6B6555	Fail
span 日本語	1.95:1	4.5:1	#000000	#403E33	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.

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 29 passed

PASS

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav#back-to-top > div.frw-wrapper--1 > div.frw-region > div.frw-js-nav-toggle `nav#back-to-top > div.frw-wrapper--1 > div.frw-region > div.frw-js-nav-toggle`

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
FITCH RATINGS - EMPOWERING CAPITAL MARKETS IN LATIN AMERICA `div.frw-video > div > div.frw-bg--img > h4.frw-heading--6`
Fitch on Indonesia 2026 `div.frw-event__row--group > div.frw-event__row > div.frw-column > h3.frw-event__title`

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●`[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.

●Links have a discernible name

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

○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.

○Image elements have `[alt]` attributes

○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.

○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.

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