Skip to content
https://cookpad.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
F
Alt Text Quality
Action
10 of 26 images have issues
FIX
10 of 26 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
10 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
3 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
26 images 13 good alt text 3 decorative 10 missing
IssueCount
missing10 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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.

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
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (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

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="commit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="navigation_search">; <input type="text" name="q">
3 controls
0 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#navigation_searchtext(Busca por receta o ingredientes)placeholder only
qtext(Busca por receta o ingredientes)placeholder only
commitsubmit(none)none

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

<input type="submit" name="commit">

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" name="q" id="navigation_search">; <input type="text" name="q">

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
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title The page you requested was not found - Cookpad ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Cookpad - ¡Hacemos que cocinar cada día sea una diversión!
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Cookpad - ¡Hacemos que cocinar cada día sea una diversión! ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Name Cookpad - ¡Hacemos que cocinar cada día sea una diversión! Icons 3 icon(s)
C
Lighthouse Accessibility Audits
Action
Score 70/100 — 8 failing, 18 passed
REVIEW
70

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Buscar div.navigation-container > nav#sidebar-navigation > div.bg-cookpad-white > ul.flex

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Premium div.bg-cookpad-white > ul.flex > li.px-[20px] > a.flex
Retos div.bg-cookpad-white > ul.flex > li.px-[20px] > a.flex
Preguntas frecuentes div.bg-cookpad-white > ul.flex > li.px-[20px] > a.flex
Enviar opinión div.bg-cookpad-white > ul.flex > li.px-[20px] > a.flex
Región div.bg-cookpad-white > ul.flex > li.px-[20px] > a.flex

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.

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
Descárgate la App div.w-full > div.order-3 > a.btn > span.align-middle
Recetas que tienen más de 10 Cooksnaps a > div.flex > div > p.text-cookpad-12
Las recetas más vistas, actualizadas cada día a > div.flex > div > p.text-cookpad-12

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.relative > div.bg-cookpad-gray-700 > picture > img.h-full div.relative > div.bg-cookpad-gray-700 > picture > img.h-full
div.relative > div.bg-cookpad-gray-700 > picture > img.h-full div.relative > div.bg-cookpad-gray-700 > picture > img.h-full
div.relative > div.bg-cookpad-gray-700 > picture > img.h-full div.relative > div.bg-cookpad-gray-700 > picture > img.h-full
div.relative > div.bg-cookpad-gray-700 > picture > img.h-full div.relative > div.bg-cookpad-gray-700 > picture > img.h-full
div.relative > div.bg-cookpad-gray-700 > picture > img.h-full div.relative > div.bg-cookpad-gray-700 > picture > img.h-full
div.relative > div.bg-cookpad-gray-700 > picture > img.h-full div.relative > div.bg-cookpad-gray-700 > picture > img.h-full
div.relative > div.bg-cookpad-gray-700 > picture > img.h-full div.relative > div.bg-cookpad-gray-700 > picture > img.h-full
div.relative > div.bg-cookpad-gray-700 > picture > img.h-full div.relative > div.bg-cookpad-gray-700 > picture > img.h-full
a > div.flex > div.relative > img.absolute a > div.flex > div.relative > img.absolute
a > div.flex > div.relative > img.absolute a > div.flex > div.relative > img.absolute

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.swiper > ul.swiper-wrapper > li.swiper-slide > a.banner div.swiper > ul.swiper-wrapper > li.swiper-slide > a.banner

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Premium nav#sidebar-navigation > div.bg-cookpad-white > ul.flex > li.px-[20px]
Retos nav#sidebar-navigation > div.bg-cookpad-white > ul.flex > li.px-[20px]
Preguntas frecuentes nav#sidebar-navigation > div.bg-cookpad-white > ul.flex > li.px-[20px]
Enviar opinión nav#sidebar-navigation > div.bg-cookpad-white > ul.flex > li.px-[20px]
Región nav#sidebar-navigation > div.bg-cookpad-white > ul.flex > li.px-[20px]

These are opportunities to improve the experience of reading tabular or list data using 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
Slide 1 div.sm:hidden > div.relative > div.absolute > button.swiper-pagination-bullet
Slide 2 div.sm:hidden > div.relative > div.absolute > button.swiper-pagination-bullet
Slide 3 div.sm:hidden > div.relative > div.absolute > button.swiper-pagination-bullet

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.js html.js

These items highlight common accessibility best practices.

○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
●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.
●ARIA attributes are used as specified for the element's role
●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>`).
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○Elements with visible text labels have matching accessible names.
○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
Heading Hierarchy
4 headings
PASS
4 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Lo más buscado
  • H1 Premium duplicate H1
  • H2 Las recetas más cooksnappeadas
  • H2 Las recetas más visitadas

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
Favicon & Branding
13 icon(s) detected
PASS
13 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: //global-web-assets.cpcdn.com/packs/css/print-4bd48ce3.css
Print Stylesheet ✓ Print Optimized
Print stylesheet //global-web-assets.cpcdn.com/packs/css/print-4bd48ce3.css ✓Inline @media print Not detected ✗
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 Lo más buscado21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Premium21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Las recetas más coo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Las recetas más vis…21.00:13.0:1
#000000
#FFFFFF
Pass
title Cookpad - Cocina cas…21.00:14.5:1
#000000
#FFFFFF
Pass
div Regístrate o entra21.00:14.5:1
#000000
#FFFFFF
Pass
div Guarda recetas, sigu…19.46:14.5:1
#000000
#F8F6F2
Pass
div Buscar19.46:14.5:1
#000000
#F8F6F2
Pass
div Premium19.46:14.5:1
#000000
#F8F6F2
Pass
div Las recetas más coo…19.46:14.5:1
#000000
#F8F6F2
Pass
div Acceso diario al ran…19.46:14.5:1
#000000
#F8F6F2
Pass
div Premium19.46:14.5:1
#000000
#F8F6F2
Pass
div Retos19.46:14.5:1
#000000
#F8F6F2
Pass
div Preguntas frecuentes19.46:14.5:1
#000000
#F8F6F2
Pass
div Enviar opinión19.46:14.5:1
#000000
#F8F6F2
Pass
div Región19.46:14.5:1
#000000
#F8F6F2
Pass
div Tu biblioteca19.46:14.5:1
#000000
#F8F6F2
Pass
div Tu biblioteca19.46:14.5:1
#000000
#F8F6F2
Pass
div Para empezar a crear…19.46:14.5:1
#000000
#F8F6F2
Pass
a registrarse o entrar19.46:14.5:1
#000000
#F8F6F2
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