Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

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

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

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.

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 ✗

Landmark Structure

2 landmarks

REVIEW

2 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Lighthouse Accessibility Audits

Action

Score 78/100 — 5 failing, 17 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.

ARIA

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reveal password `div > div.v-input > div.v-input__append-outer > button.g-input__field-control`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
We use cookies to run this website. See our Cookie Notice . `div.b-cookies-informer > div.b-cookies-informer__inner > div.b-cookies-informer__container > div.b-cookies-informer__text`
Cookie Notice `div.b-cookies-informer__inner > div.b-cookies-informer__container > div.b-cookies-informer__text > a`
ONLY NECESSARY COOKIES `div.b-cookies-informer__inner > div.b-cookies-informer__container > div.b-cookies-informer__nav > button.g-btn`
ACCEPT ALL `div.b-cookies-informer__inner > div.b-cookies-informer__container > div.b-cookies-informer__nav > button.g-btn`
Email `div.v-input__control > div.v-input__slot > div.v-text-field__slot > label.v-label`
Password `div.v-input__control > div.v-input__slot > div.v-text-field__slot > label.v-label`
By logging in and using OnlyFans, you agree to our Terms of Service and Privacy… `div.login-col > div.login-col__inner > form.b-loginreg__form > div.b-loginreg__form__issues`
Terms of Service `div.login-col__inner > form.b-loginreg__form > div.b-loginreg__form__issues > a`
Privacy Policy `div.login-col__inner > form.b-loginreg__form > div.b-loginreg__form__issues > a`
Forgot password? `form.b-loginreg__form > div.b-loginreg__links > span > button.g-btn`
Sign up for OnlyFans `form.b-loginreg__form > div.b-loginreg__links > span > button.g-btn`
SIGN IN WITH X `div.login-col > div.login-col__inner > form.b-loginreg__form > a.g-btn`
SIGN IN WITH GOOGLE `div.login-col > div.login-col__inner > form.b-loginreg__form > a.g-btn`
PASSWORDLESS SIGN IN `div.login-col > div.login-col__inner > form.b-loginreg__form > button.g-btn`
©2026 OnlyFans `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Contact `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Help `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
About `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Blog `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Branding `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Store `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Terms of Service `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Privacy `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Complaints Policy `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Cookie Notice `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
DMCA `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
USC 2257 `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Contract between Fan and Creator `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
OnlyFans Safety & Transparency Center `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Anti-Slavery and Anti-Trafficking Statement `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`
Acceptable Use Policy `div.container > nav > div.l-footer-static__menu__col > a.l-footer-static__menu__item`

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
Cookie Notice `div.b-cookies-informer__inner > div.b-cookies-informer__container > div.b-cookies-informer__text > a`
Terms of Service `div.login-col__inner > form.b-loginreg__form > div.b-loginreg__form__issues > a`
Privacy Policy `div.login-col__inner > form.b-loginreg__form > div.b-loginreg__form__issues > a`

These are opportunities to improve the legibility of your content.

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.m-android `html.m-android`

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

●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 have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

A+

Heading Hierarchy

3 headings

PASS

3 headings

Single H1 present

H1 onlyfans.com
H2 Performing security verification
H2 Verification successful. Waiting for onlyfans.com to respond

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

2 links, 0 buttons — all OK

PASS

2 links, 0 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://www.cloudflare.com?utm_source=challenge&utm_campaign=m; https://www.cloudflare.com/privacypolicy/

2 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cloudflare.com?utm_source=ch…	Cloudflare	new tab	Add '(opens in new tab)' to text
https://www.cloudflare.com/privacypolicy…	Privacy	new tab	Add '(opens in new tab)' to text

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

https://www.cloudflare.com?utm_source=challenge&utm_campaign=m; https://www.cloudflare.com/privacypolicy/

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

A+

Color Contrast (Screenshot)

10 text elements analyzed, 0 fail WCAG AA

PASS

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

10 pass

Show all checked elements (10)

Element	Ratio	Required	FG	BG	Result
h1 onlyfans.com	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Performing security …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Verification success…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Just a moment...	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p This website uses a …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Ray ID:	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code 9ed52efe9b8651e4	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Performance and Secu…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cloudflare	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy	21.00:1	4.5:1	#000000	#FFFFFF	Pass

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.

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