Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 4 REVIEW 8 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

No contentinfo (footer) 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

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

Link & Button Quality

Action

6 issue(s) across 45 links and 1 buttons

FIX

6 issue(s) across 45 links and 1 buttons

5 link(s) with no accessible text

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

Got: https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…; https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…; https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…; https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…; https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.psmhelp.com/section2257 ("Click Here")

16 link(s) open in new tab without warning

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

Got: https://www.psmhelp.com/section2257; https://www.psmhelp.com/tos; https://www.psmhelp.com/privacy; https://www.psmhelp.com/refund; https://www.psmhelp.com/faq; https://www.psmhelp.com/technicalsupport; https://www.psmhelp.com; https://www.psmhelp.com/billingsupport; https://www.paperstreetcash.com/; https://www.psmhelp.com/content-removal (+6 more)

23 link(s) with descriptive text

45 links

5 empty

1 generic text

16 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://join.freeuse.com/track/MTc4MjIuM…	(empty)	empty	Add link text or aria-label
https://join.freeuse.com/track/MTc4MjIuM…	(empty)	empty	Add link text or aria-label
https://join.freeuse.com/track/MTc4MjIuM…	(empty)	empty	Add link text or aria-label
https://join.freeuse.com/track/MTc4MjIuM…	(empty)	empty	Add link text or aria-label
https://join.freeuse.com/track/MTc4MjIuM…	(empty)	empty	Add link text or aria-label
https://www.psmhelp.com/section2257	2257	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/tos	TERMS	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/privacy	PRIVACY POLICY	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/refund	REFUND POLICY	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/faq	F.A.Q.'S	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/technicalsupport	HELP	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com	CUSTOMER SERVICE	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/billingsupport	BILLING SUPPORT	new tab	Add '(opens in new tab)' to text
https://www.paperstreetcash.com/	WEBMASTERS	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/content-removal	CONTENT REMOVAL	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/complaints	COMPLAINTS	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/dmca	DMCA	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/anti-trafficking	TRUST & SAFETY	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/section2257	Click Here	generic text	Replace with descriptive text
Before: Click Here Suggested: Section2257
https://www.psmhelp.com/section2257	18 U.S.C. 2257 Record-Keeping …	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/cookie-policy	Cookie	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/privacy	Data Privacy	new tab	Add '(opens in new tab)' to text

24 links and buttons have descriptive text

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

https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…; https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…; https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…; https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…; https://join.freeuse.com/track/MTc4MjIuMTA0NzIuMjA0LjY2MjYuMC4wLjAuMC4w/join?…

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

Generic link text like 'click here' doesn't describe the destination.

https://www.psmhelp.com/section2257 ("Click Here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.psmhelp.com/section2257; https://www.psmhelp.com/tos; https://www.psmhelp.com/privacy; https://www.psmhelp.com/refund; https://www.psmhelp.com/faq; https://www.psmhelp.com/technicalsupport; https://www.psmhelp.com; https://www.psmhelp.com/billingsupport; https://www.paperstreetcash.com/; https://www.psmhelp.com/content-removal (+6 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

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-9lmgqa

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://freeusefuck.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://freeusefuck.com/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.

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Alt Text Quality

2 of 5 images have issues

REVIEW

2 of 5 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image(s) with good alt text

5 images 3 good alt text 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 4 pass AA only

title Freeuse Network - Join Today!

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Full Videos

2.20:1

#000000

#564040

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Join Now

1.82:1

#FFFFFF

#DBB9AD

needs 4.5:1 (normal text)

16px · above the fold

a Join Now

3.02:1

#FFFFFF

#B08C8A

needs 4.5:1 (normal text)

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

a 2257

1.23:1

#000000

#171150

needs 4.5:1 (normal text)

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

a TERMS

1.47:1

#000000

#3E1758

needs 4.5:1 (normal text)

16px · mid-page

a PRIVACY POLICY

1.35:1

#000000

#321F22

needs 4.5:1 (normal text)

16px · mid-page

a F.A.Q.'S

3.96:1

#000000

#8C6157

needs 4.5:1 (normal text)

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

a HELP

1.09:1

#000000

#130D0A

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
title Freeuse Network - Jo…	1.00:1	4.5:1	#000000	#000000	Fail
a Full Videos	2.20:1	4.5:1	#000000	#564040	Fail
a Top Pornstars	12.24:1	4.5:1	#000000	#EEC03E	Pass
a All sites	11.28:1	4.5:1	#000000	#DEBB3A	Pass
a Login	10.61:1	4.5:1	#000000	#D3B1A6	Pass
a Join Now	1.82:1	4.5:1	#FFFFFF	#DBB9AD	Fail
a Full Videos	11.30:1	4.5:1	#000000	#D9B7AA	Pass
a Top Pornstars	7.07:1	4.5:1	#000000	#B38F6D	Pass
a All sites	10.69:1	4.5:1	#000000	#B5BE88	Pass
a Login	5.97:1	4.5:1	#000000	#A88160	Pass
a Join Now	4.78:1	4.5:1	#FFFFFF	#956949	Pass
a Join Now	3.02:1	4.5:1	#FFFFFF	#B08C8A	Fail
a ...	6.61:1	4.5:1	#000000	#B0877E	Pass
span Get Access Now!	18.32:1	4.5:1	#FFFFFF	#100A43	Pass
a 2257	1.23:1	4.5:1	#000000	#171150	Fail
a TERMS	1.47:1	4.5:1	#000000	#3E1758	Fail
a PRIVACY POLICY	1.35:1	4.5:1	#000000	#321F22	Fail
a REFUND POLICY	5.76:1	4.5:1	#000000	#92837D	Pass
a F.A.Q.'S	3.96:1	4.5:1	#000000	#8C6157	Fail
a HELP	1.09:1	4.5:1	#000000	#130D0A	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.

Lighthouse Accessibility Audits

Action

Score 75/100 — 4 failing, 12 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
JOIN NOW `div.pin > div#pinWrapper > div.header > a#joinLinkButtonRight`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#pinWrapper > div > div > img `div#pinWrapper > div > div > img`
div.nextgen-col > div#gridBody > a#grid-1 > img `div.nextgen-col > div#gridBody > a#grid-1 > img`
div.nextgen-col > div#gridBody > a#grid-1 > img `div.nextgen-col > div#gridBody > a#grid-1 > img`
div.nextgen-col > div#gridBody > a#grid-2 > img `div.nextgen-col > div#gridBody > a#grid-2 > img`
div.nextgen-col > div#gridBody > a#grid-2 > img `div.nextgen-col > div#gridBody > a#grid-2 > img`
div.nextgen-col > div#gridBody > a#grid-3 > img `div.nextgen-col > div#gridBody > a#grid-3 > img`
div.nextgen-col > div#gridBody > a#grid-4 > img `div.nextgen-col > div#gridBody > a#grid-4 > img`
div.nextgen-col > div#gridBody > a#grid-4 > img `div.nextgen-col > div#gridBody > a#grid-4 > img`
div.nextgen-col > div#gridBody > a#grid-5 > img `div.nextgen-col > div#gridBody > a#grid-5 > img`
div.nextgen-col > div#gridBody > a#grid-5 > img `div.nextgen-col > div#gridBody > a#grid-5 > img`
div.nextgen-col > div#gridBody > a#grid-6 > img `div.nextgen-col > div#gridBody > a#grid-6 > img`
div#bottom-content > div > div.rta-logo > img `div#bottom-content > div > div.rta-logo > img`

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#root > div.pin > div#pinWrapper > a#mobile-video-banner-join-link `div#root > div.pin > div#pinWrapper > a#mobile-video-banner-join-link`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-1 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-1`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-2 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-2`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-3 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-3`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-4 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-4`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-5 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-5`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-6 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-6`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-7 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-7`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-8 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-8`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-9 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-9`
div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-10 `div.nextgen-row > div.nextgen-col > div#gridBody > a#grid-10`
div.pagination-div > ul > li.l > a.join-link `div.pagination-div > ul > li.l > a.join-link`
div.pagination-div > ul > li.r > a.join-link `div.pagination-div > ul > li.r > a.join-link`

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.

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

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-hidden="true"]` is not present on the document `<body>`

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

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

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

●The page contains a heading, skip link, or landmark region

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

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

○Heading elements appear in a sequentially-descending order

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

○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

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

A+

Heading Text Quality

No headings to evaluate -- check is N/A

PASS

No headings to evaluate -- check is N/A

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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

PASS

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

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

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.