Skip to content
https://viadeo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
11 landmarks
FIX
11 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.
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 MAIN (missing!) 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

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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::
2 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 2 <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
Heading Hierarchy
3 headings
REVIEW
3 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Connexion
  • H2 Inscription gratuite
  • H2 Annuaire des membres

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

C
Form Accessibility
Action
6 of 21 controls have issues
REVIEW
6 of 21 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="login">; <select name="jourDeNaissance" id="jourDeNaissance">; <select name="moisDeNaissance" id="moisDeNaissance">; <select name="anneeDeNaissance" id="anneeDeNaissance">; <input type="submit" id="btnSubmit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">
Info::
15 control(s) properly labeled
21 controls
15 labeled
0 placeholder only
6 unlabeled
ControlTypeLabelMethod
#txtMailtextEmailnone
#pwdPassAuthpasswordMot de passenone
#txtCivilite1radionone
#txtCivilite3radionone
#txtCivilite2radionone
#txtNomtextNom d'usage*none
#txtPrenomtextPrénom*none
#txtNomDeJeuneFilletextNom de naissancenone
#idPaysselectPaysnone
#txtVilletextVille*none
#txtEmailemailVotre mail*none
#pwdPasspasswordMot de passe*none
#pwdPassConfpasswordre-saisissez votre mot de passe*none
#flagAccepteMessagePartenairecheckboxOffres partenairesnone
#viadeoNewsletterscheckboxNewslettersnone
#moisDeNaissanceselect(none)none
#anneeDeNaissanceselect(none)none
loginsubmit(none)none
#jourDeNaissanceselect(none)none
#btnSubmitsubmit(none)none
#g-recaptcha-responsetextarea(none)none

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

<input type="submit" name="login">; <select name="jourDeNaissance" id="jourDeNaissance">; <select name="moisDeNaissance" id="moisDeNaissance">; <select name="anneeDeNaissance" id="anneeDeNaissance">; <input type="submit" id="btnSubmit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">

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

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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 81/100 — 6 failing, 22 passed
REVIEW
81

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
(Mot de passe oublié ?) label.grid_line > div.grid_last > div.ccmcss_form__msg > a.a_hover
form > fieldset > footer > input form > fieldset > footer > input
Conditions générales form#frmAccount > fieldset > p.ccmcss_form__cgu > a.a_hover
form#frmAccount > fieldset > footer.ccmcss_form__line--no_col > input#btnSubmit form#frmAccount > fieldset > footer.ccmcss_form__line--no_col > input#btnSubmit
à tout moment form#frmAccount > fieldset > p.ccmcss_form__cgu > a
politique de confidentialité form#frmAccount > fieldset > p.ccmcss_form__cgu > a
politique Cookies form#frmAccount > fieldset > p.ccmcss_form__cgu > a
votre numéro de mobile vous sera demandé form#frmAccount > fieldset > p.ccmcss_form__cgu > a.ccmcss_ft_bold

These are opportunities to improve the legibility of your content.

Names and labels

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
- - 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 … div#divDateNaissance > div.grid_last > span.ccmcss_form__select_wrapper > select#jourDeNaissance
- - janvier février mars avril mai juin juillet août septembre octobre novembre… div#divDateNaissance > div.grid_last > span.ccmcss_form__select_wrapper > select#moisDeNaissance
- - 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 … div#divDateNaissance > div.grid_last > span.ccmcss_form__select_wrapper > select#anneeDeNaissance

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.ccmcss_rwd_header__top > div > div.app_header_log__connected--menu > a.login div.ccmcss_rwd_header__top > div > div.app_header_log__connected--menu > a.login
header#jHeader2016 > div.ccmcss_rwd_header__top > div > a.ccmcss_rwd_header__search header#jHeader2016 > div.ccmcss_rwd_header__top > div > a.ccmcss_rwd_header__search
div.layout--flexbox > footer.cp_footer > div.cp_footer__logo > a div.layout--flexbox > footer.cp_footer > div.cp_footer__logo > 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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
fieldset > label.grid_line > div.grid_last > input#txtMail fieldset > label.grid_line > div.grid_last > input#txtMail
fieldset > label.grid_line > div.grid_last > input#pwdPassAuth fieldset > label.grid_line > div.grid_last > input#pwdPassAuth
(Mot de passe oublié ?) label.grid_line > div.grid_last > div.ccmcss_form__msg > a.a_hover
form > fieldset > footer > input form > fieldset > footer > input

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
a div.app_abcdaire > ul > li > a
b div.app_abcdaire > ul > li > a
c div.app_abcdaire > ul > li > a
d div.app_abcdaire > ul > li > a
e div.app_abcdaire > ul > li > a
f div.app_abcdaire > ul > li > a
g div.app_abcdaire > ul > li > a
h div.app_abcdaire > ul > li > a
i div.app_abcdaire > ul > li > a
j div.app_abcdaire > ul > li > a
k div.app_abcdaire > ul > li > a
l div.app_abcdaire > ul > li > a
m div.app_abcdaire > ul > li > a
n div.app_abcdaire > ul > li > a
o div.app_abcdaire > ul > li > a
p div.app_abcdaire > ul > li > a
q div.app_abcdaire > ul > li > a
r div.app_abcdaire > ul > li > a
s div.app_abcdaire > ul > li > a
t div.app_abcdaire > ul > li > a
u div.app_abcdaire > ul > li > a
v div.app_abcdaire > ul > li > a
w div.app_abcdaire > ul > li > a
x div.app_abcdaire > ul > li > a
y div.app_abcdaire > ul > li > a
z div.app_abcdaire > ul > li > a
Qui sommes nous div#footer_internal_links_viadeo > ul > li > a
Contact div#footer_internal_links_viadeo > ul > li > a
Publicité div#footer_internal_links_viadeo > ul > li > a
Recrutement div#footer_internal_links_viadeo > ul > li > a
Societé div#footer_internal_links_viadeo > ul > li > a
Données personnelles div#footer_internal_links_viadeo > ul > li > a
Mentions légales div#footer_internal_links_viadeo > ul > li > a
Tous les articles div#footer_internal_links_viadeo > ul > li > a
Corrections div#footer_internal_links_viadeo > ul > li > a
© 2022 CCM Benchmark div#footer_internal_links_viadeo > ul > li > 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.js html.js

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
●`[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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Deprecated ARIA roles were not used
○`[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
○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
○`<frame>` or `<iframe>` elements have a title
○`<input type="image">` elements have `[alt]` text
○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
○`<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.
○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+
Alt Text Quality
1 of 4 images have issues
PASS
1 of 4 images have issues
Warning::
1 image(s) with generic alt text
Info::
3 image(s) with good alt text
4 images 3 good alt text 1 generic
IssueCount
generic1 image(s)
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 Connexion16.17:13.0:1
#000000
#E0E2E4
Pass
h2 Inscription gratuite16.17:13.0:1
#000000
#E0E2E4
Pass
h2 Annuaire des membres16.17:13.0:1
#000000
#E0E2E4
Pass
title Viadeo : networking,…21.00:14.5:1
#000000
#FFFFFF
Pass
a IA News17.90:14.5:1
#000000
#ECEDED
Pass
a Tech16.17:14.5:1
#000000
#E0E2E4
Pass
a Media / Adtech16.17:14.5:1
#000000
#E0E2E4
Pass
a Start-up16.17:14.5:1
#000000
#E0E2E4
Pass
a Cybersécurité16.17:14.5:1
#000000
#E0E2E4
Pass
a Robotique16.17:14.5:1
#000000
#E0E2E4
Pass
a Cloud16.17:14.5:1
#000000
#E0E2E4
Pass
a Economie16.17:14.5:1
#000000
#E0E2E4
Pass
a IA News16.17:14.5:1
#000000
#E0E2E4
Pass
a Tech16.17:14.5:1
#000000
#E0E2E4
Pass
a Media / Adtech16.17:14.5:1
#000000
#E0E2E4
Pass
a Start-up16.17:14.5:1
#000000
#E0E2E4
Pass
a Cybersécurité16.17:14.5:1
#000000
#E0E2E4
Pass
a Robotique16.17:14.5:1
#000000
#E0E2E4
Pass
a Cloud16.17:14.5:1
#000000
#E0E2E4
Pass
a Economie16.17:14.5:1
#000000
#E0E2E4
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