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 6 REVIEW 3 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

Web Manifest

Action

Not found

FIX

Not found

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.

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 ✗

Form Accessibility

Action

3 of 6 controls have issues

REVIEW

3 of 6 controls have issues

3 control(s) without accessible label

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

Got: <input name="category">; <input name="category">; <input name="category">

3 control(s) properly labeled

6 controls

3 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
#site-header-search-autocomplete-input-mobile	search	Search	aria-label
#site-header-search-autocomplete-input	search	Search	aria-label
#welcome-page-search-form-autocomplete-input	text	Search	aria-label
category	input	(none)	none
category	input	(none)	none
category	input	(none)	none

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

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

Link & Button Quality

3 issue(s) across 76 links and 19 buttons

REVIEW

3 issue(s) across 76 links and 19 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://aka.ms/MSBuild_FY26_BN_MSLearn_Hero ("Learn more")

2 button(s) with no accessible text

75 link(s) with descriptive text

76 links

0 empty

1 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://aka.ms/MSBuild_FY26_BN_MSLearn_H…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Msbuild Fy26 Bn Mslearn Hero
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

92 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://aka.ms/MSBuild_FY26_BN_MSLearn_Hero ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 - Content not found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: 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 Mode✓ Dark Mode Supported

color-scheme meta light dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 1 pass AA only

title Microsoft Learn: Build with answers in r…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Learn more

2.41:1

#000000

#015730

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Learning for everyon…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Microsoft Build 2026	6.61:1	3.0:1	#000000	#52A31B	Pass
h2 Popular technical re…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get started with Mic…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Discover AI, Azure, …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Take in-demand train…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Additional resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Microsoft Learn: Bui…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to main content	1.00:1	4.5:1	#000000	#000000	Fail
p June 2-3, 2026	7.40:1	4.5:1	#000000	#1FAF6A	Pass
p Go deep on real code…	5.53:1	4.5:1	#000000	#01947C	Pass
span Learn more	2.41:1	4.5:1	#000000	#015730	Fail
span Dismiss alert	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p This browser is no l…	18.42:1	4.5:1	#000000	#F1F0EC	Pass
p Upgrade to Microsoft…	16.82:1	4.5:1	#000000	#E8E6DF	Pass
a Download Microsoft E…	16.82:1	4.5:1	#000000	#E8E6DF	Pass
a More info about Inte…	14.36:1	4.5:1	#171717	#E8E6DF	Pass
span Learn	16.82:1	4.5:1	#000000	#E8E6DF	Pass
span Suggestions will fil…	16.82:1	4.5:1	#000000	#E8E6DF	Pass
a Sign in	16.82:1	4.5:1	#000000	#E8E6DF	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+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

7 headings

PASS

7 headings

Single H1 present

H2 Microsoft Build 2026
H1 Learning for everyone, everywhere
H2 Popular technical resources and training
H3 Discover AI, Azure, and Copilot essentials
H3 Take in-demand training
H3 Additional resources
H2 Get started with Microsoft Learn MCP Server

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

10 decorative image(s) correctly marked

10 images 10 decorative

All images have appropriate alt text.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 26 passed

PASS

100

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.

○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

●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

●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

●Elements with visible text labels have matching accessible names.

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

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

○Image elements have `[alt]` attributes

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

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

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

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

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