Skip to content
https://office365.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
D
Heading Hierarchy
Action
57 headings, 3 skip(s)
FIX
57 headings, 3 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Global
  • H1 Sua produtividade turbinada
  • H2 Aumente sua produtividade com o Copilot
  • H3 Pesquise com facilidade
  • H3 Planeje com precisão
  • H3 Crie com confiança
  • H3 Proteja o que é importante
  • H2 Descubra o que está acontecendo com o Microsoft 365
  • H4 O Microsoft 365 Premium e os novos recursos avançados do Copilot já estão disponíveis skipped
  • H4 Seu assistente de IA. Desenvolvido para o trabalho.
  • H2 Tudo do Microsoft 365 em um só plano
  • H3 Aplicativos para gerenciar seu dia a dia
  • H4 Potencialize suas habilidades com o Copilot
  • H4 Word
  • H4 Excel
  • H4 PowerPoint
  • H4 Outlook
  • H4 OneDrive
  • H4 Microsoft Defender
  • H4 Microsoft Teams
  • H4 Designer
  • H3 Aplicativos para gerenciar seu dia a dia
  • H4 Aplicativo Microsoft 365 Copilot
  • H4 OneNote
  • H4 Clipchamp
  • H4 Editor Microsoft
  • H2 Encontre o plano ideal para você
  • H3 Microsoft 365
  • H1 Microsoft 365 Básico duplicate H1
  • H4 O Microsoft 365 Básico inclui: skipped
  • H3 Microsoft 365 Personal
  • H4 Tudo do Básico e mais:
  • H1 Microsoft 365 Family duplicate H1
  • H4 Todos os recursos do Personal, mais: skipped
  • H3 Microsoft 365 Premium
  • H4 Tudo no Family e mais:
  • H3 Microsoft 365
  • H3 Microsoft 365 Básico
  • H4 O Microsoft 365 Básico inclui:
  • H3 Microsoft 365 Personal
  • H4 Tudo do Básico e mais:
  • H3 Microsoft 365 Family
  • H4 Todos os recursos do Personal, mais:
  • H3 Microsoft 365 Premium
  • H4 Tudo no Family e mais:
  • H2 Dê o próximo passo com o Microsoft 365
  • H3 Escolha seu plano
  • H4 Frontier: experimente as novidades em IA
  • H2 Perguntas frequentes
  • H3 Qual é a diferença entre o Copilot no aplicativo móvel e o Copilot nos aplicativos do Microsoft 365?
  • H3 Posso usar o Copilot de forma integrada entre os meus aplicativos como Outlook, Word e PowerPoint?
  • H3 Quais são os cenários comuns em que alguém pode usar o Copilot no Microsoft 365?
  • H3 O Microsoft 365 Family ou o Microsoft 365 Premium são as melhores opções para usar com minha equipe no trabalho?
  • H3 Sou assinante do Microsoft 365 Family. Minha família agora tem acesso ao Copilot como parte do nosso plano?
  • H3 O que é o programa Microsoft Frontier e como participar?
  • H3 Qual é o benefício do Copilot no Microsoft 365 em comparação com ferramentas gratuitas ou mais baratas como ChatGPT, Notion AI, etc.?
  • H2 Siga o Microsoft 365

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

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

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

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
12 landmarks
PASS
12 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 "Menu contextual" 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+
Alt Text Quality
All 133 images OK
PASS
All 133 images OK
Info::
21 decorative image(s) correctly marked
Info::
112 image(s) with good alt text
133 images 112 good alt text 21 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cli_shellHeaderSearchInputsearchPesquisa Expandidaaria-label
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 365 Básic…20.06:13.0:1
#000000
#FEF9F3
Pass
h1 Microsoft 365 Family20.06:13.0:1
#000000
#FEF9F3
Pass
h2 Global20.06:13.0:1
#000000
#FEF9F3
Pass
h2 Aumente sua produtiv…20.06:13.0:1
#000000
#FEF9F3
Pass
h2 Descubra o que está…20.06:13.0:1
#000000
#FEF9F3
Pass
h2 Tudo do Microsoft 36…20.06:13.0:1
#000000
#FEF9F3
Pass
h2 Dê o próximo passo…20.06:13.0:1
#000000
#FEF9F3
Pass
h2 Siga o Microsoft 36520.06:13.0:1
#000000
#FEF9F3
Pass
h3 Aplicativos para ger…20.06:13.0:1
#000000
#FEF9F3
Pass
h3 Aplicativos para ger…20.06:13.0:1
#000000
#FEF9F3
Pass
h3 Microsoft 36520.06:13.0:1
#000000
#FEF9F3
Pass
h3 Microsoft 365 Person…20.06:13.0:1
#000000
#FEF9F3
Pass
h3 Microsoft 365 Premiu…20.06:13.0:1
#000000
#FEF9F3
Pass
h3 Microsoft 36520.06:13.0:1
#000000
#FEF9F3
Pass
h3 Microsoft 365 Básic…20.06:13.0:1
#000000
#FEF9F3
Pass
h3 Microsoft 365 Person…20.06:13.0:1
#000000
#FEF9F3
Pass
h3 Microsoft 365 Family20.06:13.0:1
#000000
#FEF9F3
Pass
h3 Microsoft 365 Premiu…20.06:13.0:1
#000000
#FEF9F3
Pass
title Microsoft 365 para u…18.76:14.5:1
#000000
#F2F2F2
Pass
span This is the Trace Id…18.76:14.5:1
#000000
#F2F2F2
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 95/100 — 3 failing, 28 passed
PASS
95

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
Pular para o conteúdo principal 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
Pesquisar no Microsoft 365 div.c-uhfh-gcontainer-st > div.c-uhfh-actions > form#searchForm > button#search

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
O Microsoft 365 Premium e os novos recursos avançados do Copilot já estão dispo… div.block-feature__headings > div.block-feature__title > div > h4
O Microsoft 365 Básico inclui:  div.block-feature__top > div.block-feature__headings > div.block-feature__title > h4
Todos os recursos do Personal, mais: div.block-feature__top > div.block-feature__headings > div.block-feature__title > h4

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
Explore todos os apps div.layout__col > div.section-master__layout-slot > div.button-group > a#action-ocd6d0
Veja ps detalhes 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.
●`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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●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
○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
○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