Skip to content
https://gettyimages.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
11 landmarks
FIX
11 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
8 <nav> landmark(s) found
Warning::
8 of 8 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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

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

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

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
No dark mode signals
FIX
No dark mode signals
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 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.

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
No navigation patterns
FIX
No navigation patterns
Info::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 8 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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 Images ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
10 icon(s) detected
REVIEW
10 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h1 Move the world
1.38:1
#000000
on
#3F1C0F
needs 3.0:1 (large text)
32px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Move the world1.38:13.0:1
#000000
#3F1C0F
Fail
title Royalty-Free Stock P…7.70:14.5:1
#000000
#A98EE6
Pass
span Pricing7.70:14.5:1
#000000
#A98EE6
Pass
span Boards16.60:14.5:1
#000000
#F7DEEB
Pass
span AI Generator16.60:14.5:1
#000000
#F7DEEB
Pass
span Sign in16.60:14.5:1
#000000
#F7DEEB
Pass
span Creative21.00:14.5:1
#000000
#FFFFFF
Pass
span Creative Content21.00:14.5:1
#000000
#FFFFFF
Pass
span Images21.00:14.5:1
#000000
#FFFFFF
Pass
span Creative Images21.00:14.5:1
#000000
#FFFFFF
Pass
p Browse millions of r…21.00:14.5:1
#000000
#FFFFFF
Pass
a See all creative ima…21.00:14.5:1
#000000
#FFFFFF
Pass
a Top image searches21.00:14.5:1
#000000
#FFFFFF
Pass
span Curated by Getty Ima…21.00:14.5:1
#000000
#FFFFFF
Pass
a Arbor Day21.00:14.5:1
#000000
#FFFFFF
Pass
a ANZAC Day21.00:14.5:1
#000000
#FFFFFF
Pass
a Palm Sunday21.00:14.5:1
#000000
#FFFFFF
Pass
a Cinco de Mayo21.00:14.5:1
#000000
#FFFFFF
Pass
a Victoria Day9.88:14.5:1
#000000
#D2AB81
Pass
a Shavuot11.75:14.5:1
#000000
#DDBC9D
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
Heading Hierarchy
10 headings, 1 skip(s)
PASS
10 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Move the world
  • H3 Picture This Nation: America's 250th skipped
  • H3 Official FIFA World Cup 2026™ Coverage
  • H3 Never Lose a Download Again
  • H3 Picture This Nation: America's 250th
  • H3 Official FIFA World Cup 2026™ Coverage
  • H3 Never Lose a Download Again
  • H3 Picture This Nation: America's 250th
  • H3 Official FIFA World Cup 2026™ Coverage
  • H3 Never Lose a Download Again

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

A+
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
3 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
14 images 11 good alt text 3 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
phraseinputtextaria-label
A
Lighthouse Accessibility Audits
Score 90/100 — 5 failing, 22 passed
PASS
90

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.

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
Picture This Nation: America's 250th figure.cjB1mFnxUs_IYrgkWdNE > figcaption.L9a3UTurR7LSze8J9qks > div.DiPuLsN83JMiloufJykl > h3.pJ1YfLNmNK295rBgSIfG

These are opportunities to improve keyboard navigation in your application.

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
ul.Ond_W20QAlkjVPGWIpi0 > li.lllaUhwFL8aASAQY2DR4 > div.qTHql9QjEdPFy_GVOIdG > a.Im6rD6w_JdK2_9OqWP0e ul.Ond_W20QAlkjVPGWIpi0 > li.lllaUhwFL8aASAQY2DR4 > div.qTHql9QjEdPFy_GVOIdG > a.Im6rD6w_JdK2_9OqWP0e
ul.Ond_W20QAlkjVPGWIpi0 > li.lllaUhwFL8aASAQY2DR4 > div.qTHql9QjEdPFy_GVOIdG > a.Im6rD6w_JdK2_9OqWP0e ul.Ond_W20QAlkjVPGWIpi0 > li.lllaUhwFL8aASAQY2DR4 > div.qTHql9QjEdPFy_GVOIdG > a.Im6rD6w_JdK2_9OqWP0e
div.IJEiQw_92EIeiLKILVLA > div.l7uMfyjmeOP24R9PYui2 > div.cHim_DwI8m09KA6b0wiZ > a.zGxHlTyllL1AqMMFwMG7 div.IJEiQw_92EIeiLKILVLA > div.l7uMfyjmeOP24R9PYui2 > div.cHim_DwI8m09KA6b0wiZ > a.zGxHlTyllL1AqMMFwMG7
div.IJEiQw_92EIeiLKILVLA > div.l7uMfyjmeOP24R9PYui2 > div.lRFNsjW_nZ4m_IpxII1W > a.zGxHlTyllL1AqMMFwMG7 div.IJEiQw_92EIeiLKILVLA > div.l7uMfyjmeOP24R9PYui2 > div.lRFNsjW_nZ4m_IpxII1W > a.zGxHlTyllL1AqMMFwMG7
div > div.fE8z5_QW3eQx6YzMCdiH > div > a.qYOl7RHtZB4KlzVZhaY2 div > div.fE8z5_QW3eQx6YzMCdiH > div > a.qYOl7RHtZB4KlzVZhaY2
div > div.fE8z5_QW3eQx6YzMCdiH > div > a.qYOl7RHtZB4KlzVZhaY2 div > div.fE8z5_QW3eQx6YzMCdiH > div > a.qYOl7RHtZB4KlzVZhaY2
div > div.fE8z5_QW3eQx6YzMCdiH > div > a.qYOl7RHtZB4KlzVZhaY2 div > div.fE8z5_QW3eQx6YzMCdiH > div > a.qYOl7RHtZB4KlzVZhaY2

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

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
Go to slide 1 div > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Site map div.yI7lAr36C5eQWXV4CXLL > div.sWVMdSFr8Yy4tcr3eaWO > div > a.Im6rD6w_JdK2_9OqWP0e

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.en-us html.en-us

These items highlight common accessibility best practices.

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
United States div.IJEiQw_92EIeiLKILVLA > div.l7uMfyjmeOP24R9PYui2 > div.lRFNsjW_nZ4m_IpxII1W > button.YfyYzPmm8jp_HBImgqyQ
TOOLS & SERVICES div.l7uMfyjmeOP24R9PYui2 > div.lRFNsjW_nZ4m_IpxII1W > div > button.YfyYzPmm8jp_HBImgqyQ
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○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
○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.
○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