Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 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.

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 ✗

Landmark Structure

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title App Center ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Welcome to App Center.

1.31:1

#000000

#0F1D51

needs 3.0:1 (large text)

32px · above the fold

h2 Collect real-time diagnostics,

1.31:1

#000000

#0F1D51

needs 3.0:1 (large text)

24px · mid-page

h2 prioritize and fix critical issue.

1.31:1

#000000

#0F1D51

needs 3.0:1 (large text)

24px · mid-page

h2 App analytics, made for developers.

1.31:1

#000000

#0F1D51

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Live analytics for sessions, events, cra…

1.31:1

#000000

#0F1D51

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Who? What? Where? When? Why? How?

1.31:1

#000000

#0F1D51

needs 3.0:1 (large text)

19px · bottom of viewport

title Visual Studio App Center | iOS, Android,…

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · top of page (header area)

span Visual Studio

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · top of page (header area)

strong App Center

1.31:1

#000000

#0F1D51

needs 3.0:1 (large text)

16px · top of page (header area)

span Documentation

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · above the fold

span 🚀 Get started

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · above the fold

div Visual Studio App Center was retired on …

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · above the fold

a Learn more.

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · above the fold

p Continuously monitor apps for every plat…

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · above the fold

span Start free

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · above the fold

span Sign In

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · above the fold

span Pricing

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · mid-page

span Blog

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · mid-page

span Documentation

1.31:1

#000000

#0F1D51

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to App Cent…	1.31:1	3.0:1	#000000	#0F1D51	Fail
h2 Collect real-time di…	1.31:1	3.0:1	#000000	#0F1D51	Fail
h2 prioritize and fix c…	1.31:1	3.0:1	#000000	#0F1D51	Fail
h2 App analytics, made …	1.31:1	3.0:1	#000000	#0F1D51	Fail
h3 Live analytics for s…	1.31:1	3.0:1	#000000	#0F1D51	Fail
h3 Who? What? Where? Wh…	1.31:1	3.0:1	#000000	#0F1D51	Fail
title Visual Studio App Ce…	1.31:1	4.5:1	#000000	#0F1D51	Fail
a Skip to main content	1.31:1	4.5:1	#000000	#0F1D51	Fail
span Visual Studio	1.31:1	4.5:1	#000000	#0F1D51	Fail
strong App Center	1.31:1	3.0:1	#000000	#0F1D51	Fail
span Documentation	1.31:1	4.5:1	#000000	#0F1D51	Fail
span 🚀 Get started	1.31:1	4.5:1	#000000	#0F1D51	Fail
div Visual Studio App Ce…	1.31:1	4.5:1	#000000	#0F1D51	Fail
a Learn more.	1.31:1	4.5:1	#000000	#0F1D51	Fail
p Continuously monitor…	1.31:1	4.5:1	#000000	#0F1D51	Fail
span Start free	1.31:1	4.5:1	#000000	#0F1D51	Fail
span Sign In	1.31:1	4.5:1	#000000	#0F1D51	Fail
span Pricing	1.31:1	4.5:1	#000000	#0F1D51	Fail
span Blog	1.31:1	4.5:1	#000000	#0F1D51	Fail
span Documentation	1.31:1	4.5:1	#000000	#0F1D51	Fail

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+

Heading Hierarchy

5 headings

PASS

5 headings

Single H1 present

H1 Welcome to App Center.
H2 Collect real-time diagnostics, prioritize and fix critical issue.
H2 App analytics, made for developers.
H3 Live analytics for sessions, events, crashes, and more
H3 Who? What? Where? When? Why? How?

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

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

14 links, 0 buttons — all OK

PASS

14 links, 0 buttons — all OK

14 link(s) with descriptive text

14 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

14 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 21 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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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

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

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○Buttons have an accessible name

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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