Accessibility

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 2 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

B

Link & Button Quality

1 issue(s) across 144 links and 5 buttons

REVIEW

1 issue(s) across 144 links and 5 buttons

1 link(s) with no accessible text

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

Got: a (#346 on page)

2 link(s) open in new tab without warning

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

Got: https://www.citypass.com/new-york?mv_source=guggenheim&campaign=footer; https://cloud.emails.guggenheim.org/newsletter

141 link(s) with descriptive text

144 links

1 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.citypass.com/new-york?mv_sou…	CityPASS®	new tab	Add '(opens in new tab)' to text
https://cloud.emails.guggenheim.org/news…	Subscribe	new tab	Add '(opens in new tab)' to text

146 links and buttons have descriptive text

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

a (#346 on page)

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.

https://www.citypass.com/new-york?mv_source=guggenheim&campaign=footer; https://cloud.emails.guggenheim.org/newsletter

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

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Homepage | The Guggenheim Museums and Foundation ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

C

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

C

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 16 pass AA only

h2 The Frank Lloyd Wright Building

1.11:1

#000000

on

#111111

needs 3.0:1 (large text)

24px · mid-page

h2 Exhibitions on View

1.11:1

#000000

on

#111111

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Welcome	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Prepare to Visit	7.69:1	3.0:1	#000000	#9E9D91	Pass
h2 Visitor Information	8.00:1	3.0:1	#000000	#AE9D8C	Pass
h2 The Frank Lloyd Wrig…	1.11:1	3.0:1	#000000	#111111	Fail
h2 Exhibitions on View	1.11:1	3.0:1	#000000	#111111	Fail
h2 Upcoming Exhibitions	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Past Exhibitions	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Calendar	3.53:1	3.0:1	#000000	#72614B	Pass
h2 In-Person Experience…	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Find a Program	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Collection Online	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Research	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Initiatives & Projec…	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Discover More	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Families & Teens	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Schools & Educators	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Adult Programs	3.53:1	3.0:1	#000000	#72614B	Pass
h2 University Students	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Membership	3.53:1	3.0:1	#000000	#72614B	Pass
h2 Support	3.53:1	3.0:1	#000000	#72614B	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

10 landmarks

PASS

10 landmarks

<main> landmark present

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

51 headings

PASS

51 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Prepare to Visit
H2 Visitor Information
H2 The Frank Lloyd Wright Building
H2 Exhibitions on View
H2 Upcoming Exhibitions
H2 Past Exhibitions
H2 Calendar
H2 In-Person Experiences
H2 Find a Program
H2 Collection Online
H2 Research
H2 Initiatives & Projects
H2 Discover More
H2 Families & Teens
H2 Schools & Educators
H2 Adult Programs
H2 University Students
H2 Membership
H2 Support
H2 Donate
H2 Shop by Category
H2 Shop by Interest
H2 Store Discounts
H1 Welcome
H2 On View Now
H3 Carol Bove
H3 Gabriele Münter: Contours of a World
H3 Collection in Focus | Robert Rauschenberg: Life Can’t Be Stopped
H3 Collection in Focus | Modern European Currents
H3 Thannhauser Collection
H2 Upcoming Events
H3 Curious about the Building?
H3 Mind’s Eye: Carol Bove
H2 From the Collection
H3 (empty)
H2 Poetry at the Guggenheim
H2 Art for Everyone
H2 Shop
H2 Membership
H3 Hours
H3 Address
H3 Tickets
H3 About Us
H3 Stay Connected
H3 Follow Us
H3 Opportunities
H3 Inquiries
H3 Resources
H3 Around the World
H3 Global Partners
H3 UNESCO World Heritage Site

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

A

Alt Text Quality

1 of 19 images have issues

PASS

1 of 19 images have issues

1 image(s) with generic alt text

8 image(s) with alt text over 125 characters

10 image(s) with good alt text

19 images 10 good alt text 1 generic

Issue	Count
generic	1 image(s)
too long	8 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 27 passed

PASS

96

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Pause video `div > div._videoBanner_1ri24_2 > div._overlaySvgs_1ri24_38 > svg`
Unmute video `div > div._videoBanner_1ri24_2 > div._overlaySvgs_1ri24_38 > svg`
Learn more `div > div._videoBanner_1ri24_2 > div._overlaySvgs_1ri24_38 > svg`

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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●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

●Elements with visible text labels have matching accessible names.

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

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

○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

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