Skip to content
https://heinz.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ 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
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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only
h1 Heinz US Hero Banner
2.61:1
#000000
on
#70471D
needs 3.0:1 (large text)
32px · top of page (header area)
h1 GET MORE WITH TASTEVIP
1.94:1
#000000
on
#263F5A
needs 3.0:1 (large text)
32px · above the fold
h1 GET MORE WITH TASTEVIP
1.30:1
#000000
on
#172133
needs 3.0:1 (large text)
32px · mid-page
h2 CHECK ‘EM OUT
2.69:1
#000000
on
#694D27
needs 3.0:1 (large text)
24px · top of page (header area)
h2 FIND YOUR FLAVOR
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 MAKE IT REAL GOOD
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 GET SOCIAL
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recent TikTok Videos
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 WE’RE ALL-IN
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Heinz®
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Our Company
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get In Touch
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Follow Us
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Country/Language
1.44:1
#000000
on
#530B25
needs 3.0:1 (large text)
19px · bottom of viewport
title Heinz Official Site - Heinz® US | Heinz
3.88:1
#000000
on
#D6001C
needs 4.5:1 (normal text)
16px · top of page (header area)
button Skip to main content
3.88:1
#000000
on
#D6001C
needs 4.5:1 (normal text)
16px · top of page (header area)
div Introducing KegChup
1.93:1
#000000
on
#51381C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p Be the first to know when Heinz KegChup …
4.18:1
#000000
on
#8E6746
needs 4.5:1 (normal text)
16px · above the fold
p Made simply with the highest quality ing…
2.13:1
#000000
on
#543F32
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 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
h1 Heinz US Hero Banner2.61:13.0:1
#000000
#70471D
Fail
h1 GET MORE WITH TASTEV…1.94:13.0:1
#000000
#263F5A
Fail
h1 GET MORE WITH TASTEV…1.30:13.0:1
#000000
#172133
Fail
h2 CHECK ‘EM OUT2.69:13.0:1
#000000
#694D27
Fail
h2 FIND YOUR FLAVOR1.44:13.0:1
#000000
#530B25
Fail
h2 MAKE IT REAL GOOD1.44:13.0:1
#000000
#530B25
Fail
h2 GET SOCIAL1.44:13.0:1
#000000
#530B25
Fail
h2 Recent TikTok Videos1.44:13.0:1
#000000
#530B25
Fail
h2 WE’RE ALL-IN1.44:13.0:1
#000000
#530B25
Fail
h3 Heinz®1.44:13.0:1
#000000
#530B25
Fail
h3 Our Company1.44:13.0:1
#000000
#530B25
Fail
h3 Get In Touch1.44:13.0:1
#000000
#530B25
Fail
h3 Follow Us1.44:13.0:1
#000000
#530B25
Fail
h3 Country/Language1.44:13.0:1
#000000
#530B25
Fail
title Heinz Official Site …3.88:14.5:1
#000000
#D6001C
Fail
button Skip to main content3.88:14.5:1
#000000
#D6001C
Fail
div Introducing KegChup1.93:14.5:1
#000000
#51381C
Fail
p Be the first to know…4.18:14.5:1
#000000
#8E6746
Fail
div Simply Tomato Ketchu…5.31:14.5:1
#000000
#937C65
Pass
p Made simply with the…2.13:14.5:1
#000000
#543F32
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
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 Navigation" MAIN CONTENTINFO footer

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

A
Heading Hierarchy
14 headings
PASS
14 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Heinz US Hero Banner
  • H2 CHECK ‘EM OUT
  • H1 GET MORE WITH TASTEVIP duplicate H1
  • H1 GET MORE WITH TASTEVIP duplicate H1
  • H2 FIND YOUR FLAVOR
  • H2 MAKE IT REAL GOOD
  • H2 GET SOCIAL
  • H2 Recent TikTok Videos
  • H2 WE’RE ALL-IN
  • H3 Heinz®
  • H3 Our Company
  • H3 Get In Touch
  • H3 Follow Us
  • H3 Country/Language

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
16 images 13 good alt text 2 decorative
IssueCount
too long1 image(s)
A
Form Accessibility
1 of 6 controls have issues
PASS
1 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
5 control(s) properly labeled
6 controls
5 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputsearchSearch products.aria-label
#firstNameinputFirst Namefor/id
#lastNameinputLast Namefor/id
#emailinputEmailfor/id
marketingCommunicationscheckboxnone
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 28 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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#main-content > div.flex > section.w-screen > div.fixed div#main-content > div.flex > section.w-screen > div.fixed

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.

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
Introducing KegChup Be the first to know when Heinz KegChup drops. div.swiper > div#swiper-wrapper-f610a9ad9a84391108 > div.swiper-slide > a.cursor-pointer
Simply Tomato Ketchup Made simply with the highest quality ingredients div.swiper > div#swiper-wrapper-f610a9ad9a84391108 > div.swiper-slide > a.cursor-pointer
Privacy Policy. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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>`
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○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
○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.
○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