Skip to content
https://sharepoint.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
1
PASS
6
INFO
0
Checks
13
6 PASS 1 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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::
5 navigation landmark(s) detected
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 5 <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
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

A
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Contextmenu" MAIN CONTENTINFO footer

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

A
Heading Hierarchy
73 headings
PASS
73 headings
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Global
  • H1 Microsoft SharePoint
  • H2 Werk samen, synchroniseer en deel inhoud, veilig
  • H3 Work IQ
  • H3 Intelligent zoeken
  • H3 Pas agents aan
  • H3 AI-gerede inhoud
  • H3 De inhoud blijft actueel
  • H3 AI-werkstromen
  • H3 AI in SharePoint
  • H3 Eenvoudig pagina-ontwerp
  • H3 Copilot Studio voeden
  • H3 Agent voor SharePoint-beheer
  • H3 SharePoint geavanceerd beheer
  • H3 Microsoft 365-back-up
  • H3 Microsoft 365-archief
  • H2 Eén SharePoint-ervaring
  • H3 Ontwikkel de merkgebonden hub van jouw organisatie
  • H3 Maak het één keer, bereik iedereen overal en meet wat echt telt
  • H3 Ontwikkel slimme oplossingen met AI en automatisering
  • H3 Blijf verbonden met de AI die precies toont wat voor jou belangrijk is
  • H2 Vereenvoudig processen in je hele bedrijf
  • H3 Microsoft 365 Copilot
  • H3 Agents in SharePoint
  • H3 Geavanceerd beheer
  • H2 Zet kennis om in actie op schaal
  • H2 (empty)
  • H2 Ontwerpen. Maken. Leveren.
  • H3 Ondersteuning bij het creëren
  • H3 Ontwerpideeën
  • H3 Flexibele lay-outs
  • H3 Geschaalde eenvoud
  • H3 Meeslepende inhoud
  • H3 Kant-en-klare agents
  • H2 Vergelijk SharePoint Online-opties
  • H1 Microsoft 365 Business Standard duplicate H1
  • H1 Microsoft 365 Business Premium duplicate H1
  • H1 SharePoint (Plan 1) duplicate H1
  • H1 Microsoft 365 Business Standard EEA (zonder Teams) duplicate H1
  • H1 Microsoft 365 Business Premium EEA (zonder Teams) duplicate H1
  • H2 Blijf verbonden met onze nieuwste evenementen en leer, verken en innoveer
  • H3 SharePoint is 25: het kennisplatform voor Copilot en agents
  • H3 SharePoint Showcase: maandelijkse inzichten, tips en praktijkverhalen voor het AI-tijdperk
  • H2 Gebruikt door miljoenen wereldwijd
  • H2 Ontdek meer over SharePoint
  • H3 Versterk zorgteams met veilig documentbeheer en AI-gedreven inzichten in de Gezond­heids­zorg
  • H3 Versterk financiële diensten met veilige, AI-gestuurde inhoudssamenwerking
  • H3 Belangrijke punten van ESPC
  • H3 Belangrijke punten van Ignite
  • H3 AI-innovaties in SharePoint en OneDrive
  • H3 Best practices voor gegevensherstel en bedrijfscontinuïteit
  • H3 Neem deel aan ons tweewekelijkse gesprek en hoor het laatste nieuws van het SharePoint-team
  • H3 Dé plek voor SharePoint-nieuws, aankondigingen en best practices
  • H3 Vind trainingsmodules, leertrajecten en cursussen over SharePoint
  • H2 Meer informatie over Microsoft 365-producten
  • H3 Maak indrukwekkende documenten en verbeter je schrijfvaardigheid met ingebouwde intelligente functies.
  • H3 Maak goed ontworpen, impactvolle presentaties met gebruik van intelligente ontwerphulpprogramma's en -functies.
  • H3 Maak en bewerk snel en eenvoudig prachtige video's.
  • H3 Bewaar, open, bewerk en deel bestanden en foto's, waar je ook bent.
  • H3 Beheer je e-mail, agenda, taken en contactpersonen op één locatie.
  • H3 Breng iedereen op één plek samen om te vergaderen, te chatten, te bellen en samen te werken.
  • H3 Vereenvoudig complexe gegevens en maak boeiende spreadsheets met opmaak, sparklines en tabellen.
  • H3 Profiteer van bescherming van persoonlijke apparaten en gegevens met één gemakkelijk te gebruiken app.
  • H2 Veelgestelde vragen
  • H3 Wat is SharePoint?
  • H3 Hoe gaat SharePoint om met beveiliging en machtigingen?
  • H3 Hoe kan ik SharePoint aanpassen?
  • H3 Hoe is Microsoft Copilot geïntegreerd in SharePoint?
  • H2 Voeg Copilot toe aan je Microsoft-plan
  • H3 Microsoft 365
  • H3 Microsoft OneDrive
  • H3 Microsoft 365-back-up
  • H2 Microsoft 365 volgen

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

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

A+
Alt Text Quality
All 130 images OK
PASS
All 130 images OK
Info::
39 decorative image(s) correctly marked
Info::
91 image(s) with good alt text
130 images 91 good alt text 39 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cli_shellHeaderSearchInputsearchZoeken uitgevouwenaria-label
#x5f88c43e04a846b9a133111371502400selectChoose your billing country/region:for/id
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
h1 Microsoft SharePoint20.70:13.0:1
#000000
#FFFDFB
Pass
h1 Microsoft 365 Busine…20.70:13.0:1
#000000
#FFFDFB
Pass
h1 Microsoft 365 Busine…20.70:13.0:1
#000000
#FFFDFB
Pass
h1 SharePoint (Plan 1)20.70:13.0:1
#000000
#FFFDFB
Pass
h1 Microsoft 365 Busine…20.70:13.0:1
#000000
#FFFDFB
Pass
h1 Microsoft 365 Busine…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Global20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Werk samen, synchron…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Eén SharePoint-erva…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Vereenvoudig process…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Zet kennis om in act…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Ontwerpen. Maken. Le…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Vergelijk SharePoint…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Blijf verbonden met …20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Gebruikt door miljoe…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Ontdek meer over Sha…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Meer informatie over…20.70:13.0:1
#000000
#FFFDFB
Pass
h2 Microsoft 365 volgen20.70:13.0:1
#000000
#FFFDFB
Pass
h3 SharePoint is 25: he…20.70:13.0:1
#000000
#FFFDFB
Pass
h3 SharePoint Showcase:…20.70:13.0:1
#000000
#FFFDFB
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 97/100 — 2 failing, 30 passed
PASS
97

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.

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
Overslaan naar hoofdinhoud div#headerArea > div#headerRegion > div#headerUniversalHeader > a#uhfSkipToMain
Microsoft header.c-uhfh > div.theme-light > div.c-uhfh-gcontainer-st > a#uhfLogo
Microsoft 365 div.theme-light > div.c-uhfh-gcontainer-st > div.cat-logo-button-cont > button#uhfCatLogoButton
Zoeken in Microsoft 365 div.c-uhfh-gcontainer-st > div.c-uhfh-actions > form#searchForm > button#search

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
Beheercentrum div.block-heading > div.block-heading__button-group > div.button-group > a#action-ocfca5
Bekijk alles div.layout__col > div.section-master__layout-slot > div.action > a#action-oc5226
Lees meer over het opzeggen van je Microsoft 365-abonnement div.footnote-item > div.footnote__item > div.footnote__item-text > a.ms-rte-link
Meer informatie over gegevensretentie, -verwijdering en -vernietiging in Micros… div.footnote-item > div.footnote__item > div.footnote__item-text > a.ms-rte-link
○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
●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
●`[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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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.
●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
●Touch targets have sufficient size and spacing.
●`[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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○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>`.
○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