Skip to content
https://www.stackoverflow.blog

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
10 landmarks
FIX
10 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Alt Text Quality
Action
16 of 36 images have issues
FIX
16 of 36 images have issues
Critical::
16 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
16 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
20 image(s) with good alt text
36 images 20 good alt text 16 missing
IssueCount
missing16 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ff5e00
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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
No navigation patterns
FIX
No navigation patterns
Info::
6 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 6 <nav> element(s)
Back to Top
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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found! ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Lighthouse Accessibility Audits
Action
Score 76/100 — 7 failing, 23 passed
REVIEW
76

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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search form.print:d-none > div > div.d-none > button.s-topbar--item

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.flex--item12 > div.pt24 > div.d-flex > button.bg-black-600 div.flex--item12 > div.pt24 > div.d-flex > button.bg-black-600
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100
div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100 div.flex--item6 > div.pt24 > div.d-flex > button.bg-black-100

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md
article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md article.overflow-hidden > div.d-flex > a.flex--item6 > img.bar-md

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.d-flex > div.flex--item4 > div.p24 > iframe.mt12 div.d-flex > div.flex--item4 > div.p24 > iframe.mt12

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6
div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6 div.flex--item8 > article.overflow-hidden > div.d-flex > a.flex--item6

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
Everything nav.fs-subheading > ul.list-reset > li.my4 > a.router-link-active
Read previous issues → div.d-flex > div.flex--item > p.mb12 > a.s-link
or edit your settings on your profile page. div.p-wrapper > div.d-flex > div.flex--item > a.mt12
Accept all cookies div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-accept-btn-handler
Necessary cookies only div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-reject-all-handler
Customize settings div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●Form elements have associated labels
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 are distinguishable without relying on color.
●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
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○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
○`<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
○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.
○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
58 headings
PASS
58 headings
Warning::
Multiple H1 headings (41 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Messed up my CV dates — how screwed am I?
  • H1 Did the word “elderly” originally describe what we would now call a middle-aged person? duplicate H1
  • H1 On zombies: What's it like to be nobody? duplicate H1
  • H1 mgt.clearMarks is not a function duplicate H1
  • H1 Domain expertise still wanted: the latest trends in AI-assisted knowledge for developers duplicate H1
  • H1 He designed C++ to solve your code problems duplicate H1
  • H1 What’s new at Stack Overflow: March 2026 duplicate H1
  • H1 What’s new at Stack Overflow: February 2026 duplicate H1
  • H1 What’s new at Stack Overflow: January 2026 duplicate H1
  • H1 Your 2025 Stacked: A year of knowledge, community, and impact duplicate H1
  • H1 What the AI trust gap means for enterprise SaaS duplicate H1
  • H1 Building shared coding guidelines for AI (and people too) duplicate H1
  • H1 AI is becoming a second brain at the expense of your first one duplicate H1
  • H1 The context problem: Why enterprise AI needs more than foundation models duplicate H1
  • H1 Organizing productive platform teams duplicate H1
  • H1 DeveloperWeek 2026: Making AI tools that are actually good duplicate H1
  • H1 Your sneak peek at the redesigned Stack Overflow duplicate H1
  • H1 Defense against uploads: Q&A with OSS file scanner, pompelmi duplicate H1
  • H1 Mind the gap: Closing the AI trust gap for developers duplicate H1
  • H1 How everyone and anyone can use AI for good duplicate H1
  • H1 Is anyone using AI for good? duplicate H1
  • H1 Why demand for code is infinite: How AI creates more developer jobs duplicate H1
  • H1 Code smells for AI agents: Q&A with Eno Reyes of Factory duplicate H1
  • H1 Are you learning with AI? We want to know about it! duplicate H1
  • H1 Are bugs and incidents inevitable with AI coding agents? duplicate H1
  • H1 Stack Gives Back 2025! duplicate H1
  • H1 Seizing the means of messenger production duplicate H1
  • H1 How can you test your code when you don’t know what’s in it? duplicate H1
  • H1 Prevent agentic identity theft duplicate H1
  • H1 A love letter to 'girl games' duplicate H1
  • H1 Comprehension debt: the hidden cost of AI generated code duplicate H1
  • H1 Email address obfuscation: What works in 2026? duplicate H1
  • H1 How ReXGlue is bringing the Xbox 360 into the static recompilation era duplicate H1
  • H1 The cognitive dark forest duplicate H1
  • H1 The jellies that evolved a different way to keep time duplicate H1
  • H1 So where are all the AI apps? duplicate H1
  • H1 Box of secrets duplicate H1
  • H1 Snowflake Cortex AI escapes sandbox and executes malware duplicate H1
  • H1 Your frustration is the product duplicate H1
  • H1 Be intentional about how AI changes your codebase duplicate H1
  • H1 ENIAC’s 80th anniversary: a legacy of innovation duplicate H1
  • H2 Want updates to your inbox?
  • H2 Issue 323: Where have all the coders gone?
  • H2 Issue 322: Moving too fast and breaking too much
  • H2 Issue 321: Building good AI ain't so easy
  • H2 Issue 320: AI code generating the ship of Theseus
  • H3 Our Stack
  • H3 Company
  • H3 Support
  • H3 Elsewhere
  • H2 Your privacy
  • H2 Cookie Settings
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H4 Performance Cookies
  • H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Form Accessibility
1 of 13 controls have issues
PASS
1 of 13 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="text">
Info::
12 control(s) properly labeled
13 controls
12 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputemailnone
#theme-lightradioLightfor/id
#theme-darkradioDarkfor/id
#theme-systemradioAutofor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
inputtext(Find something…)placeholder only

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

<input type="text">

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 Messed up my CV date…20.65:13.0:1
#000000
#FDFDFD
Pass
h1 Did the word “elde…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 On zombies: What's i…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 mgt.clearMarks is no…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Domain expertise sti…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 He designed C++ to s…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 What’s new at Stac…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 What’s new at Stac…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 What’s new at Stac…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Your 2025 Stacked: A…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 What the AI trust ga…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Building shared codi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 AI is becoming a sec…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 The context problem:…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Organizing productiv…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 DeveloperWeek 2026: …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Your sneak peek at t…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Defense against uplo…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Mind the gap: Closin…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 How everyone and any…21.00:13.0: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.

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

Send Feedback