Accessibility

F

Heading Hierarchy

Action

33 headings, 8 skip(s)

FIX

33 headings, 8 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.

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H3 Welcome to
H2 Top Scenes
H2 Featured Scenes
H2 Featured Models
H4 Freya Von Doom skipped
H4 Eva Nyx
H4 Elana Bunnz
H4 Maddie Wren
H4 Liv Revamped
H4 Aria Sloane
H4 Chloe Amour
H4 Luna Legend
H2 Latest Inserted Scenes
H1 Luna's Backdoor Bash
H4 Model: Luna Legend skipped
H2 A Face Full Of Fun For Christina
H4 Model: Christina Sage skipped
H2 Odessa Has A Slutty Streak
H4 Model: Odessa Bell skipped
H2 Alina's Mouth Feels Good
H4 Model: Alina Voss skipped
H2 Mandii's Pussy Has The Grip
H4 Model: Mandii Rose skipped
H2 Alana's Tight Little Tease
H4 Model: Alana Rose skipped
H4 INCLUDED IN YOUR MEMBERSHIP
H6 HOME skipped
H6 VIDEOS
H6 MODELS
H6 PRE-SALE
H6 LOGIN
H4 powered by PAYSITE.com
H3 Terms and Conditions

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

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

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

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

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

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

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

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

F

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

D

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D

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: #ffffff

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 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

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

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.

C

Landmark Structure

Action

5 landmarks

REVIEW

5 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

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

C

Link & Button Quality

Action

2 issue(s) across 66 links and 37 buttons

REVIEW

2 issue(s) across 66 links and 37 buttons

2 link(s) with no accessible text

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

Got: https://x.com/InsertedXXX; https://www.instagram.com/Inserted_officialcom

13 link(s) open in new tab without warning

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

Got: /support; https://secured.customercare.com/contact/rc/ist; https://radicalcash.com/; https://customercare.co/terms; https://customercare.co/terms#privacy; https://customercare.co/complaints; https://customercare.co/content-removal; https://paysite.com/; https://www.epoch.com/; https://cs.segpay.com/ (+3 more)

51 link(s) with descriptive text

66 links

2 empty

0 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://x.com/InsertedXXX	(empty)	empty	Add link text or aria-label
https://www.instagram.com/Inserted_offic…	(empty)	empty	Add link text or aria-label
/support	CUSTOMER SUPPORT	new tab	Add '(opens in new tab)' to text
https://secured.customercare.com/contact…	BILLING SUPPORT	new tab	Add '(opens in new tab)' to text
https://radicalcash.com/	WEBMASTERS	new tab	Add '(opens in new tab)' to text
https://customercare.co/terms	TERMS & CONDITIONS	new tab	Add '(opens in new tab)' to text
https://customercare.co/terms#privacy	PRIVACY POLICY	new tab	Add '(opens in new tab)' to text
https://customercare.co/complaints	COMPLAINT POLICY	new tab	Add '(opens in new tab)' to text
https://customercare.co/content-removal	CONTENT REMOVAL	new tab	Add '(opens in new tab)' to text
https://paysite.com/	PAYSITE.com	new tab	Add '(opens in new tab)' to text
https://www.epoch.com/	Epoch	new tab	Add '(opens in new tab)' to text
https://cs.segpay.com/	Segpay	new tab	Add '(opens in new tab)' to text
/2257	18 U.S.C. 2257 Record Keeping …	new tab	Add '(opens in new tab)' to text
https://www.rtalabel.org/	RTA	new tab	Add '(opens in new tab)' to text
https://www.rtalabel.org/	RTA	new tab	Add '(opens in new tab)' to text

88 links and buttons have descriptive text

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

https://x.com/InsertedXXX; https://www.instagram.com/Inserted_officialcom

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.

/support; https://secured.customercare.com/contact/rc/ist; https://radicalcash.com/; https://customercare.co/terms; https://customercare.co/terms#privacy; https://customercare.co/complaints; https://customercare.co/content-removal; https://paysite.com/; https://www.epoch.com/; https://cs.segpay.com/ (+3 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

C

Tap Target Adequacy

Action

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

REVIEW

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

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

C

Mobile-Readable Font Sizes

Action

83% of visible text renders at >= 12 CSS px (16 below threshold)

REVIEW

83% of visible text renders at >= 12 CSS px (16 below threshold)

16 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: <h4> 11.0px ("powered by"); <span> 11.0px ("PAYSITE.com"); <a> 11.0px ("Epoch"); <p> 11.0px ("and"); <a> 11.0px ("Segpay").

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | Inserted ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

C

Favicon & Branding

Action

7 icon(s) detected

REVIEW

7 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

h2 Scenes

1.41:1

#000000

on

#352224

needs 3.0:1 (large text)

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

h2 Featured

1.02:1

#000000

on

#040303

needs 3.0:1 (large text)

24px · mid-page

h2 Latest

1.02:1

#000000

on

#040404

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Scenes

1.02:1

#000000

on

#040404

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Terms and Conditions

1.02:1

#000000

on

#040404

needs 3.0:1 (large text)

19px · bottom of viewport

span Featured

4.36:1

#000000

on

#986469

needs 4.5:1 (normal text)

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

span Models

1.03:1

#000000

on

#040505

needs 4.5:1 (normal text)

16px · mid-page

span View

1.04:1

#000000

on

#070708

needs 4.5:1 (normal text)

16px · mid-page

2 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
h2 Top	9.71:1	3.0:1	#000000	#D6A4A5	Pass
h2 Scenes	1.41:1	3.0:1	#000000	#352224	Fail
h2 Featured	1.02:1	3.0:1	#000000	#040303	Fail
h2 Latest	1.02:1	3.0:1	#000000	#040404	Fail
h2 Scenes	1.02:1	3.0:1	#000000	#040404	Fail
h3 Welcome to	13.71:1	3.0:1	#000000	#EEC9BB	Pass
h3 Terms and Conditions	1.02:1	3.0:1	#000000	#040404	Fail
title Official Site of Ins…	9.31:1	4.5:1	#000000	#D798D2	Pass
span Videos	9.88:1	4.5:1	#000000	#DB9FD0	Pass
span Models	10.47:1	4.5:1	#000000	#DEA6D0	Pass
span Pre-Sale	10.75:1	4.5:1	#000000	#DFA9D3	Pass
li Keep on writing...	11.29:1	4.5:1	#000000	#E2AFD1	Pass
li Searching...	12.76:1	4.5:1	#000000	#EBBECB	Pass
span Login	14.18:1	4.5:1	#000000	#F3CBC7	Pass
span Join Now	14.60:1	4.5:1	#000000	#F5CFC3	Pass
p Where hot girls get …	11.65:1	4.5:1	#000000	#E0B8B0	Pass
span Scenes	7.92:1	4.5:1	#000000	#CE8E94	Pass
span Featured	4.36:1	4.5:1	#000000	#986469	Fail
span Models	1.03:1	4.5:1	#000000	#040505	Fail
span View	1.04:1	4.5:1	#000000	#070708	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.

C

Lighthouse Accessibility Audits

Action

Score 79/100 — 6 failing, 21 passed

REVIEW

79

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
KB Productions LLC, 8700 E. Pinnacle Peak Road, Suite 221, Scottsdale, Arizona … `div.--page > footer.mb-5 > div.copy > p.company`
START AGE VERIFICATION `div#yoti-first-column > div > div > button#ypp-age-submit`

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
FREYA VON DOOM `div.model-loop > div.card > div.model-card-info > h4`
Luna Legend `div.thumb-container > div.content-card-info > div.content-info > h4.content-models`
Christina Sage `div.thumb-container > div.content-card-info > div.content-info > h4.content-models`
Odessa Bell `div.thumb-container > div.content-card-info > div.content-info > h4.content-models`
Alina Voss `div.thumb-container > div.content-card-info > div.content-info > h4.content-models`
Mandii Rose `div.thumb-container > div.content-card-info > div.content-info > h4.content-models`
Alana Rose `div.thumb-container > div.content-card-info > div.content-info > h4.content-models`
HOME `footer.mb-5 > ul.nav > li.nav-item > h6`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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 > ul > li > img#YppAgeTourModalSVG `div > ul > li > img#YppAgeTourModalSVG`
div > ul > li > img#YppAgeTourModalSVG `div > ul > li > img#YppAgeTourModalSVG`
div > ul > li > img#YppAgeTourModalSVG `div > ul > li > img#YppAgeTourModalSVG`

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.lazy-parent > div.lazy-children > div.video-on-hover > a.img-hover `div.lazy-parent > div.lazy-children > div.video-on-hover > a.img-hover`
div.--page > footer.mb-5 > div.row > a `div.--page > footer.mb-5 > div.row > a`
div.--page > footer.mb-5 > div.row > a `div.--page > footer.mb-5 > div.row > 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

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
FREYA VON DOOM `div.card > div.model-card-info > h4 > a.model-name`
EVA NYX `div.card > div.model-card-info > h4 > a.model-name`
ELANA BUNNZ `div.card > div.model-card-info > h4 > a.model-name`
MADDIE WREN `div.card > div.model-card-info > h4 > a.model-name`
LIV REVAMPED `div.card > div.model-card-info > h4 > a.model-name`
ARIA SLOANE `div.card > div.model-card-info > h4 > a.model-name`
CHLOE AMOUR `div.card > div.model-card-info > h4 > a.model-name`
LUNA LEGEND `div.card > div.model-card-info > h4 > a.model-name`

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

○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

○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 a valid value for its `[lang]` attribute

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

○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

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

6 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: 6 all-caps heading(s)

A+

Alt Text Quality

All 59 images OK

PASS

All 59 images OK

1 decorative image(s) correctly marked

58 image(s) with good alt text

59 images 58 good alt text 1 decorative

All images have appropriate alt text.

A

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="text" name="q" id="search">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#search	text	(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 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

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+

Tabindex Anti-Patterns

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

PASS

3 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+

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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.