Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 403 ✗Page Title 403 Forbidden ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

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

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

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

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 ✗

Link & Button Quality

162 links, 16 buttons — all OK

REVIEW

162 links, 16 buttons — all OK

6 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/"]; a[href="https://www.ushmm.org/online-calendar"]; a[href="/information/visit-the-museum/hours-location-transportation"]; a[href="/information/exhibitions/museum-exhibitions"]; a[href="/information/visit-the-museum/admission-tickets"]; a[href="/"]

156 link(s) with descriptive text

162 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	homepage	img no alt	Add alt attribute to the image
https://www.ushmm.org/online-calendar	Today at the MuseumPrograms an…	img no alt	Add alt attribute to the image
/information/visit-the-museum/hours-loca…	Hours: 10 a.m. - 5:30 p.m.View…	img no alt	Add alt attribute to the image
/information/exhibitions/museum-exhibiti…	Museum ExhibitionsPermanent an…	img no alt	Add alt attribute to the image
/information/visit-the-museum/admission-…	Admission and TicketsInstructi…	img no alt	Add alt attribute to the image
/	United States Holocaust Memori…	img no alt	Add alt attribute to the image

172 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/"]; a[href="https://www.ushmm.org/online-calendar"]; a[href="/information/visit-the-museum/hours-location-transportation"]; a[href="/information/exhibitions/museum-exhibitions"]; a[href="/information/visit-the-museum/admission-tickets"]; a[href="/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 1 pass AA only

title United States Holocaust Memorial Museum

1.09:1

#000000

#0E0E0E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.61:1

#000000

#313131

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 United States Holoca…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 Visit the Museum	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 National Events	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 Search Our Collectio…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 News	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 Connect with the Mus…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 Get the Latest News	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h3 Alarmingly Relevant:…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h3 2026 Rubin Lecture, …	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h3 Finding Treblinka: F…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h3 2026 New York Next G…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
title United States Holoca…	1.09:1	4.5:1	#000000	#0E0E0E	Fail
a Skip to main content	1.61:1	4.5:1	#000000	#313131	Fail
button Language	5.79:1	4.5:1	#000000	#888684	Pass
a English home page	15.65:1	4.5:1	#000000	#E1DED9	Pass
a المصادر با�…	15.49:1	4.5:1	#000000	#E0DDD7	Pass
a Πηγές στα Ε…	15.64:1	4.5:1	#000000	#E1DED8	Pass
a Recursos en español	15.50:1	4.5:1	#000000	#E0DDD8	Pass
a منابع موجو�…	15.80:1	4.5:1	#000000	#E2DFDA	Pass
a Ressources en franç…	15.95:1	4.5:1	#000000	#E3E0DB	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.

A+

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

12 headings

PASS

12 headings

Single H1 present

H1 United States Holocaust Memorial Museum
H2 Despite The Odds
H2 Visit the Museum
H2 National Events
H3 Alarmingly Relevant: Holocaust Museums in an Age of Rising Holocaust Denial and Antisemitism
H3 2026 Rubin Lecture, Antisemitism Then and Now
H3 Finding Treblinka: Forensic and Archaeological Discoveries
H3 2026 New York Next Generation Event
H2 Search Our Collections
H2 News
H2 Connect with the Museum
H2 Get the Latest News

Alt Text Quality

1 of 17 images have issues

PASS

1 of 17 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with alt text over 125 characters

13 decorative image(s) correctly marked

2 image(s) with good alt text

17 images 2 good alt text 13 decorative 1 missing

Issue	Count
missing	1 image(s)
too long	1 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

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 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="submit">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#searchtext	text	Search the Entire Site	for/id
input	email	Email	none
input	text	First Name	none
input	text	Postal Code	none
input	submit	(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+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 26 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.

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
ENCYCLOPEDIA `section.promo-item > div.promo-item__content > div.promo-item__title > a`
INTRODUCTION TO THE HOLOCAUST `section.promo-item > div.promo-item__content > div.promo-item__title > a`
RESOURCES FOR EDUCATORS `section.promo-item > div.promo-item__content > div.promo-item__title > a`

These are opportunities to improve the legibility of your content.

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
Menu `div.header__container > div.primary-nav > div.primary-nav__menu-button > button`

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

●Form elements have associated labels

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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

○Identical links have the same purpose.

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