Skip to content
https://www.msn.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) MAIN (missing!) CONTENTINFO (missing!)

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

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
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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
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::
Hamburger menu detected (responsive design)
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
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
29 headings
REVIEW
29 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Microsoft se soucie de votre vie privée
  • H3 Nos équipes ainsi que nos partenaires externes, traitent des données selon les finalités suivantes :
  • H2 En savoir plus sur la protection de vos données
  • H3 Gérer les préférences de consentement
  • H4 Cookies strictement nécessaires
  • H4 Cookies de réseaux sociaux
  • H4 Cookies publicitaires
  • H4 Analyses de tiers
  • H4 Stocker et/ou accéder à des informations sur un appareil Il peut y avoir 760 fournisseurs qui utilisent cette finalité.
  • H4 Publicités et contenu personnalisés, mesure de performance des publicités et du contenu, études d’audience et développement de services Il peut y avoir 909 fournisseurs qui utilisent cette fina
  • H5 Utiliser des données limitées pour sélectionner la publicité Il peut y avoir 718 fournisseurs qui utilisent cette finalité.
  • H5 Créer des profils pour la publicité personnalisée Il peut y avoir 583 fournisseurs qui utilisent cette finalité.
  • H5 Utiliser des profils pour sélectionner des publicités personnalisées Il peut y avoir 584 fournisseurs qui utilisent cette finalité.
  • H5 Créer des profils de contenus personnalisés Il peut y avoir 260 fournisseurs qui utilisent cette finalité.
  • H5 Utiliser des profils pour sélectionner des contenus personnalisés Il peut y avoir 232 fournisseurs qui utilisent cette finalité.
  • H5 Mesurer la performance des publicités Il peut y avoir 829 fournisseurs qui utilisent cette finalité.
  • H5 Mesurer la performance des contenus Il peut y avoir 395 fournisseurs qui utilisent cette finalité.
  • H5 Comprendre les publics par le biais de statistiques ou de combinaisons de données provenant de différentes sources Il peut y avoir 536 fournisseurs qui utilisent cette finalité.
  • H5 Développer et améliorer les services Il peut y avoir 619 fournisseurs qui utilisent cette finalité.
  • H5 Utiliser des données limitées pour sélectionner le contenu Il peut y avoir 170 fournisseurs qui utilisent cette finalité.
  • H4 Utiliser des données de géolocalisation précises 273 partenaires peuvent utiliser cette fonctionnalité particulière
  • H4 Analyser activement les caractéristiques de l’appareil pour l’identification 155 partenaires peuvent utiliser cette fonctionnalité particulière
  • H4 Assurer la sécurité, prévenir et détecter la fraude et réparer les erreurs 583 partenaires peuvent utiliser cette finalité particulière
  • H4 Fournir et présenter des publicités et du contenu 581 partenaires peuvent utiliser cette finalité particulière
  • H4 Mettre en correspondance et combiner des données à partir d’autres sources de données 429 partenaires peuvent utiliser cette fonctionnalité
  • H4 Relier différents appareils 362 partenaires peuvent utiliser cette fonctionnalité
  • H4 Identifier les appareils en fonction des informations transmises automatiquement 546 partenaires peuvent utiliser cette fonctionnalité
  • H4 Enregistrer et communiquer les choix en matière de confidentialité 435 partenaires peuvent utiliser cette finalité particulière
  • H3 Liste des cookies

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

B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Microsoft se soucie …4.96:13.0:1
#000000
#7B7B7B
Pass
h2 En savoir plus sur l…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nos équipes ainsi q…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gérer les préfére…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Liste des cookies21.00:13.0:1
#000000
#FFFFFF
Pass
title MSN | Actualités pe…4.96:14.5:1
#000000
#7B7B7B
Pass
div Microsoft et nos fou…4.82:14.5:1
#000000
#797979
Pass
a Déclaration de conf…21.00:14.5:1
#000000
#FFFFFF
Pass
div Nombre de partenaire…21.00:14.5:1
#000000
#FFFFFF
Pass
span 94121.00:14.5:1
#000000
#FFFFFF
Pass
p Utiliser des donnée…21.00:14.5:1
#000000
#FFFFFF
Pass
button Liste de nos partena…21.00:14.5:1
#000000
#FFFFFF
Pass
button J'accepte21.00:14.5:1
#000000
#FFFFFF
Pass
button Tout refuser21.00:14.5:1
#000000
#FFFFFF
Pass
button Gérer les préfére…21.00:14.5:1
#000000
#FFFFFF
Pass
div Nous traitons vos do…21.00:14.5:1
#000000
#FFFFFF
Pass
a Plus d’information…21.00:14.5:1
#000000
#FFFFFF
Pass
button Tout autoriser21.00:14.5:1
#000000
#FFFFFF
Pass
h4 Cookies strictement …21.00:13.0:1
#000000
#FFFFFF
Pass
div Toujours actif21.00:14.5:1
#000000
#FFFFFF
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+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 22 controls labeled
PASS
All 22 controls labeled
Info::
22 control(s) properly labeled
22 controls
22 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0003checkboxCookies de réseaux sociauxfor/id
#ot-group-id-C0002checkboxCookies publicitairesfor/id
#ot-group-id-C0004checkboxAnalyses de tiersfor/id
#ot-group-id-IAB2V2_1checkboxStocker et/ou accéder à des informations sur un appareilfor/id
#ot-group-id-V2STACK42checkboxPublicités et contenu personnalisés, mesure de performance des publicités et du contenu, études d’audience et développement de servicesfor/id
#ot-sub-group-id-IAB2V2_2checkboxUtiliser des données limitées pour sélectionner la publicitéaria-label
#ot-sub-group-id-IAB2V2_3checkboxCréer des profils pour la publicité personnaliséearia-label
#ot-sub-group-id-IAB2V2_4checkboxUtiliser des profils pour sélectionner des publicités personnaliséesaria-label
#ot-sub-group-id-IAB2V2_5checkboxCréer des profils de contenus personnalisésaria-label
#ot-sub-group-id-IAB2V2_6checkboxUtiliser des profils pour sélectionner des contenus personnalisésaria-label
#ot-sub-group-id-IAB2V2_7checkboxMesurer la performance des publicitésaria-label
#ot-sub-group-id-IAB2V2_8checkboxMesurer la performance des contenusaria-label
#ot-sub-group-id-IAB2V2_9checkboxComprendre les publics par le biais de statistiques ou de combinaisons de données provenant de différentes sourcesaria-label
#ot-sub-group-id-IAB2V2_10checkboxDévelopper et améliorer les servicesaria-label
#ot-sub-group-id-IAB2V2_11checkboxUtiliser des données limitées pour sélectionner le contenuaria-label
#ot-group-id-ISF2V2_1checkboxUtiliser des données de géolocalisation précisesfor/id
#ot-group-id-ISF2V2_2checkboxAnalyser activement les caractéristiques de l’appareil pour l’identificationfor/id
#vendor-search-handlertextRecherche dans la liste des cookiesaria-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
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 MSN ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 26 passed
PASS
91

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
Annonce div.feed-inner-container > div.feed-ads-wrapper > div.display-ads-container > span.ad-placeholder-text
Sponsorisé div#nativead-infopane-3 > div.footer > a.ad-slug
Sponsorisé div.footer > a.ad-slug

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○`[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.
○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