Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 5 REVIEW 8 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Tap Target Adequacy

Action

12 tap target(s) too small or too close together

FIX

12 tap target(s) too small or too close together

12 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

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

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://swappz.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://swappz.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 ✗

Alt Text Quality

Action

27 of 52 images have issues

REVIEW

27 of 52 images have issues

27 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

21 decorative image(s) correctly marked

4 image(s) with good alt text

52 images 4 good alt text 21 decorative 27 missing

Issue	Count
missing	27 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

Link & Button Quality

Action

5 issue(s) across 216 links and 27 buttons

REVIEW

5 issue(s) across 216 links and 27 buttons

5 link(s) with no accessible text

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

Got: https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…; https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…; https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…; https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…; https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…

17 link(s) open in new tab without warning

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

Got: //www.paperstreetcash.com; //www.psmhelp.com/content-removal; //www.psmhelp.com/tos; //www.psmhelp.com/complaints; //www.psmhelp.com/dmca; //www.psmhelp.com/anti-trafficking; //www.psmhelp.com/faq; //www.psmhelp.com/; //www.psmhelp.com/refund; //www.psmhelp.com/technicalsupport (+7 more)

194 link(s) with descriptive text

216 links

5 empty

0 generic text

17 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/series/premium	REPTYLE	img no alt	Add alt attribute to the image
/series/premium	REPTYLE	img no alt	Add alt attribute to the image
https://psmads.psmcode.com/delivery/ck.p…	(empty)	empty	Add link text or aria-label
https://psmads.psmcode.com/delivery/ck.p…	(empty)	empty	Add link text or aria-label
https://psmads.psmcode.com/delivery/ck.p…	(empty)	empty	Add link text or aria-label
https://psmads.psmcode.com/delivery/ck.p…	(empty)	empty	Add link text or aria-label
https://psmads.psmcode.com/delivery/ck.p…	(empty)	empty	Add link text or aria-label
//www.paperstreetcash.com	WEBMASTERS	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/content-removal	CONTENT REMOVAL	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/tos	TERMS	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/complaints	COMPLAINTS	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/dmca	DMCA	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/anti-trafficking	TRUST & SAFETY	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/faq	F.A.Q	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/	HELP	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/refund	REFUND POLICY	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/technicalsupport	TECHNICAL	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/privacy	PRIVACY POLICY	new tab	Add '(opens in new tab)' to text
https://psmhelp.com/billingsupport	SUPPORT	new tab	Add '(opens in new tab)' to text
//x.com/SwappzNetwork	follow-us	new tab	Add '(opens in new tab)' to text
//www.instagram.com/swappznetwork	follow-us	new tab	Add '(opens in new tab)' to text
//www.psmhelp.com/section2257	18 U.S.C. § 2257 Record-Keepi…	new tab	Add '(opens in new tab)' to text
https://www.psmhelp.com/cookies	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

221 links and buttons have descriptive text

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

https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…; https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…; https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…; https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…; https://psmads.psmcode.com/delivery/ck.php?nats=MTc4MjIuMTA0NzIuMjAyLjY2MTkuM…

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

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

//www.paperstreetcash.com; //www.psmhelp.com/content-removal; //www.psmhelp.com/tos; //www.psmhelp.com/complaints; //www.psmhelp.com/dmca; //www.psmhelp.com/anti-trafficking; //www.psmhelp.com/faq; //www.psmhelp.com/; //www.psmhelp.com/refund; //www.psmhelp.com/technicalsupport (+7 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

Mobile-Readable Font Sizes

99% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

99% of visible text renders at >= 12 CSS px (2 below threshold)

2 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: <h3> 10.0px ("By clicking “I Agree” below, you state t..."); <p> 10.0px ("If you disagree with the above, click on...").

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 Official Swappz Porn Network

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Official Swappz Porn Network

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Upcoming & Latest Videos

1.00:1

#000000

needs 3.0:1 (large text)

24px · mid-page

h2 Popular Videos

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Daughter Swap

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sis Swap

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Mom Swap

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 OUR SERIES

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest Models

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Popular Models

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 At Swappz…Everyone Gets a Turn

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 At Swappz…Everyone Gets a Turn

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 By clicking “I Agree” below, you sta…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title Swappz Porn Site (OFFICIAL) | Swappz.com

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Videos

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a REPTYLE

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Models

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Series

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Join Now

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Join

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Official Swappz Porn…	1.00:1	3.0:1	#000000	#000000	Fail
h1 Official Swappz Porn…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Upcoming & Latest Vi…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Popular Videos	1.00:1	3.0:1	#000000	#000000	Fail
h2 Daughter Swap	1.00:1	3.0:1	#000000	#000000	Fail
h2 Sis Swap	1.00:1	3.0:1	#000000	#000000	Fail
h2 Mom Swap	1.00:1	3.0:1	#000000	#000000	Fail
h2 OUR SERIES	1.00:1	3.0:1	#000000	#000000	Fail
h2 Latest Models	1.00:1	3.0:1	#000000	#000000	Fail
h2 Popular Models	1.00:1	3.0:1	#000000	#000000	Fail
h2 At Swappz…Everyone…	1.00:1	3.0:1	#000000	#000000	Fail
h2 At Swappz…Everyone…	1.00:1	3.0:1	#000000	#000000	Fail
h3 By clicking “I Agr…	1.00:1	3.0:1	#000000	#000000	Fail
title Swappz Porn Site (OF…	1.00:1	4.5:1	#000000	#000000	Fail
a Videos	1.00:1	4.5:1	#000000	#000000	Fail
a REPTYLE	1.00:1	4.5:1	#000000	#000000	Fail
a Models	1.00:1	4.5:1	#000000	#000000	Fail
a Series	1.00:1	4.5:1	#000000	#000000	Fail
div Join Now	1.00:1	4.5:1	#000000	#000000	Fail
div Join	1.00:1	4.5:1	#000000	#000000	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

Score 81/100 — 4 failing, 19 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 `div.header-wrapper > div.right-menu > a.join-button-nav > div.mobile`
JOIN NOW `div.d-inline > a.mx-auto > div > button.btn`
JOIN NOW `div.col > a.mx-auto > div > button.btn`
Cookie `div#cookie-bar-container > div.cookie-text > div > a`
Data Privacy `div#cookie-bar-container > div.cookie-text > div > a`
Got it `div > div#cookie-bar-container > div.cookie-button > button#cookie-dismiss-button`
I AGREE - ENTER `div.age-verification-description > div.description-wrapper > div.dismiss-modal-btn-container > button#enter-verification-btn`

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.ts-organic > div.footerWrapper > div.rta-logo > img `div.ts-organic > div.footerWrapper > div.rta-logo > img`
div.age-verification-description > div.description-wrapper > div.age-verification-logo > img `div.age-verification-description > div.description-wrapper > div.age-verification-logo > img`
body > img `body > 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
ul.slider > li.slide > div.img-slider > a.join-link `ul.slider > li.slide > div.img-slider > a.join-link`
ul.slider > li.slide > div.img-slider > a.join-link `ul.slider > li.slide > div.img-slider > a.join-link`
div.ts-organic > div > div.spot > a.join-link `div.ts-organic > div > div.spot > a.join-link`
ul.slider > li.slide > div.img-slider > a.join-link `ul.slider > li.slide > div.img-slider > a.join-link`
ul.slider > li.slide > div.img-slider > a.join-link `ul.slider > li.slide > div.img-slider > 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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JOIN NOW `div.container > div.row > div.d-inline > a.mx-auto`
WEBMASTERS `div.row > div.col-lg-3 > div.service-entry > a.text-white`
CONTENT REMOVAL `div.row > div.col-lg-3 > div.service-entry > a.text-white`
TERMS `div.row > div.col-lg-3 > div.service-entry > a.text-white`
COMPLAINTS `div.row > div.col-lg-3 > div.service-entry > a.text-white`
DMCA `div.row > div.col-lg-3 > div.service-entry > a.text-white`
TRUST & SAFETY `div.row > div.col-lg-3 > div.service-entry > a.text-white`
F.A.Q `div.row > div.col-lg-3 > div.service-entry > a.text-white`
HELP `div.row > div.col-lg-3 > div.service-entry > a.text-white`
REFUND POLICY `div.row > div.col-lg-3 > div.service-entry > a.text-white`
TECHNICAL `div.row > div.col-lg-3 > div.service-entry > a.text-white`
PRIVACY POLICY `div.row > div.col-lg-3 > div.service-entry > a.text-white`

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

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

●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

●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

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Identical links have the same purpose.

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

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

Heading Hierarchy

13 headings

PASS

13 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H2 Upcoming & Latest Videos
H2 Popular Videos
H2 Daughter Swap
H2 Sis Swap
H2 Mom Swap
H2 OUR SERIES
H2 Latest Models
H2 Popular Models
H1 Official Swappz Porn Network
H2 At Swappz…Everyone Gets a Turn
H1 Official Swappz Porn Network duplicate H1
H2 At Swappz…Everyone Gets a Turn
H3 By clicking “I Agree” below, you state that the following statements are accurate:

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

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

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

PASS

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

No tabindex anti-patterns detected

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+

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.