Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 1 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-qlq668

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://codeplex.com/manifest.json contains invalid JSON. Browsers cannot parse it.

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

4 navigation landmark(s) detected

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 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Link & Button Quality

1 issue(s) across 127 links and 18 buttons

REVIEW

1 issue(s) across 127 links and 18 buttons

2 link(s) open in new tab without warning

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

Got: https://go.microsoft.com/fwlink/?LinkId=521839; https://aka.ms/3rdpartycookies

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.uhf-contextual-nav-trigger (#312 on page)

125 link(s) with descriptive text

127 links

0 empty

0 generic text

2 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://go.microsoft.com/fwlink/?LinkId=…	Privacyverklaring	new tab	Add '(opens in new tab)' to text
https://aka.ms/3rdpartycookies	Cookies van derden	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

142 links and buttons have descriptive text

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

https://go.microsoft.com/fwlink/?LinkId=521839; https://aka.ms/3rdpartycookies

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.uhf-contextual-nav-trigger (#312 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

18 headings

PASS

18 headings

Single H1 present

H1 Word een racelegende
H2 Maak kennis met Surface Laptop
H2 Surface Pro, Copilot+ PC
H2 Je productiviteit, een boost gegeven
H2 Xbox Game Pass Ultimate
H2 Accessoires om van te houden
H2 Microsoft Edge
H2 Voor bedrijven
H3 Surface Pro voor zakelijk gebruik, Copilot+ PC | Intel
H3 Microsoft 365 Copilot
H3 Doe mee aan het AI-tijdperk
H3 Windows 11 voor bedrijven
H2 Nieuw
H2 Microsoft Store
H2 Onderwijs
H2 Zakelijk
H2 Ontwikkelaar en IT
H2 Bedrijf

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

2 image(s) with alt text over 125 characters

6 decorative image(s) correctly marked

9 image(s) with good alt text

17 images 9 good alt text 6 decorative

Issue	Count
too long	2 image(s)

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="q">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search	(Zoeken op Microsoft.com)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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 Word een racelegende	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Maak kennis met Surf…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Surface Pro, Copilot…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Je productiviteit, e…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Xbox Game Pass Ultim…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Accessoires om van t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Microsoft Edge	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Voor bedrijven	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Nieuw	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Microsoft Store	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Onderwijs	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Zakelijk	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ontwikkelaar en IT	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Bedrijf	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Surface Pro voor zak…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Microsoft 365 Copilo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Doe mee aan het AI-t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Windows 11 voor bedr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Microsoft – AI, cl…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
span Trace Id is missing	18.76:1	4.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 100/100 — 1 failing, 27 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.

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
Shop voor je bedrijf `nav#link-list-uid1e91 > ul.text-center > li.font-weight-semibold > a`
Word nu lid `div.card > div.card-footer > div.link-group > a.btn`
Download nu `div.card > div#card-body-highlight-uid9268 > div.link-group > a.btn`
Koop nu `div.card > div.card-footer > div.link-group > a.btn`

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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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