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 4 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

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

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 ✗

Landmark Structure

5 landmarks

REVIEW

5 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

Mobile-Readable Font Sizes

91% of visible text renders at >= 12 CSS px (38 below threshold)

REVIEW

91% of visible text renders at >= 12 CSS px (38 below threshold)

38 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.9px ("Free"); <span> 11.2px ("Courts"); <span> 10.9px ("Free"); <span> 11.2px ("Jail"); <span> 10.9px ("Free").

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 See it in action

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Interactive coverage maps

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Popular searches

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why OSINT Atlas

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

24px · bottom of viewport

h2 More than public records

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Subject Search OSINT Tool

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Score Assessment

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get full access

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Official sources only

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Checked every week

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Nothing stored

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

19px · bottom of viewport

h3 250+ OSINT Resources

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Subject Search

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Privacy Score & Wizard

1.12:1

#000000

#0A1122

needs 3.0:1 (large text)

19px · bottom of viewport

title OSINT Atlas: official public records sea…

1.07:1

#000000

#070B1A

needs 4.5:1 (normal text)

16px · top of page (header area)

a OSINT Atlas

1.07:1

#000000

#070B1A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Guides

1.70:1

#000000

#1A316C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Log in

1.61:1

#000000

#192E63

needs 4.5:1 (normal text)

16px · top of page (header area)

p Open Source Intelligence Directory

1.50:1

#000000

#17295A

needs 4.5:1 (normal text)

16px · above the fold

span Every official public-record portal,

1.40:1

#000000

#14254E

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 See it in action	1.12:1	3.0:1	#000000	#0A1122	Fail
h2 Interactive coverage…	1.12:1	3.0:1	#000000	#0A1122	Fail
h2 Popular searches	1.12:1	3.0:1	#000000	#0A1122	Fail
h2 Why OSINT Atlas	1.12:1	3.0:1	#000000	#0A1122	Fail
h2 More than public rec…	1.12:1	3.0:1	#000000	#0A1122	Fail
h2 Subject Search OSINT…	1.12:1	3.0:1	#000000	#0A1122	Fail
h2 Privacy Score Assess…	1.12:1	3.0:1	#000000	#0A1122	Fail
h2 Get full access	1.12:1	3.0:1	#000000	#0A1122	Fail
h3 Official sources onl…	1.12:1	3.0:1	#000000	#0A1122	Fail
h3 Checked every week	1.12:1	3.0:1	#000000	#0A1122	Fail
h3 Nothing stored	1.12:1	3.0:1	#000000	#0A1122	Fail
h3 250+ OSINT Resources	1.12:1	3.0:1	#000000	#0A1122	Fail
h3 Subject Search	1.12:1	3.0:1	#000000	#0A1122	Fail
h3 Privacy Score & Wiza…	1.12:1	3.0:1	#000000	#0A1122	Fail
title OSINT Atlas: officia…	1.07:1	4.5:1	#000000	#070B1A	Fail
a OSINT Atlas	1.07:1	4.5:1	#000000	#070B1A	Fail
a Guides	1.70:1	4.5:1	#000000	#1A316C	Fail
a Log in	1.61:1	4.5:1	#000000	#192E63	Fail
p Open Source Intellig…	1.50:1	4.5:1	#000000	#17295A	Fail
span Every official publi…	1.40:1	4.5:1	#000000	#14254E	Fail

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+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H1 Every official public-record portal, in one place.
H2 See it in action
H2 Interactive coverage maps
H2 Popular searches
H2 Why OSINT Atlas
H3 Official sources only
H3 Checked every week
H3 Nothing stored
H2 More than public records
H3 250+ OSINT Resources
H3 Subject Search
H3 Privacy Score & Wizard
H2 Subject Search OSINT Tool
H2 Privacy Score Assessment
H2 Get full access

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#uxCovQ	search	Find a state	for/id

A+

Link & Button Quality

23 links, 19 buttons — all OK

PASS

23 links, 19 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://x.com/osintatlasio

22 link(s) with descriptive text

23 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://x.com/osintatlasio	OSINT Atlas on X (@osintatlasi…	new tab	Add '(opens in new tab)' to text

41 links and buttons have descriptive text

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

https://x.com/osintatlasio

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

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

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

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

PASS

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

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Coverage map categories `main#main > section.lp-section > div.lp-map > div.lp-cov-dots`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… `div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide`
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… `div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide`
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… `div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide`
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… `div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide`
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… `div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide`

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.

○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

●Buttons have an accessible name

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

●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 are distinguishable without relying on color.

●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

●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

●Identical links have the same purpose.

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

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

○Image elements have `[alt]` attributes

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

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

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