Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 2 REVIEW 9 FIX

Landmark Structure

Action

4 landmarks

FIX

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

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

Mobile-Readable Font Sizes

Action

33% of visible text renders at >= 12 CSS px (92 below threshold)

FIX

33% of visible text renders at >= 12 CSS px (92 below threshold)

92 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 ("by"); <span> 11.0px ("September 25, 2026"); <a> 11.0px ("Big Butts"); <a> 11.0px ("Big Tits"); <a> 11.0px ("Blonde").

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

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

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

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

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

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

Lighthouse Accessibility Audits

Action

Score 60/100 — 5 failing, 7 passed

FIX

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
The hottest place for sex role-play fantasies on the internet. `div.et_pb_module > div.et_pb_promo_description > div > p`
When you become a member of TeddyXXX you’ll receive access to exclusively made,… `div.et_pb_module > div.et_pb_promo_description > div > p`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SEGPAY.COM `div.et_pb_module > div.et_pb_text_inner > p > a`
SEGPAY.COM*FT `div.et_pb_module > div.et_pb_text_inner > p > a`

These are opportunities to improve the legibility of your content.

Names and labels

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.et_pb_row > div.et_pb_column > div.et_pb_module > a `div.et_pb_row > div.et_pb_column > div.et_pb_module > a`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Image elements have `[alt]` attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

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

○Buttons have an accessible name

○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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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

Link & Button Quality

Action

9 issue(s) across 156 links and 5 buttons

REVIEW

9 issue(s) across 156 links and 5 buttons

9 link(s) with generic text

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

Got: https://teddyxxx.com/my-hot-stepmom-danielle-needs-to-relax-with-my-hard-dick/ ("read more"); https://teddyxxx.com/lazy-cute-renters-vivienne-vo-and-ryder-rey-have-to-fuck… ("read more"); https://teddyxxx.com/busty-redhead-milf-jessica-wants-to-help-me-get-more-girls/ ("read more"); https://teddyxxx.com/hot-slutty-babe-sisi-rose-fucks-with-a-big-facial-on-her… ("read more"); https://teddyxxx.com/shy-nerdy-stepsis-is-back-from-college-and-needs-some-bi… ("read more"); https://teddyxxx.com/sexy-french-maid-sisi-rose-gets-fucked-on-top-of-the-kit… ("read more"); https://teddyxxx.com/sexy-street-walker-gets-fucked-in-the-rolls-willow-ryder/ ("read more"); https://teddyxxx.com/sexual-freak-jc-wilds-gets-fucked-late-night-sharing-a-b… ("read more"); https://teddyxxx.com/sophie-tyler-gets-fucked-by-her-new-management/ ("read more")

4 link(s) open in new tab without warning

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

Got: http://cs.segpay.com/; http://cs.segpay.com/; http://cs.segpay.com/; https://wyldesites.com

143 link(s) with descriptive text

156 links

0 empty

9 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
http://cs.segpay.com/	Billing & Support	new tab	Add '(opens in new tab)' to text
http://cs.segpay.com/	Billing & Support	new tab	Add '(opens in new tab)' to text
https://teddyxxx.com/my-hot-stepmom-dani…	read more	generic text	Replace with descriptive text
Before: read more Suggested: My Hot Stepmom Danielle Needs To Relax With My Hard Dick
https://teddyxxx.com/lazy-cute-renters-v…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Lazy Cute Renters Vivienne Vo And Ryder Rey Have To Fuck Landlord
https://teddyxxx.com/busty-redhead-milf-…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Busty Redhead Milf Jessica Wants To Help Me Get More Girls
https://teddyxxx.com/hot-slutty-babe-sis…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Hot Slutty Babe Sisi Rose Fucks With A Big Facial On Her Face Double Cumshot
https://teddyxxx.com/shy-nerdy-stepsis-i…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Shy Nerdy Stepsis Is Back From College And Needs Some Big Dick Experience Charlotte Mae
https://teddyxxx.com/sexy-french-maid-si…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Sexy French Maid Sisi Rose Gets Fucked On Top Of The Kitchen Counter
https://teddyxxx.com/sexy-street-walker-…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Sexy Street Walker Gets Fucked In The Rolls Willow Ryder
https://teddyxxx.com/sexual-freak-jc-wil…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Sexual Freak Jc Wilds Gets Fucked Late Night Sharing A Bed With Stepbro
https://teddyxxx.com/sophie-tyler-gets-f…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Sophie Tyler Gets Fucked By Her New Management
http://cs.segpay.com/	Billing & Support	new tab	Add '(opens in new tab)' to text
https://wyldesites.com	Wyldesites, Inc.	new tab	Add '(opens in new tab)' to text

148 links and buttons have descriptive text

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

https://teddyxxx.com/my-hot-stepmom-danielle-needs-to-relax-with-my-hard-dick/ ("read more"); https://teddyxxx.com/lazy-cute-renters-vivienne-vo-and-ryder-rey-have-to-fuck… ("read more"); https://teddyxxx.com/busty-redhead-milf-jessica-wants-to-help-me-get-more-girls/ ("read more"); https://teddyxxx.com/hot-slutty-babe-sisi-rose-fucks-with-a-big-facial-on-her… ("read more"); https://teddyxxx.com/shy-nerdy-stepsis-is-back-from-college-and-needs-some-bi… ("read more"); https://teddyxxx.com/sexy-french-maid-sisi-rose-gets-fucked-on-top-of-the-kit… ("read more"); https://teddyxxx.com/sexy-street-walker-gets-fucked-in-the-rolls-willow-ryder/ ("read more"); https://teddyxxx.com/sexual-freak-jc-wilds-gets-fucked-late-night-sharing-a-b… ("read more"); https://teddyxxx.com/sophie-tyler-gets-fucked-by-her-new-management/ ("read more")

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.

http://cs.segpay.com/; http://cs.segpay.com/; http://cs.segpay.com/; https://wyldesites.com

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h2 Check out more of the most recent TeddyX…

1.02:1

#000000

#040404

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ADULT CONTENT - ACCESS RESTRICTED

1.02:1

#000000

#040404

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Join TeddyXXX Today!

1.02:1

#000000

#040404

needs 3.0:1 (large text)

19px · bottom of viewport

title TeddyXXX

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Billing & Support

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Get Help

1.07:1

#000000

#0D0A0B

needs 4.5:1 (normal text)

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

a LOGIN

1.25:1

#000000

#281920

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.22:1

#000000

#27161C

needs 4.5:1 (normal text)

16px · above the fold

a Categories

1.17:1

#000000

#23121A

needs 4.5:1 (normal text)

16px · above the fold

a JOIN NOW!

1.24:1

#000000

#2B171E

needs 4.5:1 (normal text)

16px · above the fold

span Select Page

1.22:1

#000000

#28151D

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.20:1

#000000

#26141C

needs 4.5:1 (normal text)

16px · above the fold

a Categories

1.19:1

#000000

#26131C

needs 4.5:1 (normal text)

16px · above the fold

a JOIN NOW!

1.19:1

#000000

#25131C

needs 4.5:1 (normal text)

16px · above the fold

a Billing & Support

1.20:1

#000000

#25151E

needs 4.5:1 (normal text)

16px · above the fold

a Get Help

1.14:1

#000000

#1E0F17

needs 4.5:1 (normal text)

16px · above the fold

a LOGIN

1.22:1

#000000

#27171A

needs 4.5:1 (normal text)

16px · mid-page

span Video Player

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

span 00:01

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

1 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
h1 Welcome to TeddyXXX!	7.83:1	3.0:1	#F96EC0	#040404	Pass
h2 Check out more of th…	1.02:1	3.0:1	#000000	#040404	Fail
h2 ADULT CONTENT - ACCE…	1.02:1	3.0:1	#000000	#040404	Fail
h3 Join TeddyXXX Today!	1.02:1	3.0:1	#000000	#040404	Fail
title TeddyXXX	1.00:1	4.5:1	#000000	#000000	Fail
a Billing & Support	1.00:1	4.5:1	#000000	#000000	Fail
a Get Help	1.07:1	4.5:1	#000000	#0D0A0B	Fail
a LOGIN	1.25:1	4.5:1	#000000	#281920	Fail
a Home	1.22:1	4.5:1	#000000	#27161C	Fail
a Categories	1.17:1	4.5:1	#000000	#23121A	Fail
a JOIN NOW!	1.24:1	4.5:1	#000000	#2B171E	Fail
span Select Page	1.22:1	4.5:1	#000000	#28151D	Fail
a Home	1.20:1	4.5:1	#000000	#26141C	Fail
a Categories	1.19:1	4.5:1	#000000	#26131C	Fail
a JOIN NOW!	1.19:1	4.5:1	#000000	#25131C	Fail
a Billing & Support	1.20:1	4.5:1	#000000	#25151E	Fail
a Get Help	1.14:1	4.5:1	#000000	#1E0F17	Fail
a LOGIN	1.22:1	4.5:1	#000000	#27171A	Fail
span Video Player	1.02:1	4.5:1	#000000	#040404	Fail
span 00:01	1.02:1	4.5:1	#000000	#040404	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

16 headings

PASS

16 headings

Single H1 present

H2 My Hot StepMom Danielle Needs to Relax with My Hard Dick
H2 Sexy French Maid Sisi Rose Gets Fucked on Top of the Kitchen Counter
H2 Lazy Cute Renters Vivienne Vo and Ryder Rey Have to Fuck Landlord
H1 Welcome to TeddyXXX!
H2 Check out more of the most recent TeddyXXX video updates:
H2 My Hot StepMom Danielle Needs to Relax with My Hard Dick
H2 Lazy Cute Renters Vivienne Vo and Ryder Rey Have to Fuck Landlord
H2 Busty Redhead MILF Jessica Wants to Help Me Get More Girls
H2 Hot Slutty Babe Sisi Rose Fucks with a Big Facial on Her Face – Double Cumshot
H2 Shy Nerdy Stepsis is Back From College and Needs Some Big Dick Experience – Charlotte Mae
H2 Sexy French Maid Sisi Rose Gets Fucked on Top of the Kitchen Counter
H2 Sexy Street Walker Gets Fucked in the Rolls – Willow Ryder
H2 Sexual Freak JC Wilds Gets Fucked Late Night Sharing a Bed with StepBro
H2 Sophie Tyler Gets Fucked by her New Management
H3 Join TeddyXXX Today!
H2 ADULT CONTENT - ACCESS RESTRICTED

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+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

3 decorative image(s) correctly marked

10 image(s) with good alt text

13 images 10 good alt text 3 decorative

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search" name="s">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
s	search	(Search …)	placeholder only

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

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-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

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

PASS

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

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