Skip to content
https://rsf.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 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" id="ows-edit-submit">; <input type="submit" name="op" id="edit-submit--2">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="text" id="edit-text">; <input type="email" name="email" id="edit-email--2">
4 controls
0 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#edit-textsearch(Rechercher)placeholder only
#edit-email--2email(Your email address)placeholder only
#ows-edit-submitsubmit(none)none
#edit-submit--2submit(none)none

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

<input type="submit" id="ows-edit-submit">; <input type="submit" name="op" id="edit-submit--2">

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="search" name="text" id="edit-text">; <input type="email" name="email" id="edit-email--2">

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
Valid manifest
FIX
Valid manifest
Info::
Name present: App
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name App 192×192 icon 512×512 icon Start URL Display Mode
Name App Icons 6 icon(s)
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
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
9 headings, 1 skip(s)
REVIEW
9 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
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.
  • H1 (empty)
  • H3 Get informed skipped
  • H3 Know us
  • H3 Get involved
  • H2 Abuses worldwide in real time
  • H2 2025 Press Freedom Index
  • H2 Stay informed
  • H2 Support RSF in its fight
  • H2 Reports

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::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Reporter sans frontières, retour à l'accueil Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
20 icon(s) detected
REVIEW
20 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::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
h3 Get informed
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
19px · top of page (header area)
span Our goal: to leave no breach of freedom …
1.14:1
#000000
on
#141414
needs 4.5:1 (normal text)
16px · above the fold
a Press freedom Index
1.14:1
#000000
on
#141414
needs 4.5:1 (normal text)
16px · above the fold
a Abuses worldwide in real time
1.14:1
#000000
on
#141414
needs 4.5:1 (normal text)
16px · above the fold
span Countries and regions
1.14:1
#000000
on
#141414
needs 4.5:1 (normal text)
16px · above the fold
span AFRICA
1.56:1
#000000
on
#2B2F32
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Angola
1.45:1
#000000
on
#1F2B33
needs 4.5:1 (normal text)
16px · above the fold
a Benin
1.53:1
#000000
on
#2A2E30
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Botswana
2.09:1
#000000
on
#47413C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Burkina Faso
1.32:1
#000000
on
#1F2227
needs 4.5:1 (normal text)
16px · above the fold

3 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 Abuses worldwide in …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 2025 Press Freedom I…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Stay informed21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Support RSF in its f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Reports21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get informed1.14:13.0:1
#000000
#141414
Fail
h3 Know us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get involved21.00:13.0:1
#000000
#FFFFFF
Pass
title Homepage | RSF21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
span Get informed21.00:14.5:1
#000000
#FFFFFF
Pass
span Our goal: to leave n…1.14:14.5:1
#000000
#141414
Fail
a Press freedom Index1.14:14.5:1
#000000
#141414
Fail
a Abuses worldwide in …1.14:14.5:1
#000000
#141414
Fail
span Countries and region…1.14:14.5:1
#000000
#141414
Fail
span AFRICA1.56:14.5:1
#000000
#2B2F32
Fail
a Angola1.45:14.5:1
#000000
#1F2B33
Fail
a Benin1.53:14.5:1
#000000
#2A2E30
Fail
a Botswana2.09:14.5:1
#000000
#47413C
Fail
a Burkina Faso1.32:14.5:1
#000000
#1F2227
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.

A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Navigation principale" SEARCH MAIN CONTENTINFO footer

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

A+
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
24 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
26 images 2 good alt text 24 decorative
All images have appropriate alt text.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_lTmewEKADFLLzV119jek614dNh1V_rSYYeVeFBvK0Mk.css?delta=3&language=en&theme=rsf&include=eJw9yEEOwCAIAMEP2fKkBpWqCVUCePD3tZceNpuMoGJRlGqQdQryKb-cs8uM3KxSDmo3FB4R-TBf3Hr56HJMsNtXJ5ypuY4ebJnTAxGNXlYLJks
Print Stylesheet Print Optimized
Print stylesheet /sites/default/files/css/css_lTmewEKADFLLzV119jek614dNh1V_rSYYeVeFBvK0Mk.css?delta=3&language=en&theme=rsf&include=eJw9yEEOwCAIAMEP2fKkBpWqCVUCePD3tZceNpuMoGJRlGqQdQryKb-cs8uM3KxSDmo3FB4R-TBf3Hr56HJMsNtXJ5ypuY4ebJnTAxGNXlYLJks Inline @media print Not detected
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 29 passed
PASS
93

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

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.main-wrapper > div.mea-wrapper > div.mea-left-wrapper > a.field-group-link div.main-wrapper > div.mea-wrapper > div.mea-left-wrapper > a.field-group-link
article.node > div.node__content > div.wrapper-right > a.field-group-link article.node > div.node__content > div.wrapper-right > a.field-group-link
article.node > div.node__content > div.wrapper-right > a.field-group-link article.node > div.node__content > div.wrapper-right > a.field-group-link
article.node > div.node__content > div.wrapper-right > a.field-group-link article.node > div.node__content > div.wrapper-right > a.field-group-link
article.node > div.node__content > div.wrapper-right > a.field-group-link article.node > div.node__content > div.wrapper-right > a.field-group-link
div.wrapper-articles > article.node > div.node__content > a.field-group-link div.wrapper-articles > article.node > div.node__content > a.field-group-link
div.wrapper-articles > article.node > div.node__content > a.field-group-link div.wrapper-articles > article.node > div.node__content > a.field-group-link
div.wrapper-articles > article.node > div.node__content > a.field-group-link div.wrapper-articles > article.node > div.node__content > a.field-group-link
div > article.node > div.node__content > a.field-group-link div > article.node > div.node__content > a.field-group-link

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
ACTIONS RSF div.node__content > div.wrapper-left > div.wrapper-thematiques > a.link
ACTION IN THE FIELD div.node__content > div.wrapper-left > div.wrapper-thematiques > a.article
NEWS div.node__content > div.wrapper-infos > div.wrapper-thematiques > a.article
VIOLENCE AGAINST JOURNALISTS article.node > div.node__content > div.wrapper-thematiques > a.link
REPORT article.node > div.node__content > div.wrapper-thematiques > a.article

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
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
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
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
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[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 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.
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.

Send Feedback