Skip to content
https://openstreetmap.fr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Form Accessibility
Action
4 of 4 controls have issues
FIX
4 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit" id="search-submit">; <input type="submit" name="submit" id="search-submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="s">
4 controls
0 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
stext(Recherche)placeholder only
stext(Recherche)placeholder only
#search-submitsubmit(none)none
#search-submitsubmit(none)none

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

<input type="submit" name="submit" id="search-submit">; <input type="submit" name="submit" id="search-submit">

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

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

<input type="text" name="s">; <input type="text" name="s">

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

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::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Landmark Structure
Action
9 landmarks
REVIEW
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Heading Hierarchy
19 headings, 1 skip(s)
REVIEW
19 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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 OpenStreetMap France
  • H3 Menu skipped
  • H2 La rencontre mondiale OpenStreetMapen France pour la première fois !
  • H1 28 ➔ 30 août 2026 à Paris duplicate H1
  • H2 Participatif
  • H2 Mondial
  • H2 Libre
  • H2 Des données
  • H2 Des cartes
  • H2 Utilisez-les !
  • H2 Soutenez nos actions
  • H3 Devenez membre de l'association.
  • H3 Faites un don ponctuel ou régulier.
  • H2 La communauté OpenStreetMap en France
  • H2 Ils nous soutiennent !
  • H2 Nous sommes membre !
  • H3 Actualités
  • H3 <img class="rss-widget-icon" style="border:0" width="14" height="14" src="https://www.openstreetmap.fr/wp-includes/images/rss.png" alt="Flux" /> Événements à venir
  • H3 <img class="rss-widget-icon" style="border:0" width="14" height="14" src="https://www.openstreetmap.fr/wp-includes/images/rss.png" alt="Flux" /> Mastodon

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

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page non trouvée - OpenStreetMap France ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
B
Lighthouse Accessibility Audits
Score 82/100 — 6 failing, 21 passed
REVIEW
82

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
La carte coopérative libre div#header-text-nav-wrap > div#header-left-section > div#header-text > p#site-description
div#header-right-sidebar > aside#search-3 > form#search-form > input#search-submit div#header-right-sidebar > aside#search-3 > form#search-form > input#search-submit
Plus d'infos section#block-53 > blockquote.wp-block-quote > p.has-text-align-center > a
Voir la carte div.textwidget > p > strong > a
Lire la suite section#accelerate_image_service_widget-3 > div.tg-one-third > a.more-link > span
Lire la suite section#accelerate_image_service_widget-3 > div.tg-one-third > a.more-link > span
Lire la suite section#accelerate_image_service_widget-3 > div.tg-one-third > a.more-link > span
Lire la suite section#accelerate_image_service_widget-5 > div.tg-one-third > a.more-link > span
Lire la suite section#accelerate_image_service_widget-5 > div.tg-one-third > a.more-link > span
Lire la suite section#accelerate_image_service_widget-5 > div.tg-one-third > a.more-link > span
Adhérer div.wp-block-column > div.widget > div.call-to-action-content-wrapper > a.read-more
Donner div.wp-block-column > div.widget > div.call-to-action-content-wrapper > a.read-more
Contributeurs OpenStreetMap div#content > section#block-42 > p.has-text-align-center > a
div.tg-one-third > aside#search-5 > form#search-form > input#search-submit div.tg-one-third > aside#search-5 > form#search-form > input#search-submit

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#custom_html-5 > div.textwidget > center > iframe.iframe_map section#custom_html-5 > div.textwidget > center > iframe.iframe_map

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.wp-block-column > div.wp-block-image > figure.aligncenter > a div.wp-block-column > div.wp-block-image > figure.aligncenter > a
section#block-44 > div.wp-block-image > figure.aligncenter > a section#block-44 > div.wp-block-image > figure.aligncenter > 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.

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
Menu header#masthead > div#header-text-nav-container > nav#site-navigation > h3.menu-toggle

These are opportunities to improve keyboard navigation in your application.

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 div.menu-bas-de-page-container > ul#menu-bas-de-page > li#menu-item-384 > a
Donner div.menu-bas-de-page-container > ul#menu-bas-de-page > li#menu-item-3469 > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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 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
●Skip links are focusable.
●Deprecated ARIA roles were not used
●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-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
○Buttons have an accessible name
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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.
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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.
A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
4 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
16 images 12 good alt text 4 decorative
All images have appropriate alt text.
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 La rencontre mondial…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 en France pour la pr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Soutenez nos actions21.00:13.0:1
#000000
#FFFFFF
Pass
h2 La communauté OpenS…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ils nous soutiennent…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nous sommes membre !21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Menu19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Devenez membre de l'…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Faites un don ponctu…21.00:13.0:1
#000000
#FFFFFF
Pass
title Accueil - OpenStreet…19.77:14.5:1
#000000
#F8F8F8
Pass
a Skip to content19.77:14.5:1
#000000
#F8F8F8
Pass
a OpenStreetMap France19.77:14.5:1
#000000
#F8F8F8
Pass
p La carte coopérativ…19.77:14.5:1
#000000
#F8F8F8
Pass
a Accueil19.77:14.5:1
#000000
#F8F8F8
Pass
a Utiliser19.77:14.5:1
#000000
#F8F8F8
Pass
a Contribuer19.77:14.5:1
#000000
#F8F8F8
Pass
a Se rencontrer19.77:14.5:1
#000000
#F8F8F8
Pass
a Se former19.77:14.5:1
#000000
#F8F8F8
Pass
a Actualités19.77:14.5:1
#000000
#F8F8F8
Pass
a L’association19.77:14.5:1
#000000
#F8F8F8
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