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 4 REVIEW 6 FIX

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No contentinfo (footer) landmark

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

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

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-88o8tb

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.

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

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.

Heading Hierarchy

9 headings

REVIEW

9 headings

No H1 heading found

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

H3 Nordstrom: A Market in Motion: Looking Back on Three Decades in Foreign Exchange
H3 Statement Regarding Use of FedTrade Plus for Securities Lending Operations
H3 Business Leaders Survey: Service Sector Activity Declines
H3 The Federal Reserve’s Transition to Ample Reserves: A View from the SOMA Annual Report
H3 Key Takeaways from President Williams’s Speech on the Economic Outlook and Monetary Policy
H3 Economic Activity in the Second District Continued to Decline Modestly
H3 Empire State Manufacturing Survey: Business Activity Increases Moderately
H3 How Changes to GSE Ownership Structure Could Affect the Agency MBS Market
H3 Scams Involving the Federal Reserve Name

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

Link & Button Quality

Action

4 issue(s) across 213 links and 1 buttons

REVIEW

4 issue(s) across 213 links and 1 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a (#35 on page); /; /newsevents/speeches/2026/wil260416; /markets/annual_reports

7 link(s) open in new tab without warning

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

Got: http://libertystreeteconomics.newyorkfed.org; https://x.com/NewYorkFed; https://www.youtube.com/user/TheNewYorkFed; https://www.linkedin.com/company/federal-reserve-bank-of-new-york; https://public.govdelivery.com/accounts/USFRBNEWYORK/subscriber/new?; https://www.instagram.com/NewYorkFed; https://www.facebook.com/newyorkfed

202 link(s) with descriptive text

213 links

4 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
http://libertystreeteconomics.newyorkfed…	Blog	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
/newsevents/speeches/2026/wil260416	(empty)	empty	Add link text or aria-label
/markets/annual_reports	(empty)	empty	Add link text or aria-label
https://x.com/NewYorkFed	X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/TheNewYorkF…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/federal…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://public.govdelivery.com/accounts/…	Email	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/NewYorkFed	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/newyorkfed	Facebook	new tab	Add '(opens in new tab)' to text

203 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a (#35 on page); /; /newsevents/speeches/2026/wil260416; /markets/annual_reports

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

http://libertystreeteconomics.newyorkfed.org; https://x.com/NewYorkFed; https://www.youtube.com/user/TheNewYorkFed; https://www.linkedin.com/company/federal-reserve-bank-of-new-york; https://public.govdelivery.com/accounts/USFRBNEWYORK/subscriber/new?; https://www.instagram.com/NewYorkFed; https://www.facebook.com/newyorkfed

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

a Regional Economy

1.07:1

#000000

#0C0C0C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Data & Statistics

1.91:1

#000000

#3E3C3B

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Careers

1.14:1

#000000

#191210

needs 4.5:1 (normal text)

16px · above the fold

a Blog

1.42:1

#000000

#31251F

needs 4.5:1 (normal text)

16px · above the fold

a Press Center

2.11:1

#000000

#513F35

needs 4.5:1 (normal text)

16px · above the fold

a Menu

2.76:1

#000000

#635042

needs 4.5:1 (normal text)

16px · above the fold

a About the New York Fed

2.11:1

#000000

#4B4138

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a About the New York Fed

3.90:1

#000000

#6C6A68

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

3 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
title FEDERAL RESERVE BANK…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Museum & Visits	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Regional Economy	1.07:1	4.5:1	#000000	#0C0C0C	Fail
a Data & Statistics	1.91:1	4.5:1	#000000	#3E3C3B	Fail
a Careers	1.14:1	4.5:1	#000000	#191210	Fail
a Blog	1.42:1	4.5:1	#000000	#31251F	Fail
a Press Center	2.11:1	4.5:1	#000000	#513F35	Fail
a Menu	2.76:1	4.5:1	#000000	#635042	Fail
a About the New York…	2.11:1	4.5:1	#000000	#4B4138	Fail
a About the New York…	3.90:1	4.5:1	#000000	#6C6A68	Fail
a What We Do	18.81:1	4.5:1	#000000	#F5F2ED	Pass
a Who We Are	18.81:1	4.5:1	#000000	#F5F2ED	Pass
a Bank Leadership	20.13:1	4.5:1	#000000	#FBFAF8	Pass
a Communities We Serve	18.81:1	4.5:1	#000000	#F5F2ED	Pass
a Governance	18.81:1	4.5:1	#000000	#F5F2ED	Pass
a Board of Directors	18.81:1	4.5:1	#000000	#F5F2ED	Pass
a Disclosures	18.81:1	4.5:1	#000000	#F5F2ED	Pass
a Ethics and Conflicts…	18.81:1	4.5:1	#000000	#F5F2ED	Pass
a Annual Financial Sta…	18.81:1	4.5:1	#000000	#F5F2ED	Pass
a Org Chart	18.81:1	4.5:1	#000000	#F5F2ED	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.

Lighthouse Accessibility Audits

Action

Score 71/100 — 4 failing, 9 passed

REVIEW

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

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.dxt-logo-wrapper > div > div.dxt-logo-wrapper-a > a.dxt-logo `div.dxt-logo-wrapper > div > div.dxt-logo-wrapper-a > a.dxt-logo`
div.featured-headlines > ul.featured > li.featured-headline-active > a `div.featured-headlines > ul.featured > li.featured-headline-active > a`
div.featured-headlines > ul.featured > li > a `div.featured-headlines > ul.featured > li > a`
ul.spotlight > li#spotlight-slide-0 > div#spotlight-image-0 > a.spotlight-slide-link `ul.spotlight > li#spotlight-slide-0 > div#spotlight-image-0 > a.spotlight-slide-link`
ul.spotlight > li#spotlight-slide-1 > div#spotlight-image-1 > a.spotlight-slide-link `ul.spotlight > li#spotlight-slide-1 > div#spotlight-image-1 > a.spotlight-slide-link`
ul.spotlight > li#spotlight-slide-3 > div#spotlight-image-3 > a.spotlight-slide-link `ul.spotlight > li#spotlight-slide-3 > div#spotlight-image-3 > a.spotlight-slide-link`
ul.spotlight > li#spotlight-slide-4 > div#spotlight-image-4 > a.spotlight-slide-link `ul.spotlight > li#spotlight-slide-4 > div#spotlight-image-4 > a.spotlight-slide-link`
ul.spotlight > li#spotlight-slide-7 > div#spotlight-image-7 > a.spotlight-slide-link `ul.spotlight > li#spotlight-slide-7 > div#spotlight-image-7 > a.spotlight-slide-link`
ul.spotlight > li#spotlight-slide-8 > div#spotlight-image-8 > a.spotlight-slide-link `ul.spotlight > li#spotlight-slide-8 > div#spotlight-image-8 > a.spotlight-slide-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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
PRESS CENTER `li#spotlight-slide-0 > a.spotlight-slide-link > span.strap > a.dxt-spotlight-title`
REGIONAL ECONOMY `li#spotlight-slide-2 > a.spotlight-slide-link > span.strap > a.dxt-spotlight-title`
THE TELLER WINDOW `li#spotlight-slide-3 > a.spotlight-slide-link > span.strap > a.dxt-spotlight-title`
THE TELLER WINDOW `li#spotlight-slide-4 > a.spotlight-slide-link > span.strap > a.dxt-spotlight-title`
REGIONAL ECONOMY `li#spotlight-slide-5 > a.spotlight-slide-link > span.strap > a.dxt-spotlight-title`
REGIONAL ECONOMY `li#spotlight-slide-6 > a.spotlight-slide-link > span.strap > a.dxt-spotlight-title`
THE TELLER WINDOW `li#spotlight-slide-7 > a.spotlight-slide-link > span.strap > a.dxt-spotlight-title`
ABOUT THE NEW YORK FED `li#spotlight-slide-8 > a.spotlight-slide-link > span.strap > a.dxt-spotlight-title`

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 `html`

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-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` 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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[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

○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

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

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

○Buttons have an accessible name

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

○Identical links have the same purpose.

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

Alt Text Quality

All 27 images OK

PASS

All 27 images OK

8 decorative image(s) correctly marked

19 image(s) with good alt text

27 images 19 good alt text 8 decorative

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="text" name="text" id="searchbox">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#searchbutton	submit	Search Button	aria-label
#searchbox	text	(none)	none

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

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

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /medialibrary/media/v5/dxt-ui/css/dxt_desktop_print.c7687de8937417888ede.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /medialibrary/media/v5/dxt-ui/css/dxt_desktop_print.c7687de8937417888ede.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.