Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 3 REVIEW 7 FIX

Mobile-Readable Font Sizes

Action

60% of visible text renders at >= 12 CSS px (111 below threshold)

FIX

60% of visible text renders at >= 12 CSS px (111 below threshold)

111 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("docs"); <span> 11.0px ("Company intelligence · beta"); <div> 10.0px ("Start from a technology"); <span> 11.0px ("15,086"); <span> 11.0px ("54,181").

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-1c969h

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://echoloc.ai/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://echoloc.ai/manifest.json

Manifest contains invalid JSON.

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.

Link & Button Quality

2 issue(s) across 34 links and 18 buttons

REVIEW

2 issue(s) across 34 links and 18 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://x.com/echolocai; https://linkedin.com/company/echoloc

32 link(s) with descriptive text

34 links

2 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/research/whos-building-with-ai-2026/	Who's Actually Building with A…	img no alt	Add alt attribute to the image
/research/great-sap-migration-2026/	The Great SAP Migration, Measu…	img no alt	Add alt attribute to the image
/research/displacement-index-2026/	The Displacement IndexThe tech…	img no alt	Add alt attribute to the image
https://x.com/echolocai	(empty)	empty	Add link text or aria-label
https://linkedin.com/company/echoloc	(empty)	empty	Add link text or aria-label

50 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://x.com/echolocai; https://linkedin.com/company/echoloc

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Color Contrast (Screenshot)

Action

20 text elements analyzed, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA

h2 Not who they are.

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Real companies. Real evidence.

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Every company, in one frame.

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Simple, transparent pricing.

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently asked questions

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

24px · bottom of viewport

h2 They already told you

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 what they need

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h3 Ramp

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Rollout in progress

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Core stack

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Active initiatives

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Leadership gaps

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Momentum score

1.12:1

#000000

#0B1220

needs 3.0:1 (large text)

19px · bottom of viewport

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Every job post	17.08:1	3.0:1	#F5F7FB	#0C1428	Pass
h2 Not who they are.	1.12:1	3.0:1	#000000	#0B1220	Fail
h2 Real companies. Real…	1.12:1	3.0:1	#000000	#0B1220	Fail
h2 Every company, in on…	1.12:1	3.0:1	#000000	#0B1220	Fail
h2 We publish what the …	17.46:1	3.0:1	#F5F7FB	#0B1220	Pass
h2 Simple, transparent …	1.12:1	3.0:1	#000000	#0B1220	Fail
h2 Frequently asked que…	1.12:1	3.0:1	#000000	#0B1220	Fail
h2 They already told yo…	1.12:1	3.0:1	#000000	#0B1220	Fail
h2 what they need	1.12:1	3.0:1	#000000	#0B1220	Fail
h3 Ramp	1.12:1	3.0:1	#000000	#0B1220	Fail
h3 Rollout in progress	1.12:1	3.0:1	#000000	#0B1220	Fail
h3 Core stack	1.12:1	3.0:1	#000000	#0B1220	Fail
h3 Active initiatives	1.12:1	3.0:1	#000000	#0B1220	Fail
h3 Leadership gaps	1.12:1	3.0:1	#000000	#0B1220	Fail
h3 Momentum score	1.12:1	3.0:1	#000000	#0B1220	Fail
h3 Who's Actually Build…	17.46:1	3.0:1	#F5F7FB	#0B1220	Pass
h3 The Great SAP Migrat…	17.46:1	3.0:1	#F5F7FB	#0B1220	Pass
h3 The Displacement Ind…	17.46:1	3.0:1	#F5F7FB	#0B1220	Pass
title echoloc — Company …	20.09:1	4.5:1	#000000	#FAFAF8	Pass
span echoloc	20.09:1	4.5:1	#000000	#FAFAF8	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 89/100 — 3 failing, 18 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
ADOPTING `div.container > div.border-b > button.group > span.flex`
REPLACING `div.container > div.border-b > button.group > span.flex`
VELOCITY `div.container > div.border-b > button.group > span.flex`
PAIN POINT `div.flex > div.flex-1 > div.flex > span.inline-flex`
PAIN POINT `div.flex > div.flex-1 > div.flex > span.inline-flex`
PAIN POINT `div.flex > div.flex-1 > div.flex > span.inline-flex`
© 2026 echoloc. All rights reserved. `footer.py-16 > div.container > div.pt-8 > p.text-xs`
Built from each company's digital footprint — job posts, website, news, and soc… `footer.py-16 > div.container > div.pt-8 > p.text-xs`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Product `div.container > div.grid > div > h4.font-semibold`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.grid > div.md:col-span-2 > div.flex > a.w-9 `div.grid > div.md:col-span-2 > div.flex > a.w-9`
div.grid > div.md:col-span-2 > div.flex > a.w-9 `div.grid > div.md:col-span-2 > div.flex > a.w-9`

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.

○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

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

●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

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

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

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

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

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

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

1 <nav> landmark(s) 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

Heading Hierarchy

25 headings, 1 skip(s)

PASS

25 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Every job postis a confession.
H2 Not who they are.What they’re about to do.
H2 Real companies. Real evidence.Straight from their own hiring.
H2 Every company, in one frame.An x-ray of what they’re doing.
H3 Ramp
H3 Rollout in progress
H3 Core stack
H3 Active initiatives
H3 Leadership gaps
H3 Momentum score
H2 We publish what the data shows.
H3 Who's Actually Building with AI in 2026
H3 The Great SAP Migration, Measured
H3 The Displacement Index
H2 Simple, transparent pricing.Start free. Scale when ready.
H2 Frequently asked questions
H3 What is echoloc?
H3 How is this different from technographics?
H3 How fresh is the data?
H3 Can I export results?
H3 Do I need to know exact technology names?
H3 What makes echoloc different from other tools?
H2 They already told youwhat they need
H4 Product skipped
H4 Company

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

10 decorative image(s) correctly marked

10 images 10 decorative

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+

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

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+

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.

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