Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

404 Error Page

Action

HTTP 500, bare page

FIX

HTTP 500, bare page

Unexpected status code: HTTP 500

Expected HTTP 404 but received 500. This may confuse search engine crawlers.

Got: HTTP 500

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 500 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://outlook.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://outlook.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Lighthouse Accessibility Audits

Score 88/100 — 5 failing, 26 passed

REVIEW

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Expanded `div.c-uhfh-gcontainer-st > div.c-uhfh-actions > form#searchForm > input#cli_shellHeaderSearchInput`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Outlook for Windows Outlook for Mac Outlook for Web Outlook for Mobile `ul.js-paddle-items > li.nested-menu > div.c-uhf-menu > ul`
For home For business `ul.js-paddle-items > li.nested-menu > div.c-uhf-menu > ul`
AI email assistant AI email generator Email account Shared calendar Copilot lea… `ul.js-paddle-items > li.nested-menu > div.c-uhf-menu > ul`
Global Microsoft 365 Azure Copilot Windows Surface Xbox Deals Small Business Su… `ul.js-paddle-items > li > div.c-uhf-menu > ul.f-multi-column`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

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
Apps with subscription value `div.card-plan-detail > div.card-plan-detail__badges > div.card-plan-detail__badge-text > h6.text`
Apps with subscription value `div.card-plan-detail > div.card-plan-detail__badges > div.card-plan-detail__badge-text > h6.text`
Apps with subscription value `div.card-plan-detail > div.card-plan-detail__badges > div.card-plan-detail__badge-text > h6.text`

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
All Microsoft expand to see list of Microsoft products and services `header.c-uhfh > div.theme-light > div.c-uhfh-gcontainer-st > button.c-action-trigger`
Close search `header.c-uhfh > div.theme-light > div.c-uhfh-gcontainer-st > button.c-action-trigger`
Microsoft 365 `div.theme-light > div.c-uhfh-gcontainer-st > div.c-show-pipe > a#uhfCatLogo`
Home `nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a.c-uhf-nav-link`
Outlook `nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_subsitename`
For business `nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_6`
Support `nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_16`
Buy now `nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_custom_button_outline_newtab_buynow_bhvr92`
Sign in `nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_custom_outline_signin_bhvr100`
Surface Pro `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Surface Laptop `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Surface Laptop Studio 2 `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Copilot for organizations `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Copilot for personal use `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
AI in Windows `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Explore Microsoft products `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Windows 11 apps `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Account profile `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Download Center `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Store support `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Returns `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Order tracking `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Certified Refurbished `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Store Promise `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Flexible Payments `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft in education `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Devices for education `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Teams for Education `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft 365 Education `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
How to buy for your school `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Educator training and development `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Deals for students and parents `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
AI for education `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft AI `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Security `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Dynamics 365 `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft 365 `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Power Platform `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Teams `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft 365 Copilot `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Small Business `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Azure `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Developer `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Learn `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Support for AI marketplace apps `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Tech Community `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Microsoft Marketplace `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Marketplace Rewards `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Visual Studio `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Careers `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
About Microsoft `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Company news `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Privacy at Microsoft `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Investors `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Diversity and inclusion `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Accessibility `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Sustainability `div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link`
Sitemap `nav > ul.c-list > li#c-uhff-footer_sitemap > a.c-uhff-link`
Contact Microsoft `nav > ul.c-list > li#c-uhff-footer_contactus > a.c-uhff-link`
Privacy `nav > ul.c-list > li#c-uhff-footer_privacyandcookies > a.c-uhff-link`
Manage cookies `nav > ul.c-list > li#c-uhff-footer_managecookies > a.c-uhff-link`
Terms of use `nav > ul.c-list > li#c-uhff-footer_termsofuse > a.c-uhff-link`
Trademarks `nav > ul.c-list > li#c-uhff-footer_trademarks > a.c-uhff-link`
Safety & eco `nav > ul.c-list > li#c-uhff-footer_safetyandeco > a.c-uhff-link`
Recycling `nav > ul.c-list > li#c-uhff-recycling > a.c-uhff-link`
About our ads `nav > ul.c-list > li#c-uhff-footer_aboutourads > a.c-uhff-link`

These items highlight common accessibility best practices.

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
Search Search Microsoft 365 `div.c-uhfh-gcontainer-st > div.c-uhfh-actions > form#searchForm > button#search`
See plans and pricing `div.secondary-nav > nav#sticky-nav > div.action > a#action-ocf626`
Create a free account `div.sku > div.sku__buttons > div.button-group > a#action-oc5959`
View all apps `div.row > div.col > div.button-group > a#action-oc45c2`

○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-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

●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.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●ARIA `tooltip` elements have accessible names

●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

●No element has a `[tabindex]` value greater than 0

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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 `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

○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.

○Identical links have the same purpose.

○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

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

A+

Color Contrast (Screenshot)

1 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.

1 pass

Show all checked elements (1)

Element	Ratio	Required	FG	BG	Result
title Outlook	21.00:1	4.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.