Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Landmark Structure

Action

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

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

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

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

Lighthouse Accessibility Audits

Score 84/100 — 3 failing, 12 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.

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
Real-Time Technographic Data & API `body > div.hero-section > div.hero-content > div.badge`
View API Docs → `div.platform-cta-wrapper > div.cta-section > div.cta-buttons > a.btn-primary`
Revealera `footer.footer > div.footer-content > p > a`

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
Revealera `footer.footer > div.footer-content > p > a`

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-hidden="true"]` is not present on the document `<body>`

●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-hidden="true"]` elements do not contain focusable descendents

●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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

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

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

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

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

○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

21 headings

PASS

21 headings

Single H1 present

H1 Every tech stack change across 1,700+ B2B products
H2 Building a sales or GTM product? Ship these signals inside it.
H2 Get Alerts When It Matters
H2 API for Sales Platforms & GTM Teams
H2 What you can do with our data
H3 Find prospects actively buying in your primary (or adjacent) category
H3 Find prospects that recently churned from competitors
H3 Get deep account intelligence
H3 Find potential churn candidates
H3 Build highly relevant marketing lists
H3 Stack our signals with other 1st or 3rd party signals
H2 Frequently Asked Questions
H3 Where does your data come from, and how is it different from BuiltWith, Wappalyzer or TheirStack?
H3 Why do you cover fewer products than BuiltWith or TheirStack?
H3 Can you tell me which companies just adopted AI tools?
H3 Do you cover newer tools, or just established ones?
H3 How many product categories does your data cover?
H3 How many of these subscribe/churn events do you uncover per month?
H3 What are the limitations of your data?
H3 Do you have an UI/app or just an API?
H3 Can I get a free trial?

A+

Heading Text Quality

All 21 heading(s) have substantive, well-formed text

PASS

All 21 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

17 image(s) with good alt text

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

Link & Button Quality

61 links, 0 buttons — all OK

PASS

61 links, 0 buttons — all OK

14 link(s) open in new tab without warning

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

Got: https://docs.bloomberry.com; https://docs.bloomberry.com; https://bloomberry.com/explore; https://docs.bloomberry.com; https://bloomberry.com/signup.html; https://docs.bloomberry.com; https://revealera.com; https://x.com/bloomberry; https://linkedin.com/company/revealera; https://www.g2.com/products/bloomberry/reviews (+4 more)

47 link(s) with descriptive text

61 links

0 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://docs.bloomberry.com	View API Docs →	new tab	Add '(opens in new tab)' to text
https://docs.bloomberry.com	View API Documentation →	new tab	Add '(opens in new tab)' to text
https://bloomberry.com/explore	explore all our categories her…	new tab	Add '(opens in new tab)' to text
https://docs.bloomberry.com	API documentation	new tab	Add '(opens in new tab)' to text
https://bloomberry.com/signup.html	form	new tab	Add '(opens in new tab)' to text
https://docs.bloomberry.com	API Docs	new tab	Add '(opens in new tab)' to text
https://revealera.com	Revealera	new tab	Add '(opens in new tab)' to text
https://x.com/bloomberry	X	new tab	Add '(opens in new tab)' to text
https://linkedin.com/company/revealera	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/bloomberry/r…	G2 Reviews	new tab	Add '(opens in new tab)' to text
https://claude.ai/new?q=How%20is%20Bloom…	Ask Claude	new tab	Add '(opens in new tab)' to text
https://chatgpt.com/?q=How%20is%20Bloomb…	Ask ChatGPT	new tab	Add '(opens in new tab)' to text
https://www.perplexity.ai/search?q=How%2…	Ask Perplexity	new tab	Add '(opens in new tab)' to text
https://revealera.com	Revealera	new tab	Add '(opens in new tab)' to text

47 links and buttons have descriptive text

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

https://docs.bloomberry.com; https://docs.bloomberry.com; https://bloomberry.com/explore; https://docs.bloomberry.com; https://bloomberry.com/signup.html; https://docs.bloomberry.com; https://revealera.com; https://x.com/bloomberry; https://linkedin.com/company/revealera; https://www.g2.com/products/bloomberry/reviews (+4 more)

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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 143 visible text node(s) render at >= 12 CSS pixels

PASS

All 143 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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 Every	19.92:1	3.0:1	#000000	#FEF8F2	Pass
h1 across	19.92:1	3.0:1	#000000	#FEF8F2	Pass
h1 B2B products	19.92:1	3.0:1	#000000	#FEF8F2	Pass
h2 Building a sales or …	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h2 Get Alerts When It M…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h2 API for Sales Platfo…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h2 What you can do with…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h2 Frequently Asked Que…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Find prospects activ…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Find prospects that …	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Get deep account int…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Find potential churn…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Build highly relevan…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Stack our signals wi…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Where does your data…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Why do you cover few…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Can you tell me whic…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 Do you cover newer t…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 How many product cat…	20.10:1	3.0:1	#000000	#FFF9F3	Pass
h3 How many of these su…	20.10:1	3.0:1	#000000	#FFF9F3	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.