Skip to content
https://www.puma.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
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-ypoy73
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://www.puma.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://www.puma.com/manifest.json

Manifest contains invalid JSON.

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::
218 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 218 <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.
B
Favicon & Branding
10 icon(s) detected
REVIEW
10 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
a Passer directement au contenu principal
4.49:1
#000000
on
#747474
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Passer directement au footer
1.18:1
#000000
on
#181818
needs 4.5:1 (normal text)
16px · top of page (header area)
span Safari
3.96:1
#000000
on
#806658
needs 4.5:1 (normal text)
16px · top of page (header area)
span Google Chrome
3.92:1
#000000
on
#806557
needs 4.5:1 (normal text)
16px · above the fold
span Firefox
3.90:1
#000000
on
#7F6557
needs 4.5:1 (normal text)
16px · above the fold

1 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 PUMA – Vêtements,…6.43:13.0:1
#000000
#898F95
Pass
h2 Inscrivez-vous et b…6.43:13.0:1
#000000
#898F95
Pass
h2 Besoin d'aide ?6.43:13.0:1
#000000
#898F95
Pass
h2 Besoin d'aide ?6.43:13.0:1
#000000
#898F95
Pass
h2 À propos de PUMA6.43:13.0:1
#000000
#898F95
Pass
h2 À propos de PUMA6.43:13.0:1
#000000
#898F95
Pass
h2 Suivez-nous6.43:13.0:1
#000000
#898F95
Pass
h2 Découvrir6.43:13.0:1
#000000
#898F95
Pass
title PUMA FRANCE | Chauss…21.00:14.5:1
#000000
#FFFFFF
Pass
a Passer directement a…4.49:14.5:1
#000000
#747474
Fail
a Passer directement a…1.18:14.5:1
#000000
#181818
Fail
span Safari3.96:14.5:1
#000000
#806658
Fail
span Google Chrome3.92:14.5:1
#000000
#806557
Fail
span Firefox3.90:14.5:1
#000000
#7F6557
Fail
span NON MERCI, PEUT-ÊTR…11.86:14.5:1
#000000
#EABD45
Pass
span PASSE DE 30 À 60 JO…12.04:14.5:1
#000000
#EABF46
Pass
a INSCRIS-TOI12.04:14.5:1
#000000
#EABF46
Pass
span FAIS TON SHOPPING PL…11.95:14.5:1
#000000
#EABE46
Pass
a TÉLÉCHARGE-LA MAIN…11.58:14.5:1
#000000
#E7BB42
Pass
span Puma Home11.11:14.5:1
#000000
#E3B73D
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
Landmark Structure
222 landmarks
PASS
222 landmarks
Info::
<main> landmark present
Info::
218 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Menu" 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
17 headings
PASS
17 headings
Info::
Single H1 present
  • H6 Pour une meilleure expérience, veuillez utiliser l’un des navigateurs suivants :
  • H2 PUMA x POKÉMON PUMA x POKÉMON
  • H2 LA NORME DES ATHLÈTES LA NORME DES ATHLÈTES
  • H2 LA NORME DES ATHLÈTES LA NORME DES ATHLÈTES
  • H2 LA NORME DES ATHLÈTES LA NORME DES ATHLÈTES
  • H2 LA NORME DES ATHLÈTES LA NORME DES ATHLÈTES
  • H2 LA NORME DES ATHLÈTES LA NORME DES ATHLÈTES
  • H2 LA NORME DES ATHLÈTES LA NORME DES ATHLÈTES
  • H1 PUMA – Vêtements, chaussures et accessoires
  • H2 Inscrivez-vous et bénéficiez de 15 % de remise sur votre première commande.
  • H2 Besoin d'aide ?
  • H2 Besoin d'aide ?
  • H2 À propos de PUMA
  • H2 À propos de PUMA
  • H2 Suivez-nous
  • H2 Découvrir
  • H2 CONDITIONS PROMOTIONNELLES
A
Alt Text Quality
1 of 29 images have issues
PASS
1 of 29 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
29 images 25 good alt text 1 decorative 1 missing
IssueCount
missing1 image(s)
too long2 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

A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchRechercheraria-label
qsearchRechercheraria-label
qsearchRechercheraria-label
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 33 passed
PASS
100

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.

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
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
`[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.
`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
`<frame>` or `<iframe>` elements have a title
`<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
ARIA IDs are unique
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
No form fields have multiple labels
`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback