Skip to content
https://goonmuse.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
8
REVIEW
7
PASS
9
INFO
0
Checks
24
9 PASS 7 REVIEW 8 FIX
D
Heading Hierarchy
Action
47 headings, 3 skip(s)
FIX
47 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Choose payment method
  • H3 WARNING - This site is for adults only!
  • H3 WARNING - Javascript Required!
  • H1 The Original Pioneer of Gooning!
  • H2 No Trends, No Scripts & No Bullshit! - Just Pure Fucking Porn!
  • H2 Newest Gooning Videos Enjoy a brand new 100% exclusive video every week!
  • H4 Asteria Jade Gets A Pounding And Huge Load of Cum skipped
  • H4 Little Puck Gets Multiple Loads of Cum And Creampied!
  • H4 Gia Derza Gets Ass Pounded for Multiple Loads and Creampies!
  • H4 Kimora Quin Gets Multiple Loads of Cum!
  • H4 Liv Revamped GOONS For Creampies!
  • H4 Beca Barbie gets multiple Loads of Cum!
  • H4 Eva Nyx Comes Back for Multiple Loads of Cum!
  • H4 Amber Summer And Rissa May Come over for some Wild Fun!
  • H4 Kali Roses Is A GOONMUSE QUEEN!
  • H4 Diabella Eclair Gets Multiple Loads of Cum!
  • H4 Indica Marie Gets Multiple Loads of Cum!
  • H4 Alexa Chains Gets Multiple Loads of Cum!
  • H2 What is Gooning??
  • H2 Most Popular Models
  • H4 Tommy King skipped
  • H4 Hime Marie
  • H4 Suttin
  • H4 Tiffany Watson
  • H4 Emma Hix
  • H4 Avery Black
  • H4 Kayley Gunner
  • H4 Nicole Doshi
  • H4 Amari Anne
  • H4 Liz Jordan
  • H4 Anna Claire Clouds
  • H4 Mina Luxx
  • H2 Most Popular Gooning Videos
  • H4 Emma Hix's Perfect Pussy Oiled Up! skipped
  • H4 Hime Marie - Super Goon Slut
  • H4 That. Girl. Suttin!
  • H4 On Cloud 9 with Anna Claire Clouds
  • H4 Gaby Ortega Gets TWO Big Facials!
  • H4 Goon Queen Willow Ryder Gets Multiple Loads!
  • H4 Kayley Gunner - A Proper Goon Session
  • H4 Ameena Green Gets Multiple Loads and a Creampie
  • H4 Holly Day - Multiple Loads for Super Goon Babe
  • H4 Tommy 'Mommy' King - Goon Queen
  • H4 Nicole Doshi - Goon for a Squirt Queen!
  • H4 Tiffany Watson The Squirt & Twerk Queen!
  • H1 INCLUDED WITH YOUR MEMBERSHIP duplicate H1
  • H2 4+ New Gooning Videos a Month 100% Original Content Mobile and Tablet Optimized Videos Full Length, HD Video Unlimited Streaming Secure 256bit Encrypted Access 24/7 Customer Support

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

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
Alt Text Quality
Action
18 of 22 images have issues
FIX
18 of 22 images have issues
Critical::
18 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
14 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
4 decorative image(s) correctly marked
22 images 4 decorative 18 missing
IssueCount
missing18 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
Info::
1 navigation landmark(s) detected
Info::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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
Form Accessibility
Action
17 of 25 controls have issues
REVIEW
17 of 25 controls have issues
Critical::
17 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button">; <input type="button">; <input type="button" id="buynowbutton">; <input type="button">; <input type="button">; <input type="button">; <input type="button">; <input type="button">; <input type="button">; <input type="button"> (+7 more)
Info::
8 control(s) properly labeled
25 controls
8 labeled
0 placeholder only
17 unlabeled
ControlTypeLabelMethod
#option1radionone
#option2radionone
#option4radionone
#buyopt_##id##radioRent ##label## - $##price##for/id
#buyopt_##id##radioRent ##label## - $##price##for/id
#cartopt_##id##radioRent ##label## - $##price##for/id
#cartopt_##id##radioRent ##label## - $##price##for/id
#tokenopt_##id##radio$##price##for/id
inputbutton(none)none
inputbutton(none)none
inputbutton(none)none
inputbutton(none)none
inputbutton(none)none
#buynowbuttonbutton(none)none
inputbutton(none)none
inputbutton(none)none
inputbutton(none)none
inputbutton(none)none
inputbutton(none)none
inputbutton(none)none
Logintext(none)none
Passpassword(none)none
#g-recaptcha-response-05wat5dflu2gtextarea(none)none
#h-captcha-response-05wat5dflu2gtextarea(none)none
Submitsubmit(none)none

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

<input type="button">; <input type="button">; <input type="button" id="buynowbutton">; <input type="button">; <input type="button">; <input type="button">; <input type="button">; <input type="button">; <input type="button">; <input type="button"> (+7 more)

Why this matters

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

Source: WCAG 2.1 SC 3.3.2

B
Form Input Quality
2 input-semantic issue(s) across 25 form control(s)
REVIEW
2 input-semantic issue(s) across 25 form control(s)
Info::
1 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="Pass">.
Info::
1 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text" name="Login">.
B
Mobile-Readable Font Sizes
90% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
90% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 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: <a> 11.0px ("Click for Parental Controls").
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title GoonMuse Gooning Porn Videos ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
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 The Original Pioneer of Gooning!
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
32px · bottom of viewport
h1 INCLUDED WITH YOUR MEMBERSHIP
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
32px · bottom of viewport
h2 No Trends, No Scripts & No Bullshit! - J…
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Newest Gooning Videos
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What is Gooning??
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most Popular Models
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most Popular Gooning Videos
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 4+ New Gooning Videos a Month
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 100% Original Content
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mobile and Tablet Optimized Videos
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Full Length, HD Video
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Unlimited Streaming
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Secure 256bit Encrypted Access
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 24/7 Customer Support
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Choose payment method
1.05:1
#000000
on
#110701
needs 3.0:1 (large text)
19px · above the fold
h3 WARNING - This site is for adults only!
1.24:1
#000000
on
#1F1C15
needs 3.0:1 (large text)
19px · mid-page · over background image/gradient
h3 WARNING - Javascript Required!
1.11:1
#000000
on
#12110B
needs 3.0:1 (large text)
19px · bottom of viewport
title GoonMuse | The Original Pioneer of Gooni…
1.07:1
#000000
on
#15080C
needs 4.5:1 (normal text)
16px · top of page (header area)
span SET TITLE
1.05:1
#000000
on
#0E0607
needs 4.5:1 (normal text)
16px · top of page (header area)
span SET TITLE
1.03:1
#000000
on
#080504
needs 4.5:1 (normal text)
16px · top of page (header area)

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)
ElementRatioRequiredFGBGResult
h1 The Original Pioneer…1.11:13.0:1
#000000
#12110B
Fail
h1 INCLUDED WITH YOUR M…1.11:13.0:1
#000000
#12110B
Fail
h2 No Trends, No Script…1.11:13.0:1
#000000
#12110B
Fail
h2 Newest Gooning Video…1.11:13.0:1
#000000
#12110B
Fail
h2 What is Gooning??1.11:13.0:1
#000000
#12110B
Fail
h2 Most Popular Models1.11:13.0:1
#000000
#12110B
Fail
h2 Most Popular Gooning…1.11:13.0:1
#000000
#12110B
Fail
h2 4+ New Gooning Video…1.11:13.0:1
#000000
#12110B
Fail
h2 100% Original Conten…1.11:13.0:1
#000000
#12110B
Fail
h2 Mobile and Tablet Op…1.11:13.0:1
#000000
#12110B
Fail
h2 Full Length, HD Vide…1.11:13.0:1
#000000
#12110B
Fail
h2 Unlimited Streaming1.11:13.0:1
#000000
#12110B
Fail
h2 Secure 256bit Encryp…1.11:13.0:1
#000000
#12110B
Fail
h2 24/7 Customer Suppor…1.11:13.0:1
#000000
#12110B
Fail
h3 Choose payment metho…1.05:13.0:1
#000000
#110701
Fail
h3 WARNING - This site …1.24:13.0:1
#000000
#1F1C15
Fail
h3 WARNING - Javascript…1.11:13.0:1
#000000
#12110B
Fail
title GoonMuse | The Origi…1.07:14.5:1
#000000
#15080C
Fail
span SET TITLE1.05:14.5:1
#000000
#0E0607
Fail
span SET TITLE1.03:14.5:1
#000000
#080504
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 78/100 — 2 failing, 13 passed
REVIEW
78

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.

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.cookiesScroll > div.cookiesSpace > div.warningPop > img.warnlogo div.cookiesScroll > div.cookiesSpace > div.warningPop > img.warnlogo
div.warningPop > div.splash_rta > a.link_med > img div.warningPop > div.splash_rta > a.link_med > img

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

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>`
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
○`[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 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
○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.
○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
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 187 chars
Got: 1 >120-char heading(s)
Info::
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 Input Types
25 form control(s) checked, no type mismatches
PASS
25 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://newassets.hcaptcha.com/captcha/v1/494ae5ee0caca30cfa99514c266b501a90fa2…")
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
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.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback