Skip to content
https://ens.fr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Heading Hierarchy
Action
15 headings, 2 skip(s)
FIX
15 headings, 2 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::
Heading level skipped: H3 → H5 (missing H4)
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.
  • H2 Rechercher
  • H2 Navigation principale
  • H2 Main and footer menu
  • H2 Navigation principale
  • H2 Dernières actualités
  • H2 Cette semaine à l’ENS
  • H4 Trajectoires skipped
  • H3 Intégrer l'École
  • H5 Vie des campus ENS skipped
  • H6 (empty)
  • H2 Main and footer menu
  • H3 École normale supérieure - PSL
  • H2 Main and footer menu
  • H2 Pied de page
  • H2 Le site de l'École normale supérieure utilise des cookies pour vous offrir la meilleure navigation possible. En continuant, vous en acceptez l'utilisation

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

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

F
Alt Text Quality
Action
15 of 64 images have issues
FIX
15 of 64 images have issues
Critical::
15 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
15 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
49 image(s) with good alt text
64 images 49 good alt text 15 missing
IssueCount
missing15 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
6 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 6 <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.
C
Form Accessibility
Action
3 of 4 controls have issues
REVIEW
3 of 4 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="departements" id="departements">; <select name="laboratoires" id="laboratoires">; <select name="bibliothèques" id="bibliothèques">
Info::
1 control(s) properly labeled
4 controls
1 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#edit-keyssearchRechercherfor/id
#departementsselect(none)none
#laboratoiresselect(none)none
#bibliothèquesselect(none)none

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

<select name="departements" id="departements">; <select name="laboratoires" id="laboratoires">; <select name="bibliothèques" id="bibliothèques">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA 1 pass AA only
h2 Navigation principale
1.58:1
#000000
on
#2C321E
needs 3.0:1 (large text)
24px · above the fold · over background image/gradient
h3 Intégrer l'École
2.01:1
#FFFFFF
on
#EAAC3F
needs 3.0:1 (large text)
19px · bottom of viewport
title Accueil | ENS
1.14:1
#000000
on
#240925
needs 4.5:1 (normal text)
16px · top of page (header area)
span Rechercher
2.63:1
#000000
on
#4D5432
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Communiqués
1.51:1
#000000
on
#292F19
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Recrutement
1.63:1
#000000
on
#30341D
needs 4.5:1 (normal text)
16px · above the fold
a Tous les recrutements
1.30:1
#000000
on
#24201E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

4 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
h2 Rechercher21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Navigation principal…1.58:13.0:1
#000000
#2C321E
Fail
h2 Main and footer menu10.47:13.0:1
#000000
#EAAC3F
Pass
h2 Navigation principal…10.47:13.0:1
#000000
#EAAC3F
Pass
h2 Dernières actualit…10.47:13.0:1
#000000
#EAAC3F
Pass
h2 Cette semaine à l…10.47:13.0:1
#000000
#EAAC3F
Pass
h2 Main and footer menu10.47:13.0:1
#000000
#EAAC3F
Pass
h2 Main and footer menu10.47:13.0:1
#000000
#EAAC3F
Pass
h2 Pied de page10.47:13.0:1
#000000
#EAAC3F
Pass
h2 Le site de l'École …10.47:13.0:1
#000000
#EAAC3F
Pass
h3 Intégrer l'École2.01:13.0:1
#FFFFFF
#EAAC3F
Fail
h3 École normale supé…10.47:13.0:1
#000000
#EAAC3F
Pass
title Accueil | ENS1.14:14.5:1
#000000
#240925
Fail
a Aller au contenu pri…8.03:14.5:1
#000000
#A79DA8
Pass
span toggle menu21.00:14.5:1
#000000
#FFFFFF
Pass
label Rechercher4.53:14.5:1
#000000
#757755
Pass
span Rechercher2.63:14.5:1
#000000
#4D5432
Fail
a Communiqués1.51:14.5:1
#000000
#292F19
Fail
a Recrutement1.63:14.5:1
#000000
#30341D
Fail
a Tous les recrutement…1.30:14.5:1
#000000
#24201E
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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 6 failing, 24 passed
REVIEW
79

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.

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
NOUS SOUTENIR div.region > div.noussoutenir > div.noussoutenir_block > a.noussoutenir_lien
FRIENDS OF ENS div.region > div.noussoutenir > div.noussoutenir_block > a.noussoutenir_lien
S’inscrire à la newsletter div.field > p > a.bouton > 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
Trajectoires div.region > div.home_page > div.hidden_block > h4
Vie des campus ENS div.region > div.home_page > div.hidden_block > h5

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.header_block > a.more_info > div.event_image > img div.header_block > a.more_info > div.event_image > img

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accéder à la fiche du département Centre interdisciplinaire sur les enjeux stra… div.views-element-container > div.js-view-dom-id-f6e0ac072fffab4b4e67b39d0c5795b35f21634d25d9fc5811c6f08aff0c54a9 > div.select > select#departements
Accéder à la fiche du laboratoire Archéologie et Philologie d'Orient et d'Occid… div.views-element-container > div.js-view-dom-id-072a09af1c4d140730268372948988588f50457afe56e90329d9e326b3f2dd45 > div.select > select#laboratoires
Accéder à la bibliothèque La bibliothèque de Mathématiques et Informatique La b… div.views-element-container > div.js-view-dom-id-f198e958921aa74f1c4154736aa19034e87b0230a0cbd5a2b7d1ac7f2c6d2b08 > div.select > select#bibliothèques

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.dialog-off-canvas-main-canvas > div.layout-container > div.left_sidebar > a.twitter-timeline div.dialog-off-canvas-main-canvas > div.layout-container > div.left_sidebar > a.twitter-timeline
div.home_page > div.header_block > div.slider_video > a div.home_page > div.header_block > div.slider_video > a
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--facebook section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--facebook
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--twitter section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--twitter
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--youtube section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--youtube
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--instagram section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--instagram
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--linkedin section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--linkedin
div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-next div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-next
div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-prev div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-prev
div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-next div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-next
div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-prev div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-prev
div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-next div.bx-wrapper > div.bx-controls > div.bx-controls-direction > a.bx-next
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--facebook section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--facebook
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--twitter section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--twitter
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--youtube section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--youtube
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--instagram section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--instagram
section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--linkedin section#block-socialmedialinks > ul.social-media-links--platforms > li > a.social-media-link-icon--linkedin

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
Mentions légales nav#block-pieddepage > ul > li.menu-level--0 > a
Lettre d’information nav#block-pieddepage > ul > li.menu-level--0 > 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-*]` 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 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
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
○`[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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○Tables have different content in the summary attribute and `<caption>`.
○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
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
6 <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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "block-navigationprincipale-menu" SEARCH 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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | ENS ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback