Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

Landmark Structure

Action

3 landmarks

FIX

3 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

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

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

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

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://soup.io/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://soup.io/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #dd3333

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 ModePartial Dark Mode

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

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Heading Hierarchy

20 headings, 1 skip(s)

REVIEW

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H2 Zootpia: Dominates Disney+ Viewership Trends
H2 Daniel Documentary: HBO’s New Documentary Experience
H2 Big Mouth Show: Animated Mating Season Adventures
H2 Norristown Juvenile Delinquency and Expungement Options
H2 7 Secrets to Better-Tasting Low-Sugar Cherry Gummies
H2 How I Got a Windows 11 Pro KEY for a Low Price!
H2 Official Jayaslot App Download for Android and iOS Indonesia
H2 Best Medical Coverage Insurance: How to Compare Plans and Choose the Right One
H4 Mixed List skipped
H2 Bergenfield Car Accident Lawyer
H2 Severance Awards: Severance and The Penguin Lead the Charge
H2 Yankees Network: YES Network Joins Forces
H2 Outfit Toy Story: Insights from Fandango Feedback
H2 Arc Network Token Launch: Circle’s Move Signals Fresh Chapter in RWA Evolution
H2 How the Kado Bar Rizz Fits into a Modern Wellness Routine: Convenience Without Compromise
H2 Building a Secure Online Payment Platform for Modern Commerce
H2 Why So Many Meta Employees Leave 401k Match Money on the Table
H2 Tax planning strategies for NRIs with income in India
H3 Subscribe to Updates

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Form Accessibility

Action

3 of 4 controls have issues

REVIEW

3 of 4 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email" name="EMAIL">; <input type="search" name="s">

1 control(s) properly labeled

4 controls

1 labeled

2 placeholder only

1 unlabeled

Control	Type	Label	Method
privacy	checkbox		none
EMAIL	email	(Your email address..)	placeholder only
s	search	(Search...)	placeholder only
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA

a Business

4.42:1

#000000

#70737A

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span X (Twitter)

3.94:1

#000000

#6C6B67

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Instagram

1.90:1

#000000

#443A33

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Contact Us

4.37:1

#000000

#577970

needs 4.5:1 (normal text)

16px · above the fold

a Write For Us

3.71:1

#000000

#4F6D65

needs 4.5:1 (normal text)

16px · above the fold

a Guest Post

2.57:1

#000000

#515040

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

a About Us

1.43:1

#000000

#1F2B28

needs 4.5:1 (normal text)

16px · mid-page

4 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
h3 Subscribe to Updates	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Soup.io	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Close Menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	16.14:1	4.5:1	#000000	#D6E3F3	Pass
a News	17.12:1	4.5:1	#000000	#DFE9F6	Pass
a Technology	9.83:1	4.5:1	#000000	#A7B3BE	Pass
a Business	4.42:1	4.5:1	#000000	#70737A	Fail
a Entertainment	8.05:1	4.5:1	#000000	#A1A0A0	Pass
a Science / Health	13.08:1	4.5:1	#000000	#A1D8BE	Pass
span Facebook	10.43:1	4.5:1	#000000	#ADBAB0	Pass
span X (Twitter)	3.94:1	4.5:1	#000000	#6C6B67	Fail
span Instagram	1.90:1	4.5:1	#000000	#443A33	Fail
a Contact Us	4.37:1	4.5:1	#000000	#577970	Fail
a Write For Us	3.71:1	4.5:1	#000000	#4F6D65	Fail
a Guest Post	2.57:1	4.5:1	#000000	#515040	Fail
a About Us	1.43:1	4.5:1	#000000	#1F2B28	Fail
a Terms of Service	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Facebook	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span X (Twitter)	21.00:1	4.5: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+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

Link & Button Quality

111 links, 4 buttons — all OK

PASS

111 links, 4 buttons — all OK

11 link(s) open in new tab without warning

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

Got: #; #; #; #; #; #; ; ; ; (+1 more)

100 link(s) with descriptive text

111 links

0 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	Facebook	new tab	Add '(opens in new tab)' to text
#	X (Twitter)	new tab	Add '(opens in new tab)' to text
#	Instagram	new tab	Add '(opens in new tab)' to text
#	Facebook	new tab	Add '(opens in new tab)' to text
#	X (Twitter)	new tab	Add '(opens in new tab)' to text
#	Instagram	new tab	Add '(opens in new tab)' to text
	Facebook	new tab	Add '(opens in new tab)' to text
	Twitter	new tab	Add '(opens in new tab)' to text
	Youtube	new tab	Add '(opens in new tab)' to text
	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.soup.io/news/feed/gn	Rss	new tab	Add '(opens in new tab)' to text

104 links and buttons have descriptive text

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

#; #; #; #; #; #; ; ; ; (+1 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

Lighthouse Accessibility Audits

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

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
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 22, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 22, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 22, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
April 22, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 22, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 21, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 21, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 21, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 21, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 21, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 21, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`
By `div.post-meta > div.post-meta-items > span.meta-item > span.by`
April 21, 2026 `div.post-meta-items > span.meta-item > span.date-link > time.post-date`

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
Mixed List `div.elementor-widget-container > section.block-wrap > div.block-head > h4.heading`

These are opportunities to improve keyboard navigation in your application.

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.s-light `html.s-light`

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-*]` attributes match their 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

●Input buttons have discernible text.

●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

●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

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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 type="image">` elements have `[alt]` text

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

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