Skip to content
https://persee.fr

Accessibility

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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'>.
✓ favicon.ico Present
✓ 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.
D
Lighthouse Accessibility Audits
Action
Score 64/100 — 7 failing, 15 passed
FIX
64

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

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FR EN body.persee > header#sidebar
Informations Au sujet de persee.fr Votre collection sur persee.fr   Nous contac… div.persee_content-nobox > div.persee_content > div.content > footer#footer

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
Portail Persée body.persee > header#persee-headbar > a.a_css
alités div.portlet-body > div.persee_news > h3 > span.perseePrimary
en chiffres div.portlet-body > div#doc-count > h4.title > span.emphasis
nous ? div.persee_content-nobox > div.persee_content > h4.title > span.perseePrimary

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
info.persee.fr div.persee_content > div.content > p > a
info.persee.fr div.persee_content > div.content > p > a
Publications de l'EHESS div.persee_content > div.content > p > a
Les Jeux olympiques div.content > ul > li > a
Les origines des jeux olympiques mythes et réalités div.content > ul > li > a
Les jeux olympiques dans l'Antiquité div.content > ul > li > a
Jeux Olympiques : du signal universel à la pluralité des images div.content > ul > li > a
Jeux et enjeux olympiques div.content > ul > li > a
Chiffres clés et premières analyses des Jeux olympiques et paralympiques div.content > ul > li > a
Persée footer > footer#footer-small > section#copyright > a

These are opportunities to improve the legibility of your content.

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
Persée en chiffres div.portlet-borderless-container > div.portlet-body > div#doc-count > h4.title

These are opportunities to improve keyboard navigation in your application.

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.persee_news > p > a.picto > img.default-picto div.persee_news > p > a.picto > img.default-picto

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.content > header#header-banner > section#banner > a
div.portlet-body > div.persee_news > p > a.picto div.portlet-body > div.persee_news > p > a.picto
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content > div.content > p > a div.persee_content > div.content > p > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content-withpic > div.persee_content > div.content > a div.persee_content-withpic > div.persee_content > div.content > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content > div.content > p > a div.persee_content > div.content > p > a

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
Au sujet de persee.fr div.content > footer#footer > section#information > a
Votre collection sur persee.fr div.content > footer#footer > section#information > a
Interopérabilité div.content > footer#footer > section#resources > a
Modèles documentaires div.content > footer#footer > section#resources > a
Statistiques de consultation div.content > footer#footer > section#resources > a
Kit logos div.content > footer#footer > section#resources > a
CGU div.content > footer#footer > section#misc > a
Mentions légales div.content > footer#footer > section#misc > a
Crédits div.content > footer#footer > section#misc > a
Politique d'archivage pérenne div.content > footer#footer > section#misc > a

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●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.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
C
Heading Hierarchy
Action
18 headings, 1 skip(s)
REVIEW
18 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Actualités
  • H4 Persée rejoint le Keepers Registry
  • H4 Publication du rapport d’activité 2024
  • H3 Nouvelles revues en ligne
  • H4 Cahiers de Linguistique sociale
  • H4 Cahiers du Brésil contemporain
  • H4 Publications de l'EHESS : Affaires et gens d'affaires
  • H3 Ils font la une
  • H4 Focus sur...
  • H4 (empty)
  • H2 Les jeux olympiques d’hiver à Milan et Cortinal d’Ampezzo
  • H4 Persée en chiffres skipped
  • H4 Qui sommes nous ?
  • H4 Outils
  • H3 Informations
  • H3 Ressources
  • H3 Suivez-nous
  • H3 Légal

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Persée ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Landmark Structure
6 landmarks
PASS
6 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 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
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input name="q">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
qinput(Rechercher dans tout Persée…)placeholder only

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

<input 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

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
h2 Les jeux olympiques …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Actu20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Nouvelles16.52:13.0:1
#000000
#E4E4E4
Pass
h3 Ils font la21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Informations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ressources21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Suivez-nous21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Légal21.00:13.0:1
#000000
#FFFFFF
Pass
title Persée : Accéder …20.12:14.5:1
#000000
#FAFAFA
Pass
a Saut au contenu17.46:14.5:1
#000000
#EAEAEA
Pass
a Persée18.43:14.5:1
#000000
#F0F0F0
Pass
a Portail Persée20.12:14.5:1
#000000
#FAFAFA
Pass
a Perséides17.46:14.5:1
#000000
#EAEAEA
Pass
a Data Persée18.43:14.5:1
#000000
#F0F0F0
Pass
a Parcourir les collec…20.12:14.5:1
#000000
#FAFAFA
Pass
span alités17.46:14.5:1
#000000
#EAEAEA
Pass
h4 Persée rejoint le K…18.43:13.0:1
#000000
#F0F0F0
Pass
p Le 13 mars 2025, Per…20.12:14.5:1
#000000
#FAFAFA
Pass
a info.persee.fr17.46:14.5:1
#000000
#EAEAEA
Pass
h4 Publication du rappo…18.43:13.0:1
#000000
#F0F0F0
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