Skip to content
https://asp.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-jckiiu
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.

D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://asp.net/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://asp.net/manifest.json

Manifest contains invalid JSON.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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.
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: dark light
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 dark light Dark theme-color Not set CSS indicators Detected

Detection limited to meta tags and inline styles.

A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Contextual menu" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
17 headings
PASS
17 headings
Info::
Single H1 present
  • H1 ASP.NET Core
  • H2 Build web apps fast with one stack
  • H2 Web Apps
  • H2 APIs
  • H2 Real-time
  • H2 Artificial Intelligence and ML
  • H2 What is ASP.NET Core?
  • H2 Learn ASP.NET Core
  • H2 Fast and scalable
  • H2 Build secure apps
  • H2 Active community and open-source
  • H2 Free hosting on Azure
  • H2 You may also be interested in these free e-books
  • H3 Blazor e-book
  • H3 ASP.NET Core architecture e-book
  • H3 Azure quick start e-book
  • H2 Ready to get started?
A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
9 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
16 images 5 good alt text 9 decorative
IssueCount
too long2 image(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#culture-optionsselectChange languagearia-label
qsearch(Search or ask a question)placeholder only

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

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

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)
ElementRatioRequiredFGBGResult
h1 ASP.NET Core20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Build web apps fast …20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Web Apps20.12:13.0:1
#000000
#FAFAFA
Pass
h2 APIs20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Real-time20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Artificial Intellige…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 What is ASP.NET Core…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Learn ASP.NET Core20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Fast and scalable20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Build secure apps20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Active community and…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Free hosting on Azur…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 You may also be inte…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Ready to get started…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Blazor e-book20.12:13.0:1
#000000
#FAFAFA
Pass
h3 ASP.NET Core archite…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Azure quick start e-…20.12:13.0:1
#000000
#FAFAFA
Pass
title ASP.NET Core, an ope…18.76:14.5:1
#000000
#F2F2F2
Pass
a Skip to main content18.76:14.5:1
#000000
#F2F2F2
Pass
p We use optional cook…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 97/100 — 1 failing, 27 passed
PASS
97

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.

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
Download PDF div.col-lg-4 > ul.mt-auto > li > a#ebook-blazor-for-web-forms-devs-pdf
View on the web div.col-lg-4 > ul.mt-auto > li > a#ebook-blazor-for-web-forms-devs-web
Download PDF div.col-lg-4 > ul.mt-auto > li > a#ebook-aspnet-pdf
View on the web div.col-lg-4 > ul.mt-auto > li > a#ebook-aspnet-web
Powered by .NET 10.0.7 nav.uhf-footer-menu > ul > li > a#uhf-Powered by .NET 10.0.7
Contact Microsoft nav.uhf-footer-menu > ul > li > a#uhf-Contact Microsoft
Support nav.uhf-footer-menu > ul > li > a#uhf-Support
Privacy & Cookies nav.uhf-footer-menu > ul > li > a#uhf-Privacy & Cookies
Manage cookies nav.uhf-footer-menu > ul > li > a#uhf-Manage cookies
Terms of Use nav.uhf-footer-menu > ul > li > a#uhf-Terms of Use
Trademarks nav.uhf-footer-menu > ul > li > a#uhf-Trademarks

These items highlight common accessibility best practices.

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.
Select elements have associated label elements.
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
Heading elements appear in a sequentially-descending order
Skip links are focusable.
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.
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
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.

Send Feedback