Skip to content
https://foodnetwork.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
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 Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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 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

B
Heading Hierarchy
72 headings, 1 skip(s)
REVIEW
72 headings, 1 skip(s)
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Michel Roux's Pear and Plum Crumble
  • H3 Asma Khan's Courgette and Pea Paratha
  • H3 Tom Kerridge's Pickled Onion & Blue Cheese Sausage Rolls
  • H3 Cauliflower Kung Pao
  • H3 Hot Cross Buns
  • H3 Carrot Cake Jelly Roll
  • H3 Duck Fat Potatoes
  • H3 What to Eat (and Drink) in London this Week: 13th April
  • H3 Mike Reid on Setting Foundations, Stock-Making, and Suckling Pig Tacos
  • H3 What Fruit is in Season?
  • H3 Ravneet Gill
  • H3 Asma Khan
  • H3 Sophie Grigson
  • H3 Tom Kerridge
  • H3 Tom Kerridge Secrets Of The Pub Kitchen
  • H3 Secrets of the Curry Kitchen
  • H3 Adam Richman Eats Italy
  • H3 Easter Sweets & Chocolate Drink Pairings
  • H3 Sage & Brown Butter Turkey
  • H3 Asparagus & Tarragon Mayo Recipe With Laphroaig Single Malt Whisky
  • H3 Chocolate Sundae Cake Bar
  • H1 Adam Richman Eats Italy
  • H1 Guess What's in Season? duplicate H1
  • H1 Adam Richman Eats Italy duplicate H1
  • H1 Guess What's in Season? duplicate H1
  • H5 Watch the Shows skipped
  • H5 TV Schedule
  • H3 Ravneet Gill's Chop House
  • H3 Watch Secrets of the Curry Kitchen
  • H3 The Great British Bake-Off
  • H3 The Great British Bake-Off
  • H2 The Tuna Steak
  • H3 Grilled Tuna Steaks
  • H3 Seared Tuna & Avocado Rolls
  • H3 Tuna Steak Burgers
  • H3 Teriyaki Ginger Tuna Skewers
  • H3 Tart and Crunchy Fresh Tuna Salad
  • H2 Estiatorio Milos
  • H2 Fancy a Read?
  • H3 What to Eat (and Drink) in London this Week: 13th April
  • H3 Where Simplicity and Grandeur Collide: Estiatorio Milos
  • H3 Mike Reid on Setting Foundations, Stock-Making, and Suckling Pig Tacos
  • H3 What Fruit is in Season?
  • H4 Popular Shows This Week
  • H2 Popular Shows This Week
  • H3 Secrets of the Curry Kitchen
  • H3 Adam Richman Eats Italy
  • H3 Ravneet Gill's Chop House
  • H3 Tom Kerridge: Secrets of The Pub Kitchen
  • H2 Taste the World
  • H3 Indian Starters
  • H3 Vegan Spanish Recipes
  • H3 Taste the World
  • H3 French Touch: Baguette Lunch Ideas
  • H3 Mexican Party Recipes: Crowd-Pleasing Dishes for Your Next Fiesta
  • H3 Air Fryer Recipes
  • H3 Spring Recipes Using Spinach
  • H3 Brownie Pudding
  • H3 Marcus Wareing's Salmon Pithivier with Spring Onions, Chives and Dill
  • H3 Mediterranean Asparagus Recipes: Elegant and Easy Dishes for Spring
  • H3 30+ Naturally Gluten-Free Dinners
  • H3 Vietnamese Lunch Recipes: Fresh and Flavourful
  • H3 Make Her Day with Mother's Day Lunch Recipes
  • H3 Tom Kerridge’s Ultimate Gravy
  • H3 Sweet Potatoes Vs White Potatoes: Which Are Healthier?
  • H3 Breakfasts to Make with Plant-Based Milk
  • H3 St Patrick's Day on Food Network
  • H3 Serving Caribbean Cuisine on the Plate it Deserves: Our Chat with Natty Can Cook
  • H3 What is Matcha
  • H3 Spring Sunshine: Mediterranean Easter Recipes
  • H3 Delicious Spring Roll Lunch Ideas
  • H3 How to Tenderise Steak

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

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputtext(Search recipes...)placeholder only
selectselect(none)none

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

<select>

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 23 passed
REVIEW
83

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.flex > div.flex > button.bg-maroon div.container > div.flex > div.flex > button.bg-maroon
div.container > div.flex > div.flex > button.flex div.container > div.flex > div.flex > button.flex

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
div.flex > ul.flex > li > a.bg-cream div.flex > ul.flex > li > a.bg-cream
div.flex > ul.flex > li > a.bg-cream div.flex > ul.flex > li > a.bg-cream
div.flex > ul.flex > li > a.bg-cream div.flex > ul.flex > li > a.bg-cream
div.flex > ul.flex > li > a.bg-cream div.flex > ul.flex > li > a.bg-cream
div.max-lg:order-1 > ul.flex > li.max-lg:text-center > a.border div.max-lg:order-1 > ul.flex > li.max-lg:text-center > a.border
div.max-lg:order-1 > ul.flex > li.max-lg:text-center > a.border div.max-lg:order-1 > ul.flex > li.max-lg:text-center > a.border
div.max-lg:order-1 > ul.flex > li.max-lg:text-center > a.border div.max-lg:order-1 > ul.flex > li.max-lg:text-center > a.border
div.max-lg:order-1 > ul.flex > li.max-lg:text-center > a.border div.max-lg:order-1 > ul.flex > li.max-lg:text-center > a.border

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.

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
55 RECIPES div.col > a.block > div.px-[8px] > p.h5
11 RECIPES div.col > a.block > div.px-[8px] > p.h5
48 RECIPES div.col > a.block > div.px-[8px] > p.h5
125 RECIPES div.col > a.block > div.px-[8px] > p.h5
ARTICLE div.w-1/2 > div.relative > a.block > span.block
ARTICLE div.w-1/2 > div.relative > a.block > span.block
ARTICLE div.w-1/2 > div.relative > a.block > span.block

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
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-*]` 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
●Image elements have `[alt]` attributes
●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
●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.
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○`<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.
○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.
A+
Alt Text Quality
All 107 images OK
PASS
All 107 images OK
Info::
67 decorative image(s) correctly marked
Info::
40 image(s) with good alt text
107 images 40 good alt text 67 decorative
All images have appropriate alt text.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Adam Richman Eats It…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Guess What's in Seas…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Adam Richman Eats It…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Guess What's in Seas…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fancy a Read?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Popular Shows This W…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Taste the World21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Michel Roux's Pear a…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Asma Khan's Courgett…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Tom Kerridge's Pickl…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cauliflower Kung Pao21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hot Cross Buns21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Carrot Cake Jelly Ro…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Duck Fat Potatoes21.00:13.0:1
#000000
#FFFFFF
Pass
h3 What to Eat (and Dri…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Mike Reid on Setting…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 What Fruit is in Sea…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ravneet Gill21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Asma Khan21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sophie Grigson21.00:13.0:1
#000000
#FFFFFF
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback