Skip to content
https://www.sorbonne-universite.fr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
41
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
F
Heading Hierarchy
Action
62 headings, 7 skip(s)
FIX
62 headings, 7 skip(s)
Warning::
Multiple H1 headings (26 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Les journées arts & culture dans l’enseignement supérieur - JACES 2026
  • H1 Science et décision publique : comment peser ? duplicate H1
  • H1 Une page du palimpseste d’Archimède redécouverte après plus d’un siècle duplicate H1
  • H1 Les journées arts & culture dans l’enseignement supérieur - JACES 2026 duplicate H1
  • H1 Science et décision publique : comment peser ? duplicate H1
  • H1 Accès directs duplicate H1
  • H4 Préparer votre rentrée skipped
  • H4 Soutenir notre action
  • H4 Louer nos espaces
  • H4 Bibliothèques
  • H4 Service des Archives
  • H4 Espace Presse
  • H1 Expliquer, partager, convaincre duplicate H1
  • H4 Nos Actualités skipped
  • H1 South Pole Telescope : notre modèle de l’Univers est-il à réviser ? duplicate H1
  • H1 SN@SU : une plateforme open-access de ressources pédagogiques pour la formation à la santé numérique duplicate H1
  • H1 Toba, le volcan qui a failli tuer l’humanité duplicate H1
  • H1 Finale Alliance Sorbonne Université MT180 duplicate H1
  • H4 Nos événements skipped
  • H1 Le Populisme sauvera-t-il la démocratie ? duplicate H1
  • H1 Exposition « Création, entre arts et mathématiques » duplicate H1
  • H1 Journées Filles, Maths et Informatique duplicate H1
  • H1 Rencontre autour de la parution de l’ouvrage "Faire Science Ensemble" duplicate H1
  • H1 Nos visages, notre force ! duplicate H1
  • H4 Marie Jaspard skipped
  • H3 Spécialiste des maladies infectieuses et tropicales
  • H4 Frédéric Decremps
  • H3 Professeur de physique et écrivain
  • H4 Léa Griton
  • H3 Astrophysicienne
  • H2 Les parutions de la communauté Sorbonne Université
  • H1 Recherche sans filtre duplicate H1
  • H1 Les Dentelles noires de l’Etna duplicate H1
  • H2 Université européenne 4EU+
  • H4 Actualités de l'Alliance Sorbonne Université skipped
  • H1 Participez à une étude sur le gaspillage alimentaire duplicate H1
  • H1 9e appel à candidatures myStartup Program duplicate H1
  • H1 Appel à projets : financements REAL@SU duplicate H1
  • H1 MSCA Postdoctoral Fellowships 2026 duplicate H1
  • H4 Agenda skipped
  • H1 Exposition "Paysage témoin" duplicate H1
  • H1 Dire le monde – Émotion, censure et imagination duplicate H1
  • H1 Circulation de plantes et d'animaux entre Amérique et Europe duplicate H1
  • H1 "La cité et le nombre", un séminaire sur les mathématiques grecques anciennes duplicate H1
  • H3 53 000 skipped
  • H4 étudiantes et étudiants
  • H3 3 800
  • H4 doctorantes et doctorants
  • H3 3 300
  • H4 personnels enseignants et chercheurs
  • H3 3 500
  • H4 personnels administratifs et techniques
  • H3 145
  • H4 unités de recherche
  • H3 23
  • H4 écoles doctorales
  • H3 18
  • H4 instituts thématiques pluridisciplinaires
  • H3 14 500
  • H4 alumni actifs dans le réseau
  • H4 Retrouvez-nous !
  • H2 Vos paramètres de cookies

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

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

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

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

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

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

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

F
Alt Text Quality
Action
9 of 24 images have issues
FIX
9 of 24 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
15 image(s) with good alt text
24 images 15 good alt text 9 missing
IssueCount
missing9 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
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.
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 Page non trouvée | Sorbonne Université| Sorbonne université ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
title Sorbonne Université| Sorbonne universit…
2.18:1
#000000
on
#22495C
needs 4.5:1 (normal text)
16px · top of page (header area)
button Skip to main navigation
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
button Aller au contenu principal
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
button Skip to search
1.40:1
#000000
on
#1C2833
needs 4.5:1 (normal text)
16px · top of page (header area)
span Université
1.42:1
#000000
on
#1D2935
needs 4.5:1 (normal text)
16px · above the fold
span Lettres
1.46:1
#000000
on
#1F2B35
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Expliquer, partager,…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Nos visages, notre f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Les parutions de la …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Université europée…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Vos paramètres de c…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Spécialiste des mal…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Professeur de physiq…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Astrophysicienne21.00:13.0:1
#000000
#FFFFFF
Pass
h3 53 00021.00:13.0:1
#000000
#FFFFFF
Pass
h3 3 80021.00:13.0:1
#000000
#FFFFFF
Pass
h3 3 30021.00:13.0:1
#000000
#FFFFFF
Pass
h3 3 50021.00:13.0:1
#000000
#FFFFFF
Pass
h3 14521.00:13.0:1
#000000
#FFFFFF
Pass
h3 14 50021.00:13.0:1
#000000
#FFFFFF
Pass
title Sorbonne Université…2.18:14.5:1
#000000
#22495C
Fail
button Skip to main navigat…3.66:14.5:1
#000000
#666666
Fail
button Aller au contenu pri…3.66:14.5:1
#000000
#666666
Fail
button Skip to search1.40:14.5:1
#000000
#1C2833
Fail
span Université1.42:14.5:1
#000000
#1D2935
Fail
span Lettres1.46:14.5:1
#000000
#1F2B35
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 21 passed
REVIEW
80

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.header__content > div.header__item > div#mobile-trigger-container > button.hamburger div.header__content > div.header__item > div#mobile-trigger-container > button.hamburger

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.swiper-slide > a.hero__row > div.hero__img > img.img-fluid div.swiper-slide > a.hero__row > div.hero__img > img.img-fluid
div.swiper-slide > div.thumbnail > a.thumbnail__img > img.lazyload div.swiper-slide > div.thumbnail > a.thumbnail__img > img.lazyload
div.swiper-slide > div.thumbnail > a.thumbnail__img > img.lazyload div.swiper-slide > div.thumbnail > a.thumbnail__img > img.lazyload
main.wrapper > div.c-keyfigures > div.c-keyfigures__img > img.lazyload main.wrapper > div.c-keyfigures > div.c-keyfigures__img > img.lazyload
div.row > div.col-12 > a.footer__logo > img.img-fluid div.row > div.col-12 > a.footer__logo > img.img-fluid

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.container > div.header__content > div.header__item > a.header__logo div.container > div.header__content > div.header__item > a.header__logo
Plateforme SN@SU div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img
Finale MT180 2026 div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img
div.swiper-slide > div.book > div.book__img > a div.swiper-slide > div.book > div.book__img > a
div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img
Laurence Guyonneau-Harmand, Mathias Brunet-Manquat div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img
div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img
div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img div.swiper-wrapper > div.swiper-slide > div.thumbnail > a.thumbnail__img
div.container > div.row > div.col-12 > a.footer__logo div.container > div.row > div.col-12 > a.footer__logo

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
LETTRES div.layers > ul.layers__triggers > li.layers__trigger > span
SCIENCES & INGÉNIERIE div.layers > ul.layers__triggers > li.layers__trigger > span

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
PRÉPARER VOTRE RENTRÉE div.swiper-wrapper > div.swiper-slide > a.access-box > h4.access-label
Nos Actualités div.row > div.newsroom__cell > div.newsroom__content > h4.dash
Nos événements div.row > div.newsroom__cell > div.newsroom__content > h4.dash
Marie Jaspard div.swiper-slide > a.profile-box > div.profile-box__inner > h4.dash
Actualités de l'Alliance Sorbonne Université div.row > div.newsroom__cell > div.newsroom__content > h4.dash
Agenda div.row > div.newsroom__cell > div.newsroom__content > h4.dash
53 000 div.col-12 > div.c-keyfigures__box > div.c-keyfigures__body > h3.c-keyfigures__figure

These are opportunities to improve keyboard navigation in your application.

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
ACCÈS DIRECTS div.hero > div.hero__access > div.access > button.access-trigger
○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
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●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.
●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-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 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
Landmark Structure
4 landmarks
PASS
4 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 "Navigation principale" 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 4 controls have issues
PASS
1 of 4 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cookie-category-requiredcheckboxCookies obligatoire (session Drupal)for/id
#cookie-category-statscheckboxCookies de mesure d’audiencefor/id
#cookie-category-videocheckboxCookies vidéosfor/id
#edit-search-api-fulltexttext(Tapez votre recherche ici...)placeholder only

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

<input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">

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

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

Send Feedback