Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Link & Button Quality

Action

2 issue(s) across 379 links and 66 buttons

FIX

2 issue(s) across 379 links and 66 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

6 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/fr/soutenez-la-bnf"]; a[href="https://x.com/laBnF"]; a[href="https://www.facebook.com/bibliothequebnf"]; a[href="https://www.instagram.com/labnf/"]; a[href="https://www.youtube.com/user/BibliothequeBnF"]; a[href="/fr/handicap-auditif-le-service-de-communication-acceo"]

12 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://espacepersonnel.bnf.fr/; https://inscriptionbilletterie.bnf.fr/; /fr/agenda/cartes-imaginaires; /fr/agenda/cartes-imaginaires; /fr/agenda/cartes-imaginaires; /fr/les-lettres-dinformation-de-la-bnf; https://catalogue.bnf.fr/; https://ccfr.bnf.fr/; https://data.bnf.fr/; https://gallica.bnf.fr/ (+2 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.btn-no-style (#41 on page)

360 link(s) with descriptive text

379 links

1 empty

0 generic text

12 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://espacepersonnel.bnf.fr/	Mon espace (nouvelle fenêtre)	new tab	Add '(opens in new tab)' to text
https://inscriptionbilletterie.bnf.fr/	Inscription / Billetterie (nou…	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
/fr/agenda/cartes-imaginaires	Cartes imaginaires. Inventer d…	new tab	Add '(opens in new tab)' to text
/fr/agenda/cartes-imaginaires	Cartes imaginaires. Inventer d…	new tab	Add '(opens in new tab)' to text
/fr/agenda/cartes-imaginaires	En savoir plus - Cartes imagin…	new tab	Add '(opens in new tab)' to text
/fr/soutenez-la-bnf	Soutenez la BnF	img no alt	Add alt attribute to the image
https://x.com/laBnF	Twitter (nouvelle fenêtre)	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/bibliothequebnf	Facebook (nouvelle fenêtre)	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/labnf/	Instagram (nouvelle fenêtre)	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/Bibliothequ…	YouTube (nouvelle fenêtre)	new tab	Add '(opens in new tab)' to text
/fr/les-lettres-dinformation-de-la-bnf	Inscription newsletter (nouvel…	new tab	Add '(opens in new tab)' to text
/fr/handicap-auditif-le-service-de-commu…	Service Acceo	img no alt	Add alt attribute to the image
https://catalogue.bnf.fr/	Catalogue général …	new tab	Add '(opens in new tab)' to text
https://ccfr.bnf.fr/	CCFr …	new tab	Add '(opens in new tab)' to text
https://data.bnf.fr/	Data …	new tab	Add '(opens in new tab)' to text
https://gallica.bnf.fr/	Gallica …	new tab	Add '(opens in new tab)' to text
https://archivesetmanuscrits.bnf.fr/	Archives et manuscrits …	new tab	Add '(opens in new tab)' to text
https://medaillesetantiques.bnf.fr	Médailles et antiques …	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

425 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/fr/soutenez-la-bnf"]; a[href="https://x.com/laBnF"]; a[href="https://www.facebook.com/bibliothequebnf"]; a[href="https://www.instagram.com/labnf/"]; a[href="https://www.youtube.com/user/BibliothequeBnF"]; a[href="/fr/handicap-auditif-le-service-de-communication-acceo"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://espacepersonnel.bnf.fr/; https://inscriptionbilletterie.bnf.fr/; /fr/agenda/cartes-imaginaires; /fr/agenda/cartes-imaginaires; /fr/agenda/cartes-imaginaires; /fr/les-lettres-dinformation-de-la-bnf; https://catalogue.bnf.fr/; https://ccfr.bnf.fr/; https://data.bnf.fr/; https://gallica.bnf.fr/ (+2 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.btn-no-style (#41 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Search functionality detected

Got: role-search

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link

Labeled Navigation 5 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Landmark Structure

10 landmarks

REVIEW

10 landmarks

<main> landmark present

5 <nav> landmark(s) found

2 of 5 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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.

Search landmark present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Heading Hierarchy

21 headings, 1 skip(s)

REVIEW

21 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

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

H1 En ce moment à la BnF
H2 (empty)
H3 Cartes imaginaires. Inventer des mondes
H2 La BnF et moi
H3 Le Pass BnF lecture/culture dès 14 ans
H3 Une question ? Pensez à SINDBAD !
H3 La salle Ovale
H2 Les brèves de la BnF
H2 LES COULISSES DE LA BnF
H5 Rapport d'activité 2024 skipped
H3 Gallica et les Carnets de tatouages d’Alexandre Lacassagne
H3 Les achats publics responsables à la BnF : un cadre juridique approuvé et un plan d'actions en 2026
H3 Relecture(s) de Joséphin Péladan
H3 Des écrivains géographes ?
H2 Vous pouvez également effectuer vos recherches sur les bases de données et les catalogues de la BnF
H3 Catalogue général
H3 CCFr
H3 Data
H3 Gallica
H3 Archives et manuscrits
H3 Médailles et antiques

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 - Page non trouvée | BnF - Site institutionnel ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

A+

Alt Text Quality

All 27 images OK

PASS

All 27 images OK

12 decorative image(s) correctly marked

15 image(s) with good alt text

27 images 15 good alt text 12 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-keyword	text	Recherche	aria-label

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)

Element	Ratio	Required	FG	BG	Result
h1 En ce moment à la B…	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h2 La BnF et moi	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h2 Les brèves de la Bn…	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h2 LES COULISSES DE LA …	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h2 Vous pouvez égaleme…	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h3 Catalogue général	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h3 CCFr	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h3 Data	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h3 Gallica	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h3 Archives et manuscri…	15.61:1	3.0:1	#000000	#DEDEDE	Pass
h3 Médailles et antiqu…	15.61:1	3.0:1	#000000	#DEDEDE	Pass
title Accueil \| BnF – Si…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Aller au contenu pri…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Mon espace	20.65:1	4.5:1	#000000	#FDFDFD	Pass
span Horaires / Accès	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Agenda	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Catalogues	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Inscription / Bille…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Fermer le menu	13.36:1	4.5:1	#000000	#DBCDAF	Pass
button Venir	14.41:1	4.5:1	#000000	#E4D4B8	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+

Lighthouse Accessibility Audits

Score 95/100 — 3 failing, 26 passed

PASS

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
EXPOSITION `div.accueil-article-main-container > div.article-text > div.center > div.article-sub-text`
Jusqu'au 19 juillet 2026 \| François-Mitterrand `div.accueil-article-main-container > div.article-text > div.center > div.article-dates`
Du mardi au dimanche \| Richelieu `div.row > div.article-text > div.center > div.article-dates`
EXPOSITION `div.row > div.article-text > div.center > div.article-sub-text`
Jusqu'au 4 juillet 2026 \| Arsenal `div.row > div.article-text > div.center > div.article-dates`
BRÈVES DE LA BNF `div.view-content > div.bnf-item-header > div.bnf-item-title > span`
21 avr. 2026 `div.view-content > div.bnf-item-header > div.bnf-item-date > time`
BRÈVES DE LA BNF `div.view-content > div.bnf-item-header > div.bnf-item-title > span`
20 avr. 2026 `div.view-content > div.bnf-item-header > div.bnf-item-date > time`
BRÈVES DE LA BNF `div.view-content > div.bnf-item-header > div.bnf-item-title > span`
20 avr. 2026 `div.view-content > div.bnf-item-header > div.bnf-item-date > time`
PUBLICATION `div.col-xs-12 > div.bnf-item-content > div.center > p.zoom-sur`
ACTUALITÉS PROFESSIONNELLES `div.views-element-container > div.view > div.view-content > div.taxo-coulisses`
20 avr. 2026 `div.view > div.view-content > article.padding-actu-coulisse > div.date`
25 mar. 2026 `div.view > div.view-content > article.padding-actu-coulisse > div.date`
COLLOQUES `div.views-element-container > div.view > div.view-content > div.taxo-coulisses`

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
Rapport d'activité 2024 `div.col-xs-12 > div.bnf-item-content > div.center > h5.title`

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
INSCRIVEZ-VOUS AUX LETTRES D’INFORMATIONS `div#block-contactnewsletter > div.field > div.links-group > a.btn`

○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

●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.

●ARIA attributes are used as specified for the element's role

●`[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

●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.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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

○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.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○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.

○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.