Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 6 REVIEW 3 FIX

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗

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

8 landmarks

REVIEW

8 landmarks

<main> landmark present

4 <nav> landmark(s) found

2 of 4 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Skip link target(s) don't exist on page: #main

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

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

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

Heading Hierarchy

40 headings

REVIEW

40 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 One Platform. Zero seams.
H2 Data that never goes stale.
H2 Any data, production-ready.
H2 Find anyone. No boolean gymnastics.
H2 We help customers achieve measurable results.
H2 Built for teams who need data to just work.
H3 Launch data-powered products faster.
H3 Keep your data clean and complete.
H3 Volume without the bill shock.
H2 We don't just aggregate data. We create it.
H3 A continuous verification loop.
H4 1B+
H3 Every record has a paper trail.
H4 100%
H3 Primary sources, not resellers.
H4 97%+
H2 Infrastructure. Not another B2B data vendor.
H2 What actually changes when you switch.
H3 Without RevenueBase
H3 ?
H3 With RevenueBase
H3 1B+
H2 Go-to-market is becoming autonomous.
H2 Common questions
H3 01What is RevenueBase?
H3 02What does RevenueBase do?
H3 03Who is RevenueBase for?
H3 04How is RevenueBase different from traditional B2B data tools?
H3 05What notable companies use RevenueBase?
H3 06How many contacts and companies does RevenueBase have in its database?
H3 07What does "B2B data infrastructure" mean?
H3 08Does RevenueBase require a sales call to get started?
H3 09Is RevenueBase suitable for startups?
H3 10What is the best B2B data provider for GTM teams in 2026-2027?
H2 You shouldn’t have to choose between clean data & doing your actual job
H2 Footer
H3 Product
H3 SOLUTIONS
H3 Company
H3 Company lists

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 Page not found | RevenueBase ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

PWA Depth

3 PWA signal(s) surfaced

REVIEW

3 PWA signal(s) surfaced

Manifest is missing `display` -- defaults to browser, no PWA UX

When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

Manifest is missing `theme_color`

Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

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.

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "?"

Got: 1 ≤2-char heading(s)

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Alt Text Quality

All 23 images OK

PASS

All 23 images OK

23 image(s) with good alt text

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

62 links, 12 buttons — all OK

PASS

62 links, 12 buttons — all OK

15 link(s) open in new tab without warning

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

Got: https://docs.revenuebase.ai/; https://app.revenuebase.ai/; /book-a-demo; https://docs.revenuebase.ai/; https://app.revenuebase.ai/; /book-a-demo; https://app.revenuebase.ai/signup; https://app.revenuebase.ai/signup; https://status.revenuebase.ai/; https://www.linkedin.com/company/revenue-base/ (+5 more)

47 link(s) with descriptive text

62 links

0 empty

0 generic text

15 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://docs.revenuebase.ai/	Docs	new tab	Add '(opens in new tab)' to text
https://app.revenuebase.ai/	Log in	new tab	Add '(opens in new tab)' to text
/book-a-demo	Get a demo	new tab	Add '(opens in new tab)' to text
https://docs.revenuebase.ai/	Docs	new tab	Add '(opens in new tab)' to text
https://app.revenuebase.ai/	Log in	new tab	Add '(opens in new tab)' to text
/book-a-demo	Get a demo	new tab	Add '(opens in new tab)' to text
https://app.revenuebase.ai/signup	Start Free Trial	new tab	Add '(opens in new tab)' to text
https://app.revenuebase.ai/signup	Start building for free	new tab	Add '(opens in new tab)' to text
https://status.revenuebase.ai/	Check systems status	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/revenue…	Linked In	new tab	Add '(opens in new tab)' to text
https://x.com/revenuebase	X	new tab	Add '(opens in new tab)' to text
https://github.com/revenuebase	YouTube	new tab	Add '(opens in new tab)' to text
https://docs.revenuebase.ai/	Documentation	new tab	Add '(opens in new tab)' to text
https://jobs.ashbyhq.com/revenuebase-inc	Careers	new tab	Add '(opens in new tab)' to text
https://www.grafit.agency/	Made by GRAFIT	new tab	Add '(opens in new tab)' to text

59 links and buttons have descriptive text

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

https://docs.revenuebase.ai/; https://app.revenuebase.ai/; /book-a-demo; https://docs.revenuebase.ai/; https://app.revenuebase.ai/; /book-a-demo; https://app.revenuebase.ai/signup; https://app.revenuebase.ai/signup; https://status.revenuebase.ai/; https://www.linkedin.com/company/revenue-base/ (+5 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

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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 214 visible text node(s) render at >= 12 CSS pixels

PASS

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

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

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
h2 One Platform.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Data that never goes…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Any data, production…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Find anyone. No bool…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 achieve measurable r…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Built for teams who …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We don't just aggreg…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Infrastructure.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 when you switch.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Go-to-market is	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Common	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 between clean data &…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 your actual job	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Launch data-powered …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Keep your data clean…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Volume without the b…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A continuous verific…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Every record has a p…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Primary sources, not…	21.00:1	3.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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 24 passed

PASS

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
M e n u C l o s e `div.nav_mobile_contain > div.nav_mobile_layout > div.nav_button_wrap > div.nav_toggle_wrap`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
M e n u C l o s e `div.nav_mobile_wrap > div.nav_mobile_contain > div.nav_mobile_layout > div.nav_button_wrap`

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

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

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

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

●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 have a discernible name

●No element has a `[tabindex]` value greater than 0

●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

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

○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

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

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