Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 6 REVIEW 4 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

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

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark found

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

Link & Button Quality

Action

2 issue(s) across 25 links and 3 buttons

REVIEW

2 issue(s) across 25 links and 3 buttons

6 link(s) open in new tab without warning

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

Got: https://forms.gle/uuEsawKm7u9wCT4T8; https://forms.gle/uuEsawKm7u9wCT4T8; https://github.com/prometheus; https://github.com/prometheus/prometheus; https://cncf.io/; https://www.linuxfoundation.org/trademark-usage

2 button(s) with no accessible text

19 link(s) with descriptive text

25 links

0 empty

0 generic text

6 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://forms.gle/uuEsawKm7u9wCT4T8	Prometheus User Survey (Editio…	new tab	Add '(opens in new tab)' to text
https://forms.gle/uuEsawKm7u9wCT4T8	Prometheus User Survey (Editio…	new tab	Add '(opens in new tab)' to text
https://github.com/prometheus	GitHub Logo	new tab	Add '(opens in new tab)' to text
https://github.com/prometheus/prometheus	Star us on GitHub	new tab	Add '(opens in new tab)' to text
https://cncf.io/	CNCF logo	new tab	Add '(opens in new tab)' to text
https://www.linuxfoundation.org/trademar…	Trademark Usage	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

20 links and buttons have descriptive text

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

https://forms.gle/uuEsawKm7u9wCT4T8; https://forms.gle/uuEsawKm7u9wCT4T8; https://github.com/prometheus; https://github.com/prometheus/prometheus; https://cncf.io/; https://www.linuxfoundation.org/trademark-usage

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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 1 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Open source	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 for your systems and…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Monitoring for the c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Prometheus - Monitor…	5.61:1	4.5:1	#000000	#E6522C	Pass
span Take the	12.49:1	4.5:1	#000000	#F5BAAB	Pass
span Prometheus User Surv…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span and help the communi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Prometheus User Surv…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Prometheus	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Docs	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Download	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Community	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Support & Training	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Blog	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Ctrl + K	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span metrics and monitori…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Monitor your applica…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Get started	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Download	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Get started	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.

Lighthouse Accessibility Audits

Score 86/100 — 3 failing, 19 passed

REVIEW

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.m_7485cace > div.Header_inner__ggL_E > div.m_4081bf90 > button#mantine-fdqpb6lm5-target `div.m_7485cace > div.Header_inner__ggL_E > div.m_4081bf90 > button#mantine-fdqpb6lm5-target`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Prometheus User Survey (Edition 03.2026) `div.mantine-hidden-from-sm > span > a.mantine-focus-auto > span`
Monitor your applications, systems, and services with the leading open source m… `div.m_7485cace > div.Hero_wrapper__PHxif > div.Hero_inner__M_C9y > p.mantine-focus-auto`
Get started `div.Hero_buttons__KNKv_ > a.mantine-focus-auto > span.m_80f1301b > span.m_811560b9`
Prometheus models time series in a flexible dimensional data model. Time series… `div.m_7485cace > div.m_2415a157 > a.FeaturesCards_card__6UuI0 > p.mantine-focus-auto`
The PromQL query language allows you to query, correlate, and transform your ti… `div.m_7485cace > div.m_2415a157 > a.FeaturesCards_card__6UuI0 > p.mantine-focus-auto`
Alerting rules are based on PromQL and make full use of the dimensional data mo… `div.m_7485cace > div.m_2415a157 > a.FeaturesCards_card__6UuI0 > p.mantine-focus-auto`
Prometheus servers operate independently and only rely on local storage. Develo… `div.m_7485cace > div.m_2415a157 > a.FeaturesCards_card__6UuI0 > p.mantine-focus-auto`
Prometheus provides a large number of official and community-contributed metric… `div.m_7485cace > div.m_2415a157 > a.FeaturesCards_card__6UuI0 > p.mantine-focus-auto`
Prometheus comes with hundreds of official and community-contributed integratio… `div.m_7485cace > div.m_2415a157 > a.FeaturesCards_card__6UuI0 > p.mantine-focus-auto`
MODERN MONITORING `div.m_7485cace > div.m_4081bf90 > div.m_347db0ec > span.m_5add502a`
Designed for the cloud native world, Prometheus integrates with Kubernetes and … `div.m_89ab340 > main.m_8983817 > div.m_7485cace > p.mantine-focus-auto`
Site Reliability Engineering: How Google Runs Production Systems (O'Reilly Medi… `main.m_8983817 > div.m_7485cace > blockquote.m_ddec01c0 > cite.m_dde51a35`
Prometheus is 100% open source and community-driven. All components are availab… `main.m_8983817 > div.m_7485cace > div.FeaturesCards_description__Nd9a8 > p.mantine-focus-auto`
Apache 2 License `div.m_7485cace > div.FeaturesCards_description__Nd9a8 > p.mantine-focus-auto > a.mantine-focus-auto`
GitHub `div.m_7485cace > div.FeaturesCards_description__Nd9a8 > p.mantine-focus-auto > a.mantine-focus-auto`
Star us on GitHub `div.m_6d731127 > a.mantine-focus-auto > span.m_80f1301b > span.m_811560b9`
Prometheus is a Cloud Native Computing Foundation graduated project. `main.m_8983817 > div.m_7485cace > div.FeaturesCards_description__Nd9a8 > p.mantine-focus-auto`
Cloud Native Computing Foundation `div.m_7485cace > div.FeaturesCards_description__Nd9a8 > p.mantine-focus-auto > a.mantine-focus-auto`
© Prometheus Authors 2014-2026 \| Documentation Distributed under CC-BY-4.0 `footer > div.m_7485cace > div.m_4081bf90 > p.mantine-focus-auto`
© 2026 The Linux Foundation. All rights reserved. The Linux Foundation has regi… `footer > div.m_7485cace > div.m_4081bf90 > p.mantine-focus-auto`
Trademark Usage `div.m_7485cace > div.m_4081bf90 > p.mantine-focus-auto > a.mantine-focus-auto`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Apache 2 License `div.m_7485cace > div.FeaturesCards_description__Nd9a8 > p.mantine-focus-auto > a.mantine-focus-auto`
GitHub `div.m_7485cace > div.FeaturesCards_description__Nd9a8 > p.mantine-focus-auto > a.mantine-focus-auto`
Cloud Native Computing Foundation `div.m_7485cace > div.FeaturesCards_description__Nd9a8 > p.mantine-focus-auto > a.mantine-focus-auto`
Trademark Usage `div.m_7485cace > div.m_4081bf90 > p.mantine-focus-auto > a.mantine-focus-auto`

These are opportunities to improve the legibility of your content.

○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

●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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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

A+

Heading Hierarchy

4 headings

PASS

4 headings

Single H1 present

H1 Open source metrics and monitoring for your systems and services
H2 Monitoring for the cloud native world
H2 Open Source
H2 Open Governance

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 image(s) with good alt text

5 images 5 good alt text

All images have appropriate alt text.

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 id="mantine-_R_1mmmlmtb_">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#mantine-_R_1mmmlmtb_	input	(Search)	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

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