Skip to content
https://getty.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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
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 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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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
Heading Hierarchy
55 headings
REVIEW
55 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Sitewide Messages
  • H2 Site Navigation
  • H3 Visit
  • H3 Primary navigation links
  • H3 Secondary navigation links
  • H3 What's On
  • H3 Primary navigation links
  • H3 Secondary navigation links
  • H3 Explore Art
  • H3 Primary navigation links
  • H3 Secondary navigation links
  • H3 Research & Conservation
  • H3 Primary navigation links
  • H3 Secondary navigation links
  • H3 Funding
  • H3 Primary navigation links
  • H3 Secondary navigation links
  • H3 About
  • H3 Primary navigation links
  • H3 Secondary navigation links
  • H2 Celebrate Earth Month at Getty
  • H3 Celebrate our planet all month long with activities at Getty that highlight the connection between art and our environment.
  • H2 What We Do
  • H3 Our Locations
  • H3 Art & Archives
  • H3 Research & Conservation
  • H2 News & Stories
  • H3 Is Drawing a Form of Self Care?
  • H3 How to Merge with the Gods
  • H3 What Was Life Like for Kids in the Middle Ages?
  • H2 Explore Our Work
  • H3 PST ART 2030
  • H2 Resources
  • H2 Shop
  • H2 Stay Connected
  • H2 Work with Us
  • H2 Contact Us
  • H2 Footer
  • H3 Social Navigation
  • H3 Footer Primary Navigation
  • H3 Getty Center
  • H4 Address
  • H4 Hours
  • H3 Getty Villa
  • H4 Address
  • H4 Hours
  • H3 Site Map Navigation
  • H4 Books and Publications
  • H4 Education
  • H4 Art and Research
  • H4 Opportunities
  • H4 Conservation
  • H4 Funding Opportunities
  • H4 News and Contact
  • H4 © J. Paul Getty Trust

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

B
Alt Text Quality
2 of 11 images have issues
REVIEW
2 of 11 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
11 images 4 good alt text 1 decorative 2 missing
IssueCount
missing2 image(s)
too long4 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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Getty: Resources for Visual Art and Cultural Heritage ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA 17 pass AA only
h2 Site Navigation
2.25:1
#000000
on
#31495F
needs 3.0:1 (large text)
24px · top of page (header area) · over background image/gradient
h3 Primary navigation links
2.66:1
#000000
on
#275958
needs 3.0:1 (large text)
19px · mid-page · over background image/gradient
title Getty: Resources for Visual Art and Cult…
2.17:1
#000000
on
#484622
needs 4.5:1 (normal text)
16px · top of page (header area) · 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)
ElementRatioRequiredFGBGResult
h2 Site Navigation2.25:13.0:1
#000000
#31495F
Fail
h2 Footer4.04:13.0:1
#000000
#4F7374
Pass
h3 Primary navigation l…3.05:13.0:1
#000000
#3F5A8C
Pass
h3 Secondary navigation…4.10:13.0:1
#000000
#5A736B
Pass
h3 Primary navigation l…2.66:13.0:1
#000000
#275958
Fail
h3 Secondary navigation…4.12:13.0:1
#000000
#207D53
Pass
h3 Primary navigation l…4.04:13.0:1
#000000
#4F7374
Pass
h3 Secondary navigation…4.04:13.0:1
#000000
#4F7374
Pass
h3 Primary navigation l…4.04:13.0:1
#000000
#4F7374
Pass
h3 Secondary navigation…4.04:13.0:1
#000000
#4F7374
Pass
h3 Primary navigation l…4.04:13.0:1
#000000
#4F7374
Pass
h3 Secondary navigation…4.04:13.0:1
#000000
#4F7374
Pass
h3 Primary navigation l…4.04:13.0:1
#000000
#4F7374
Pass
h3 Secondary navigation…4.04:13.0:1
#000000
#4F7374
Pass
h3 Social Navigation4.04:13.0:1
#000000
#4F7374
Pass
h3 Footer Primary Navig…4.04:13.0:1
#000000
#4F7374
Pass
h3 Getty Center4.04:13.0:1
#000000
#4F7374
Pass
h3 Getty Villa4.04:13.0:1
#000000
#4F7374
Pass
h3 Site Map Navigation4.04:13.0:1
#000000
#4F7374
Pass
title Getty: Resources for…2.17:14.5:1
#000000
#484622
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+
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Site" MAIN CONTENTINFO footer
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 26 passed
PASS
95

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
A painting of a colorful field of flowers overlaid by the Getty logo. div > div > main > section.o-hero--blocks--simple

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.

Names and labels

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content div > header.g-header > div#skiplink > a.g-header__skip-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.

○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
●Background and foreground colors have a sufficient contrast ratio
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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
●No element has a `[tabindex]` value greater than 0
●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
●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
○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.
○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.
○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.

Send Feedback