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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-lweca9

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

Got: https://windows.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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 5 <nav> element(s)

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.

Landmark Structure

Action

12 landmarks

REVIEW

12 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

5 <nav> landmark(s) found

1 of 5 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Alt Text Quality

2 of 28 images have issues

REVIEW

2 of 28 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 decorative image(s) correctly marked

24 image(s) with good alt text

28 images 24 good alt text 2 decorative 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Link & Button Quality

181 links, 29 buttons — all OK

REVIEW

181 links, 29 buttons — all OK

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a#uhfLogo

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.microsoft.com/en-us/windows/back-to-school-offer; https://www.microsoft.com/en-us/windows/business/windows-11-pro; https://support.microsoft.com/windows; http://www.facebook.com/windows; http://www.twitter.com/windows; https://www.facebook.com/sharer/sharer.php?m2w&s=100&u=https://www.microsoft.…; http://twitter.com/share?url=https://www.microsoft.com/en-us/windows/

173 link(s) with descriptive text

181 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.microsoft.com	Microsoft	img no alt	Add alt attribute to the image
https://www.microsoft.com/en-us/windows/…	Explore offer on our webpage	new tab	Add '(opens in new tab)' to text
https://www.microsoft.com/en-us/windows/…	Continue to business version o…	new tab	Add '(opens in new tab)' to text
https://support.microsoft.com/windows	Learn more about Windows Suppo…	new tab	Add '(opens in new tab)' to text
http://www.facebook.com/windows	Follow Microsoft Windows on Fa…	new tab	Add '(opens in new tab)' to text
http://www.twitter.com/windows	Follow Microsoft Windows on X …	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sharer/sharer.p…	Share this page on Facebook	new tab	Add '(opens in new tab)' to text
http://twitter.com/share?url=https://www…	Share this page on X (formerly…	new tab	Add '(opens in new tab)' to text

202 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a#uhfLogo

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.microsoft.com/en-us/windows/back-to-school-offer; https://www.microsoft.com/en-us/windows/business/windows-11-pro; https://support.microsoft.com/windows; http://www.facebook.com/windows; http://www.twitter.com/windows; https://www.facebook.com/sharer/sharer.php?m2w&s=100&u=https://www.microsoft.…; http://twitter.com/share?url=https://www.microsoft.com/en-us/windows/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Heading Hierarchy

19 headings

PASS

19 headings

Single H1 present

H2 Global
H2 Choose a Windows PC
H2 Find the Windows PC that’s right for you
H1 Welcome to Windows
H2 Explore Windows 11’s new features
H2 Get the best Windows yet
H2 Find the right PC for you
H2 Find a PC that meets your needs
H2 What’s new in Windows 11
H3 A new AI era begins
H3 Sync your phone and PC
H2 Explore Windows 11 features
H3 Smart security
H3 Windows 11 works how you work
H3 Gaming never looked so good
H3 Creativity meets intelligence
H2 Start your Windows 11 journey
H3 Follow Microsoft Windows
H3 Share this page

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#cli_shellHeaderSearchInput	search	Search Expanded	aria-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)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to Windows	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Global	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Choose a Windows PC	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Find the Windows PC …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore Windows 11�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get the best Windows…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Find the right PC fo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Find a PC that meets…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What’s new in Wind…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore Windows 11 …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Start your Windows …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A new AI era begins	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sync your phone and …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Smart security	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Windows 11 works ho…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Gaming never looked …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Creativity meets int…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Follow Microsoft Win…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Share this page	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Experience the Power…	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.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 25 passed

PASS

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
Skip to main content `div#headerArea > div#headerRegion > div#headerUniversalHeader > a#uhfSkipToMain`
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`
Microsoft `header.c-uhfh > div.theme-light > div.c-uhfh-gcontainer-st > a#uhfLogo`
Windows `div.theme-light > div.c-uhfh-gcontainer-st > div.cat-logo-button-cont > button#uhfCatLogoButton`
Search or ask a question `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
View Copilot+ PCs `nav.c-link-navigation > ul > li > a.c-hyperlink`
View laptops `nav.c-link-navigation > ul > li > a.c-hyperlink`
View desktop computers `nav.c-link-navigation > ul > li > a.c-hyperlink`
View gaming PCs `nav.c-link-navigation > ul > li > a.c-hyperlink`
View 2-in-1s `nav.c-link-navigation > ul > li > a.c-hyperlink`

○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

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

●Heading elements appear in a sequentially-descending order

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

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

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