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

Mobile-Readable Font Sizes

Action

67% of visible text renders at >= 12 CSS px (32 below threshold)

FIX

67% of visible text renders at >= 12 CSS px (32 below threshold)

32 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: <p> 11.0px ("The map of the internet"); <p> 11.0px ("Featured routes"); <span> 11.0px ("01"); <span> 11.0px ("Business & Startups"); <span> 11.0px ("02").

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.

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 WebAtlas — The Map of the Internet ✓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

h1 What are you trying

1.11:1

#000000

#130F1E

needs 3.0:1 (large text)

32px · above the fold

h2 Start somewhere real

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Thirty regions of the internet, drawn ar…

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Google asks what you are searching for.

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Start a small business in 30 days

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Master playing guitar as a complete begi…

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get started with astrophysics in 30 days

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Learn getting a dog as a complete beginn…

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Master neural networks in 30 days

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get started with english as a complete b…

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Start solo travel in 30 days

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Master video games as a complete beginne…

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Fund injection moulding in 30 days

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Software & Engineering

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI & Data

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Design

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Business & Startups

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Marketing & Growth

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Money & Finance

1.08:1

#000000

#080D16

needs 3.0:1 (large text)

19px · bottom of viewport

title WebAtlas — The Map of the Internet

2.47:1

#000000

#205170

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 What are you trying	1.11:1	3.0:1	#000000	#130F1E	Fail
h2 Start somewhere real	1.08:1	3.0:1	#000000	#080D16	Fail
h2 Thirty regions of th…	1.08:1	3.0:1	#000000	#080D16	Fail
h2 Google asks what you…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Start a small busine…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Master playing guita…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Get started with ast…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Learn getting a dog …	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Master neural networ…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Get started with eng…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Start solo travel in…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Master video games a…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Fund injection mould…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Software & Engineeri…	1.08:1	3.0:1	#000000	#080D16	Fail
h3 AI & Data	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Design	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Business & Startups	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Marketing & Growth	1.08:1	3.0:1	#000000	#080D16	Fail
h3 Money & Finance	1.08:1	3.0:1	#000000	#080D16	Fail
title WebAtlas — The Map…	2.47:1	4.5:1	#000000	#205170	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.

Landmark Structure

4 landmarks

PASS

4 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

A+

Heading Hierarchy

19 headings

PASS

19 headings

Single H1 present

H1 What are you tryingto accomplish?
H2 Start somewhere real
H3 Start a small business in 30 days
H3 Master playing guitar as a complete beginner
H3 Get started with astrophysics in 30 days
H3 Learn getting a dog as a complete beginner
H3 Master neural networks in 30 days
H3 Get started with english as a complete beginner
H3 Start solo travel in 30 days
H3 Master video games as a complete beginner
H3 Fund injection moulding in 30 days
H2 Thirty regions of the internet, drawn around what people actually do
H3 Software & Engineering
H3 AI & Data
H3 Design
H3 Business & Startups
H3 Marketing & Growth
H3 Money & Finance
H2 Google asks what you are searching for.We ask where you are going.

A+

Heading Text Quality

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

PASS

All 19 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
input	input	Describe your goal	aria-label

A+

Link & Button Quality

34 links, 8 buttons — all OK

PASS

34 links, 8 buttons — all OK

34 link(s) with descriptive text

34 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

42 links and buttons have descriptive text

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

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+

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+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 21 passed

PASS

100

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.

○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

●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

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

●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

●Document has a main landmark.

●Elements with visible text labels have matching accessible names.

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

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

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